PolyWogg

Official support would obviously have more guidance, but as a fellow user, is it possible you turned “breadcrumbs” on in NGG and it could be conflicting? Just a thought, I had a somewhat similar problem awhile ago and it was breadcrumb related. Worth a try…

Paul
aka PolyWogg, a fellow user

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

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

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 Barbara, another post was looking at resizing images, and included some tips to prevent compression…just a thought.

https://www.imagely.com/docs/image-sizes-and-resolutions/

Ah-hah. The difference is apparent when the two are compared for the small bit of sky above and to the right of the woman. I wouldn’t say blurred so much as basically muted.

I’m not official support, just another user, but since I like to do astro photography, how the photos transfer and show up is incredibly important. It’s a pain for FB, for example. In the interim, I could suggest a few things to check, based on a few conversations some fellow Astro Photographers have had with their sites (not all NGG):

a. Often it is because of compression somewhere. Does it matter which gallery layout you use?

b. Is there any chance your theme is somehow showing 90% opaque or something.

c. When you upload in NGG, do you have them resized and altered for quality? (NGG / Other Options / resizing / quality). You could try NOT resizing them and see what happens?

I would leave your optimole off for now too. SOlve it without anything playing with the images.

d. You could also try uploading it to your media library and put them on the same page…that way you would know if NGG was altering the upload or WP was doing it.

e. Check your lightbox settings I suppose too…Does it show any different in the lightbox?

All of those are things I’ve seen happen with APs…not sure any of them are what is happening with yours though. ??

Good luck, I’d love to know the answer when you get it resolved. I’m redoing my site, and will need my AP images to be razor sharp.

Paul
aka PolyWogg

Fellow user –> I think you need to clear your cache too — the images look fine to me now. I assume you are referring to the actual images, not just the thumbnails.

As a fellow user, I can tell you the main solution is the same for any plugin that seems to have crashed your admin and that you want to disable. You have to go into your site’s hosting account (CPANEL, if you have it) to edit the directory where the plugins are stored, and just delete that plugin’s directory OR just rename the plugin directory something else temporarily (but this would disable ALL plugins at once). That will let you load your admin. No plugin is going to be able to give you a fix for your setup if you can’t even get into the site.

However, FYI, since NGG has 800K active users, it is highly unlikely that NGG “broke” your site on its own or it would be breaking a lot more sites. Far more likely is that your site has bad designs in its theme or other custom plugins, and when you activated NGG, those conflicts suddenly crashed your site because they are not fully WP compliant. Not NGG itself.

Equally, it would be even odder for NGG to crash your admin side of things. It might crash a page, a post, a gallery, etc., but your admin side? Not unless the update was somehow corrupted. Unless again, you have some sort of custom plugin that is actively managing your admin side perhaps or you’re running a custom theme you designed in Elementor or Divi that isn’t entirely compliant? Even then, it shouldn’t affect your admin side. I assume you’ve cleared all caches too. When you do get back in, you could try switching to a default theme like Twenty Twenty and reactivate NGG. You’ll at least know what it is conflicting “with”.

I’m also assuming though that you have ensured your site is running the specs for NGG, including the right versions of PHP.

Good luck, maybe official support has a better solution…

P.

Support might have something else to point to, but FYI, that link seems to going to the wrong page — it is going to your master gallery (ridestoke.gallery) instead of the mountain gallery. The one beside it goes to Whistler 2017, but that one likely just has the wrong page linked in the description.

Cool, I’ll file this one away for future use ??

P.

Maybe Benjamin will have a formal answer from support, but I use the original form:

[singlepic id=4482 float=”right” w=”250″]

and it works just fine.

I’m not sure what you are trying to do … it’s a simple gallery, you can’t “select” the photos…

P.

Hi Frederic, I’m using Firefox and Windows 10 and got no error from that page, it worked fine, including opening Lightbox images.

P.

Thats cool. Where do you add that code? Now I have ideas for my own site heheheh

PolyWogg

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