PolyWogg

So on my other albums, that is the setting (240). For this one, that size is too big I guess…I had to lower it to 150 for this group of files. They’re really small photos, a age old glitch of my wife sending me photos by email before people in general realized that email shrunk files, and then she deleted them from her saved area (since I had them) before I could get the larger originals.

It works for this one, it’s a one-off problem I guess.

Hmm…I don’t have a specific “small” option by itself, but I have five choices and I’ll try each back with the grid option:

– Small square (75) — works
– Large square (150) — works
– Thumbnail (100) — works
– Small (240) — crashes
– Small (320) — crashes

So it looks like I just need to reduce the size on that album to the 150×150 size or smaller. On other albums, I had more of a masonry thing happening with smaller photos on the one line and some larger ones farther down. I assume there would be no difference if I switched to a masonry style? It’s a shame I have to force the later photos in that album to a small size too., but at least I can get it to show now. ??

Thanks, yes, we did cross. That makes sense. Although I did find one that wasn’t behaving like the rest, so I changed it to BELOW for that specific post. Might have been delayed cache. Although I had cleared the caches too. Shrug. It works now hehehe ??

Hmm…so I found some more posts where the titles weren’t showing. None of them were the mosaic or popup exceptions. But, regardless, I reset the Photos (Main) setting to “Below the Thumbnail”, which solved most of the problems. On a couple others, it said “use the default” except it didn’t seem to TAKE the default. If I changed it to BELOW THE THUMBNAIL, all good.

So I got them all to work, so I guess resolved?

Enabled Hosting cache, disabled other stuff. Checkd my settings, is there anything really wonky anywhere in this for PHP.INI:

max_execution_time = 90
max_input_time = 60
max_input_vars = 1000
memory_limit = 512M
post_max_size = 500M
session.gc_maxlifetime = 1440
upload_max_filesize = 450M
zlib.output_compression = Off

On another site, I have max_execution_time at the default of 30; memory_limit set to only 128M; post max size at 1024M; and max_filesize for upload at only 2M.

Is it possible the max execution time or the Upload size could be throwing things off?

Paul

Thanks James. Super frustrating. I had it working well again and then suddenly, it’s bogging down even with 15 plugins running, and I don’t even have the security or cache ones running yet. Sigh.

It DOES provide built-in caching, but I had turned that off some time ago, as it conflicted with one of my plugins at the time, don’t remember which now. I’d really rather run it, I’m not a photo-heavy site anyway, nor am I particularly worried about rankings. It’s a personal site, people come to it for specific reasons, none of which are search engine derived. So if it loads a little faster or a little slower on the front end, I can live with it (I made it a bit more mobile friendly, but that’s about it). I have a lot of text spread over thousands of posts, but the website structure is not load heavy. So I could get by with no cache, and since caching interacted oddly at times, I had just disabled it.

Interestingly, with the new cache enabled, and the back end running cached, I can load everything again. So technically it is “fixed” in the sense of “working”, just not working as per the normal load.

For what it’s worth for posterity, here are the plugins I’m running:

WP: 6.1.1
THEME: Weaver XTreme

CORE PLUGINS (15) — Everything works with these running, even without cache:
– Front-end:
– Display Posts
– Display Posts – Date View
– Flexible Table Block
– Weaver Xtreme Plus
– Weaver Xtreme Theme Support
– Back-end:
– Advanced Editor Tools (previously TinyMCE Advanced)
– Akismet Anti-Spam
– LiteSpeed Cache
– ManageWP – Worker
– Media Library Assistant
– OG — Better Share on Social Media
– Really Simple SSL
– Redirection
– Wordfence Security
– WP to Buffer Pro

SECONDARY PLUGINS I LIKE HAVING (11): Once I get above about 5 of these, the edit post window grinds to a halt
– Front-end:
– AddToAny Share Buttons
– Photonic Gallery & Lightbox for Flickr, SmugMug, Google Photos & Others
– Simple Lightbox
– Stackable – Gutenberg Blocks (Premium)
– Yet Another Related Posts Plugin (YARPP)
– Back-end:
– MailPoet
– MailPoet Premium
– WPForms Lite
– WP Mail SMTP
– Nested Pages
– Yoast Duplicate Post`

TERTIARY PLUGINS I CAN DROP (4): The backend is easily disabled although I would prefer to keep WPDiscuz (comment manager). With Cache running, I can run all 30.
– Front-end:
– wpDiscuz
– Back-end:
– Dashboard Wordcount
– Server IP & Memory Usage Display
– Simple Blog Stats

Paul

Thanks James, I’ve confirmed multiple times that it is neither.

If I deactivate all plugins, and run default themes (2017-2021) or my current theme, no difference. The edit window loads just fine. So it has to be a plugin, right?

Except I’ll try them one by one, no issues. So it has to be a combo, right? That plugin one is conflicting with plugin two or something. Except I’ll play with multiple combos, everything works in WHATEVER order up until I get to about #15. Then it starts bogging down no matter WHICH 15 I have loaded. I feel like I could randomly grab any 15 popular plugins and it would grind the site to a halt.

Interestingly, today I loaded Litespeed Cache which is what my server host likes best. I loaded the edit page with 20 plugins activated. It went slow. Backed out, reloaded, it loaded faster. Great. But not everything. Closed out again, reloaded. This time EVERYTHING loaded in under five seconds. So I loaded up another 8 plugins, now running 28, which it wouldn’t accept earlier. No problem at all.

Caching sped up the back end too, which some caches don’t seem to do, I know. I would prefer NOT to run the cache on the backend, but it seems to be the ONLY thing that lets me load. Physical resource limits are getting flagged on teh server (512MB) and IO processes are overloading (2MB/S). Prior to cache, of course.

Now it’s working. But shouldn’t it work WITHOUT the cache? It’s not that heavy a site…

Paul

I was hoping you had found a more definitive solution. I have this issue from time to time and there doesn’t seem to be much rhyme or reason. I can go through the process, get everything to work without plugins, add them back in, wait for it to stop working, annnnnd it goes back to working just fine. I am half-convinced it is a memory management issue, but I’ve tweaked memory out the wazoo with no effect. My other half thought is that it is a messed up config file…frequently when you take out caches or security files and reinstall them, the config goes back to the order it SHOULD be in, and everything goes back to working. I suspect some of the updates don’t work the way they should and code gets left behind. If you remove everything, you’re closer to an original copy and putting them all back in resets them to the right order. Except it doesnt’ always work. I also seem to have a problem at the 25 plugin mark. Sigh.

As a fellow user, reviewing the history, I’m confused as this seems like a NimbleBuilder conflict, not a NextGen one. Just to be clear, when two plugins conflict, it isn’t A conflicting with B, or B conflicting with A, it is that A & B are conflicting with each other.

However, since NGG has 900k+ users, and NB only about 50K, it seems more likely for NB to fix their compatibility with a top ten plugin than the reverse…Don’t get me wrong, it’s great that NGG will try to accommodate the conflict, but I’m surprised NB did nothing despite going through “several updates”?

P.

I don’t have a solution for you for the conflict, but as a fellow user, you could use any number of block collections to produce the same ToC. I prefer ones I can turn on and off more easily, customize etc. Just a thought, or as a temporary fix.

As a fellow user, I have a couple of ideas at the bottom for you to try. In the meantime, I’ll share my standard problem-solving steps for NGG glitches:

a. Create a staging site so that I’m testing on it, not my live site;

b. If something isn’t showing (gallery, image) after a recent NGG update, I disable my security plugin, load a page in NGG or create a new gallery, test it, and then re-enable my security plugin;

c. If it’s an image not triggering the lightbox, I make sure I’m not running two lightboxes at the same time (i.e. I’m only using the NGG lightbox);

d. If the changes aren’t showing, I try disabling my cache to see if it’s simply a static cache problem;

e. Check to see if there’s a conflict with my theme by switching temporarily to something like Twenty Twenty;

f. Check to see if there’s a plugin conflict by temporarily disabling my other plugins (either one by one or en masse)…having done testing like this before, I know certain ones that are easy to load/reload so I test them first. Others that require reconfiguring every time they’re disabled and re-enabled, I try to deactivate last. On the other hand, there’s a lot to be said for stripping away all other plugins temporarily, and going to just Twenty Twenty as a theme, and seeing if it works.

I inspected your page, and it is set up for those images to trigger your fancy box lightbox. You could try switching which lightbox is running. However, regardless, I think you have two errors. There’s no obvious reason why anything is showing in your footer unless that is the first image in your album perhaps. You should also try creating a brand new gallery on another page/post and previewing that to see if it works i.e. is it only “existing galleries” that are affected or “all galleries”. I suspect you have two problems, not just one — i.e. one problem is the lightbox not working and one is why something is showing in the footer. I thought at first perhaps that was just where popups were going but it doesn’t change on clicking the other images.

P.

As a fellow user (not formal support), that usually happens one of two ways:

a. Your theme is “stealing” the code so that NGG doesn’t see it (by wrapping it some other code)
b. You have it pasted into a Paragraph Block instead of a Custom HTML or ShortCode block within the editor.

I would try embedding it in a “Custom HTML” block in the editor first, and if that doesn’t “fix it”, you could try switching to a basic theme like Twenty TWenty to see if shows properly there.

Paul
aka PolyWogg

Have you tried removing the display buddy too? It sounds, as a fellow user not support, like your iThemes and NGG are both triggering the display each. I’m not positive for sliders, but that is a problem with other ones running Lightboxes, for example (see recent support post). Can you insert only one code or turn off sliders in either NGG or the DisplayBuddy?

PolyWogg

Hi JH…as a fellow user, I can point to a couple of things to try to help narrow down the problem…

a. In the gallery with the broken image, can you change the cover photo? You may have already tried that but it isn’t mentioned in your description. If another image is also broken, then you know if the problem is the image or the gallery.

b. If it’s the gallery, one of the most common problems is an extra odd character somewhere in the file chain i.e. a space that’s not a simple space, a special character “!]* etc…

c. If it’s the image (i.e. it works with another image as the cover), then I would guess it is EITHER the special character in a filename somewhere OR the metadata for that image (not necessarily the visible metadata) OR something with the image itself. You could try deleting that image, open it on your PC in something that can strip all metadata, and reupload + regenerate the size.

No guarantees any of those will help, but it might narrow down the problem…

Paul
aka PolyWogg