Plugin Author
Cetabo
(@cetabo)
Hi,
Thanks for feedback could you give me a sequence of steps so we can reproduce the problem and fix it. Also what version of WP do you use ?
Thanks! WordPress 3.6.1. with minimum plugins. I disabled them one by one until I discovered that it was yours that was blocking the featured images. That said, I have the StyleShop theme from Elegant Themes installed, along with their Elegant Builder and ET Shortcodes; in addition, I have the latest Jetpack, a thumbnail regeneration tool (not currently in use), Slideshow and your plugin, version 1.0. The theme and all plugins are current.
When your plugin is active, if I try to set a Featured image, the media library modal window displays one weird blank “image” at the top of the list, and no matter what image I select from the media library, it never “takes”. As soon as I deactivate your plugin, that mysterious blank image disappears and I can select an image for the Featured Image. This applies both to pages and posts, and applies whether it’s a new post/page or an existing one that I try to update. It also applies if I’m trying to change an existing Featured Image or add a new one to an existing article. Basically any permutation I could think of…
Please let me know if you need any other information.
Plugin Author
Cetabo
(@cetabo)
Thanks! for feedback, with your help I have identified the problem and fixed it, please update the plugin and check if this is working correctly.
Oops, no–now the media library doesn’t appear at ALL in the modal window when trying to add or update a featured image. By that I mean that the modal does come up, but it’s completely blank.
Plugin Author
Cetabo
(@cetabo)
This should not happen, did you tried to clean the browser cache ? Normally no script should load except when the plugin page is active. Is there any JS error in the browser console ?
I have cleared the cache and restarted the browser, with the same result. There are a few JS errors, but I don’t know how to get them to you.
We may need to hold off on solving this, though; it turns out there is a DNS resolution issue on this site; I hesitate to try to chase this down until I know the site resolves correctly. I’ll keep you posted.