Plugin Contributor
Imagely
(@imagely)
@eword1 – You will likely need to manually deactivate NextGEN Gallery via FTP or your server’s file manager; or, at least this will remove it from the equation if it is exacerbating an existing condition on the site.
To do this, use an FTP client (for example FileZilla) to rename the /nextgen-gallery/ folder under the /wp-content/plugins/ folder, then log into your WordPress dashboard and visit the Plugins > Installed Plugins page, you will likely see a message that NextGEN Gallery has been deactivated. Now, return to your site via FTP and change the NextGEN Gallery folder back to its original name. I often suggest just adding the tilde ( ~ ) character to the front of the folder name as a renaming convention.
From this point, there could be a plugin conflict going on here or at least it should be ruled out. Have you tried deactivating all of your plugins, clearing your browser cache (and site caches if you are using a caching plugin), then reactivating the NextGEN plugin? If this fixes the problem then it was likely one of the deactivated plugins that was causing an issue. Now, retrace your steps activating each plugin and re-checking to see if the problem returns. If it does then that last activated plugin was probably the one. Keep reactivating and in most cases it is also best to keep checking after each plugin, sometimes there may be more than one plugin on a site that will create an issue. If you do find one (or more) plugins causing this problem we would greatly appreciate your feedback on them so the developers may address them as soon as they can.
Also to note, in rare cases it may be the theme itself that is causing a conflict so while you have just the NextGEN plugin activated you might consider temporarily switching to one of the default WordPress Twenty series themes and see if this corrects the issue as well.
If the problem still persists after all of this we would still want to know, even more so, as we will still want to sort out the issue and may need additional details.
Thanks!
– Cais.
Thread Starter
EWord1
(@eword1)
Hello Cais: thank you for your reply. While waiting for it, I went to work on the issue. To make a long story short, it had to be a plugin conflict which it proved to be. I took the opportunity to delete bloat plugins (including the infamous W3C cache) and to deactivate plugins one at a time. I found the conflicting plugin to be: “Call Now Button” Version 0.3.1 | By Jerry Rietveld.” I had not detected a prior conflict, but once removed the site stabilized, NGG operated as it should and even seemed to allow features that were not working that I had given up on. For this site I am using the flycase WordPress theme and there seem to be no conflicts between it and NGG. We are back in business and once again, thank you for your response.
-Erik
Plugin Contributor
Imagely
(@imagely)
@eword1 – Thanks for the update!
– Cais.
