@szabesz – 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.
Thanks for your reply!
I figured it out, it was an issue with the Theme, which has this rather unconventional rule:
div { position: relative; }
Strange, but it has not have any other side effects so far. I overwrote it so that it is back to the default “static” value and the buttons behave as expected. Luckily, only one div on the whole site seems to be using relative positioning, so I just had to fix that element and nothing else.
I hope this helps others who happen to run into this.
Anyway, thanks Cais!
@szabesz – Thanks for the follow-up!
– Cais.
