Conflict with NextGen

Thank you for reaching out to us. I don’t use NGG myself, so I can’t really say what could be causing this issue. You could carry out a process of elimination test by disabling all Firewall rules first then carrying out a test. If that does not work then disable other settings in the plugin until you come across the conflicting feature.

Let me know what the NGG developers find. I am curious to know.

Thank you

Thanks, I’ll have to wait to the next update causes a conflict. I’ll try disabling various rules/sections of AIO one by one until it works.

Hi,

I got the same kind of problems when updating NGG. I hade noted and read this thread before I did this update, so before I performed the update, I disabled all the aiowps settings. Then I updated NGG, thereafter put all the aiowps settings back again. Now, when checking the published gallery, it doesn’t work as expected, e.g. the image thumbnails are placed below each other, not in rows as they should be, and the thumbnails can’t be enlarged.

After this I also tried with deactivating aiowps completely. But the problems with NGG remains. Finally, I deleted aiowps completely. The problems remain. Of course finished with installing aiowps again.

PolyWogg – I read your descriptions again, how you solved the problems the first time. But I am not really sure concerning some parts. You say “I deactivated everything in stages until it worked”. Did you deactivated all other plugins, except NGG, including aiowps before it started to work? Or did it start to work before you deactivated/removed aiowps? Did you in any step deactivated NGG? Would very much appreciate if you can clarify.

Perhaps you also have tested again, and found what is causing the problem?

Hi Gurra,

If you deactivated AIOWPS completely, and you still had problems with NGG, then it isn’t a conflict with AIOWPS.

Equally, the problems you describe — layout, buttons, sizing — are not conflict problems of the same type. The ones you’re describing are more CSS/theme styling, whereas my conflict was more with permissions (although they might look the same as they both deal with blocks).

So, you’ll likely need to post for support over in NGG area, but generally, the solution is:

a. Set your theme to Twenty Twenty (or equivalent).
b. Disable all plugins except NGG.

Test it. This is the most vanilla install possible. If it works, then you have a conflict with something else; if it doesn’t work, then the problem is a configuration or error within NGG itself.

If it works with the vanilla config of Twenty Twenty and only NGG running, switch it back to your current theme. If it still works, you know it’s a plugin problem; if it conflicts, you know it’s a theme conflict. Either way, it gives you a big piece of the plugin.

In my case, where you ask about disabling in stages, what I mean is that what I first disabled plugins in stages trying to figure out which one was the problem. Some plugins are good candidates for potential conflict if they do layout for instance. Or if for instance they aren’t that critical to my site and easy to disable. So I have about 40 plugins running…I tried switching my theme from Weaver Extreme to Twenty Twenty, leaving all my plugins running, still a problem. Likely therefore a plugin problem not a theme issue.

I then took plugins 1-5, disabled them, checked. Still a problem.
Plugins 6-10, disabled, checked, still a problem.

In an ideal world, you won’t have to go ALL THE WAY down to 1 plugin to find the problem, but since I don’t like deactivating AIOWPS, I deactivated it last, leaving just NGG running. Yep, it worked after that. So I re-enabled AIOWPS and got the conflict. Disabled, reenabled the other 38 in stages again, testing as I went (just in case there’s a second conflict happening with another plugin too). Got everything back running except AIOWPS, and everything worked.

Then I ran some updates, and voila, reactivating AIOWPS left it running again just fine. Now I have a conflict again.

This time when I go to deactivate AIOWPS, I’m going to do it in stages within the plugin. So I’ll disable the firewall first. Then permissions. Etc. Hopefully it will narrow down which “section” of AIOWPS is the conflict. Noting of course that it isn’t AIOWPS conflicting with NGG or NGG conflicting with AIOWPS, it’s just the two conflicting with each other. Most likely somewhere there’s a file permission problem where NGG wants something set one way, and AIOWPS recommends something else. NGG has a unique feature in it for directories – it doesn’t use the standard media library (that’ s a deliberate feature, and one of NGG’s strengths), and perhaps that “feature” is not paying nicely with AIOWPS.

Again, that doesn’t likely have anything to do with your issue htough. If NGG doesn’t work when AIOWPS is deactivated, that’s not your conflict.

Good luck,

Paul

Hi PolyWogg,

Thanks very much for your answer! You have a lot of good explanations how you have tested and the reason why. Now I understand what you did.

In my case though, the issue seems to have been solved. During the night, without me doing anything. And I guess the explanation. The chache, some place. I thought about that directly after the NGG update and when the problems remained. I then tried with clearing the webb cache, and also tested several times yesterday, with some time between, in case of cache on the server. But nothing changed. Then I tried this morning and all was okay again.

Have a bit bad conscience, since you have done a lot of work with your answer. On the other hand it should be good to know that also the cache may be a part of the problem solving. And of course, the way you think when problem solving will be very good to know in all problem cases.

I am pretty sure that aiowps caused the problem from start. I recently changed the antivirus and firewall program to aiowps. Before this change, the NGG update problem never has occured. No other changes have been done on the site.

I am in a hurry right now, but if more points to discuss or straighten I will come back, not sure though if I have the time before the christmas holidays.

Thanks again!

@polywogg, have you found a solution to your problem?

Thank you

Unfortunately, no, or more like, “not really”. So I tried opening an existing page today, with AIOWPS running, went to edit the gallery, and since I had it in a Classic Block, I thought that had overcome the problem before. Nope, wouldn’t open i.e. I couldn’t edit the gallery.

Deactivated AIOWPS, reloaded the page, click, yep, it opens no problem. Reactivated AIOWPS, reinserted the old code, reloaded the page, and while it SHOULD block again, it doesn’t. For some reason, deactivating and reactivating works perfect to fix the conflict. I’m convinced it’s some sort of update thing — it’s trying to do something that AIOWPS won’t let it do. Once I deactivate it, it works fine, so it sets whatever is needed for the editing function (some sort of popup code perhaps?). Then when I reactivate it, since it has been loaded, it still works. Maybe it’s coming from cache instead, I don’t know. But it works after that.

My intent was to go through section by section for the next conflict, but this time, it reset before I could go through them.

P.

I am wondering if it has something to do with the issue mentioned in the following link forum post. There are a few bugs in WordPress 5.6.

Thank you

• This reply was modified 3 years, 11 months ago by mbrsolution.

Perhaps, but it is doubtful to me. It seems to me like it is blocking a popup…and for most of that link, if they deactivate and reactivate, the problem comes back. Mine stays gone. Next time I get the error, I’ll remove sections of AIOWPS to help narrow it down. For now, the solution is simply deactivate and reactivate for my site…

P.

Please let me know if you find out which feature is causing the conflict. I am curios to know ??

Thank you

I’ve made progress! So I upgraded NextGen earlier today. I had been using it a week or so ago, everything was working. Did the upgrade tonight, and suddenly I couldn’t edit galleries. I was about to do my dance of disabling AIOWPS when I remembered I’m supposed to be going through the sub-elements!

I started with the Firewall tabs, disabling things one by one, testing, reenabling. I didn’t get anywhere at first. Finally I did a full export of my settings, saved it. Then in Settings, I did a DISABLE ALL FIREWALL RULES. As soon as I did, NGG started working again. In between each test, I reloaded the pages to make sure I was testing options, so it is DEFINITELY in FIREWALL somewhere, but not the basic settings that I can see. I had expected it to be file permissions, but FIREWALL it is.

When I reimported the Settings to go back to what I had before, NGG still works. So whatever it is, from their side, it seems to be related to the update process for Imagely NGG and it loading the first time after an update. Since you don’t have problems like this with other plugins, perhaps it has something to do with NGG accessing non-typical WP directories (since it saves its images other than to Media Library).

If I was send you the Settings file somehow (uploading it here doesn’t seem like a safe idea hehehe), could you do a short-list of what functions are being blocked by my settings (not the code, I don’t think, something generically short) so I could send it to the Imagely developers to say “Which of these functions is NGG trying to use?”. Maybe there’s a better way to narrow it down, I’m only spitballing.

Let me know…

Paul Sadler

Hi,

so it is DEFINITELY in FIREWALL somewhere, but not the basic settings that I can see. I had expected it to be file permissions, but FIREWALL it is.

I suspect the issue might be coming from 6G Blacklist Firewall Rules / Enable 6G Firewall Protection:.

Regards

I’ll try disabling that for the next update! I can confirm that it wasn’t fixed by toggling:

– Basic Firewall Protection
– Pingback
– Debug Log
– Directory Contents
– Trace and Track
– Proxy Comment
– Bad Query
– Character String Filter

At least not individually, anyway. Stay tuned ??

PolyWogg

There was another update today, and I can confirm it was a 6G / 5G conflict. I disabled 6G, still didn’t work, disabled 5G and it did.

So do you recommend I pass that info to Imagely now? Or to Perishable Press?

PolyWogg

Hi,

There was another update today, and I can confirm it was a 6G / 5G conflict. I disabled 6G, still didn’t work, disabled 5G and it did.

Don’t enable 5G, this is now obsolete. Only enable 6G. The plugin developers will be removing 5G in the future.

Kind regards