WP_PLUGIN_URL doesn't take SSL into account
It's common for sites that sell stuff to force the page to load with SSL by redirecting to the blog URL with https protocol instead of http. Countless plugins don't take this into account and use WP_PLUGIN_URL to locate their scripts, stylesheets and images, breaking the "clean" SSL page load and causing some browsers to issue scary sounding warnings about "insecure content".
Whilst there are hacks that fix most of these plugins, no single hack will fix every errant plugin. Changing WP_PLUGIN_URL to handle the change in protocol would fix them all.
Yes, correct; tell all the other plugin developers :)
(I should add: yes, I have fudged it myself in the past, but I'm amazed at how many very professional and *for profit* plugins still use WP_PLUGIN_URL)
Well. It changed ;)
If it helps, the plugin repo team knows and is compiling lists of plugins who're doin' it wrong in many aspects. First up are the ones with serious issues, then rules violations, then things like this.
Beauty. In the meantime, there's always this:
(yes, I wrote that, and then I fixed a couple of my own plugins!)
RSS feed for this topic
You must log in to post.