@tom Harrington
Hi Tom,
Good on you! You sound like a decent guy, and I apologize for being hard on you. It’s just that this sort of thing is becoming something of a trend.
I do appreciate that you wanted to let others know about the issue you experienced, however as I mentioned, this would have been better communicated by opening a new topic on the support forums. It’s the first place people tend to head (and are directed to) if they’re having difficulties, and it’s exactly the place this sort of minor incompatibility should be documented (as many people don’t read the plugin description before downloading). Additionally, for users who do conduct some due diligence before they download a plugin, the support forum is the best indicator of active development, support and outstanding issues.
The problem with writing a review for what is essentially a support ticket is that firstly, most people won’t ever read it (contrary to your intention), and may actually avoid using the plugin altogether thanks to the gradual decline in average star rating. Secondly, they’re not helpful moving forward, as the text is typically void of any reference to a particular version, and unlike a support ticket, can never be marked as resolved, giving the impression the described problem is a permanent issue.
But regardless, I do appreciate your feedback, and I’ll hopefully be wrapping up development of v2.0.1 (including the fix) over the weekend, for a release later next week after thorough testing. I hope you’ll check it out, and as always, just reach out via the support forum if you have any issues.
All the best,
Mark.