So there was one post a few weeks ago, including by the AIO developer, where there was a very specific conflict. I didn’t have that one oddly enough.
Mine is weird. About two months ago, people were noticing that they would create a block, they could insert the Gallery but afterwards, they couldn’t re-edit it. Or if they went back to an old gallery, they could see the “edit” or “delete” buttons, but couldn’t edit it. At the time, I wasn’t doing much new with galleries, so I ignored it, just noted in passing (I follow all the NGG posts for info, mostly).
Anyway, I had the error about six weeks later after everyone else’s problem had been fixed. I even use the Plus version, so I shouldn’t have had a problem still, but it looked the same. I couldn’t edit.
So I did the basic problem-solving loop:
a. Switch themes to see if the problem persists (it did, so not a theme conflict);
b. Progressively disable plugins (of which I have about 40) and keep checking as you go. I disabled my AIO-WPS last, and suddenly it worked again. I slowly re-enabled every other plugin in the list, all 39, and it still worked.
So definitely AIOWPS, right? Except when I reenabled it, it was STILL working again. I wrote it off as a glitch.
Fast-forward about six weeks, both updated (WP and NGG), and again, same problem. I couldn’t edit. This time, I was more strategic:
– NGG doesn’t work with everything enabled
– I *just* disabled AIOWPS, NGG works;
– Re-enabled AIOWPS, NGG still works.
WTH? My impression is that when NGG updates, something is “blocked” by AIO. If I disable it, run NGG, it seemingly “sets” something, everything works. Then when I reenable AIO, it still runs. That’s the only thing I can imagine. Unfortunately, with all the settings in AIO, it’s hard to know WHERE the problem might be. Next time I update NGG and get the error, I’m going to slowly disable “parts” of AIO to see where the conflict might be. I’ve been in touch with the AIO developer, and he’s open to any narrowing down I can do, so we’ll see if I find something. It’s not aggressive, seems to only happen after updates, and easily fixed (disable, reenable AIOWPS), but it’s a puzzle. ??
Paul
aka PolyWogg