koolgirl

UPDATE:

I was obviously addressing the above reply to Mark Maunder and his post, which I addressed to Tim by mistake – though it does seem from Mark’s post that one of the staff such as Tim would carry on the topic anyhow. Regardless, I just wanted to clear that up – I was responding to Mark, of course, not Tim. Couldn’t edit the post, so leaving this update here.

Andrew,

I see. Thank you for the answer. I will not do that again, sorry for that.

Coincidentally, Andrew, or Jan (or one of the forum team members), it would appear that I in fact was mistaken in blaming the plugin here, although if the support team would like to continue to the details that is perfectly fine of course; but I would like to be able to make that very clear here. Can I delete threads, such as this one? Or is the proper procedure to just state the situation and that it was a mis-understanding and mark it resolved?

Note: I do again, just want to apologize for coming off as jumping to conclusions and/or offensive, if I did in any way at all, as I really do appreciate the plugin and really did not intend to do so.

Everyone reading this: I apologize for the long-winded post(s); seeing as how the founder personally responded here and seemed as though my post came off as some what offensive, as a developer my integrity really mandates that I clarify that this was not intentional. At all. I also wanted to explain that I clearly feel the plugin is both awesome and one of the very best available, both the free and paid versions.

Tim,

I actually made no damning statements about your plugin at all, and went out of may to explain how much I appreciated the plugin, and I also explained that I could possibly have been wrong about how this type of attack occurs, etc.

I do not understand you seemingly taking offense, when I went out of my way to explain that I appreciate the plugin, and very well could be mis-understanding how these types of attacks work (which I probably am from what Jan said – who did provide some helpful info about why that may be – thank you Jan). The only thing I said about the plugin is that it failed to alert me to the attack. That is a fact. Whether it is because of the type of attack and it probably couldn’t of been caught at all and therefore completely not related to the plugin’s performance, or because the plugin missed something, I clearly said I did not know. That was the main point of the post.

I have been using this plugin for a long time, and have brought you many, many users, and because of this I took the time to write this post in such a way as to explain how much I appreciated your plugin, why in my case, as having recommended it so extensively, a failing was a major source of concern and be respectful.

I also clearly stated that if it turned out this was the plugin’s failing, then, I would need another option – but that it was possible it wasn’t and I didn’t want to do that as I really like the plugin. I made no statements about the plugin at all, actually – I merely asked questions, and explained, very respectfully, why it would be a big problem in such and such circumstance, because of my business IF there had been a failing. I am actually quite, I guess the word would be upset (not angry or offended mind you – more bothered), that you seem to have thought the complete opposite. Users constantly berate developers in these forums making all sorts of wild assumptions and nasty statements and nasty reviews (which I did not do btw), and as a developer myself, I loathe that type of behavior; so for you to basically be lumping me with it (so to speak, not quite, I am stretching a bit on that one) is quite disappointing to me because that was not my intention. I took a lot of time to write that post so it did not come off that way, and any implications I made about the plugin’s performance, I made as to how this would be unacceptable if it had been a mishap on behalf of the plugin, to explain to your team, that it was a big part of my business flow and therefore a very, very big deal for me, and as every single client of mine is using either your free or paid plugin, it most certainly is.

Jan – I made that email as a throw away anonymous email, specifically for this purpose to be deactivated once I got a hold of the developer. Is this not allowed (not being sarcastic I really thought throw-aways would be accepted)?

If you had responded as Jan had, explaining that the type of attack in question probably couldn’t have even triggered the plugin, I would have responded with a comment that it was then my mis-understanding, stated how much the plugin had helped, etc., and then probably left a nice review and deleted this thread (I think I could do that – I am not a big forum user here by any means). My point being not that you should’ve responded as he did, but just that I am more than happy to sing the plugin’s praises loudly and apologize if it was my misunderstanding, which it seems likely to be, by the way.

In conclusion, I am pretty close to being convinced it in fact wasn’t a fail of the plugin but rather my misunderstanding how the attack worked, that caused it to be missed. If you would like the details (I would think you’d understand why providing that in a public forum, given my occupation, would not be something I would do – and again – should we have spoken the details in private and discovered me to be in error I certainly would have publicly stated that loud and clear asap) of the attack, I am happy to provide them in a non-public conversation. As I said however, after taking what Jan explained and searching a bit deeper, it does appear to be in fact my error not the plugin’s error. I am happy to concede that at this point, and should you like me to delete this thread due to that (or make a statement and mark resolved if that is not possible), I am happy to do that as well.

Thank you, and sorry for the confusion,

Nicole

Sorry, link did not show up in previous post:

See Screenshot of issue

So, yep. That’s what I get for no sleep. Wrong plugin entirely. ??