Tom Ewer

creativitymatters: I’m afraid I don’t follow — you’re saying that if you use a default theme the plugin comes back to life…have you considered that it’s the theme? What theme are you using?

In theory the way to track a plugin issue is to revert to a default theme and deactivate all plugins. Then reactivate your normal theme and plugins one by one to find the culprit. I appreciate that this is not always practical — perhaps you can do it one step at a time (i.e. theme first, then plugin by plugin).

creativitymatters: I agree. If this is a major issue affecting a lot of users then it would be in Joost’s best interests to jump in and fix the problem ASAP. My guess is that it’s not, because the support forum hasn’t been flooded with complaints and the WordPress community isn’t up in arms.

As such it’s probably some incompatibility issue with another plugin etc on our sites, which one could argue is our problem first, and Joost’s second (especially if the issue is only affecting a small number of people — he can’t be expected to resolve every single issue experienced by every single person — let’s not forget how complex and varied an environment WP can be).

The fact that I can’t be bothered to test the plugin on a blank WP install to see if the issue is with my site personally or with the plugin is a whole is indicative of the current importance of the issue to me, and as such, I can hardly expect Joost to drop whatever he’s doing and address my issue.

In closing, consider this — have you, I, or Mr. Flame (appropriate name) over there followed all of the instructions in Joost’s “READ THIS before you open a new thread!” stickied post — or even read them? If not, on what grounds should we even be submitting a support request?