Charles Fulton

Looks good; thanks for the quick resolution.

I apologize for being unclear. The renaming isn’t done with a plugin but in the Network Admin. On the site editing page (wp-admin/network/site-info.php) it’s possible to change the domain. These notifications are useful and don’t want to disable them, but I’m concerned that in the rename scenario I’m getting a notification that is both redundant (in terms of visibility) and incorrect (in the name of the affected blog).

Note, this doesn’t actually resolve the issue for non-super admins on multisite.

Benjamin, thank you for your very helpful suggestions. I really do appreciate it. I’ve incorporated both into the script, and rewritten it to be aware of which blog it’s in (although probably breaking single-site compatibility in the process).

I’m satisfied at this point that our issue was caused by missing image slugs, which in turn was probably caused by a botched upgrade in the last 3-4 years. I think we’re all set here. Thanks again to you and @photocrati for your assistance.

I’ve made a wp-cli plugin which populates missing image slugs. The code is available on Github. @photocrati, I’d appreciate feedback on whether filling in the missing image_slug entries, without doing anything else, is a sound approach. Limited testing showed no issues, aside from needing to empty the gallery cache after running the script.

@photocrati We haven’t used any database optimization plugins or anything like that. We have a separate hosted MySQL database server. This is an enterprise environment and it is not possible to provide credentials.

If you could provide guidance about the image_slug field I think that would be most helpful toward resolving the issue. It’s empty (not null, it’s simply empty with a length of zero) for about 20% of entries, and only from the oldest gallery. I suspect there may have been an issue with an upgrade 3-4 years ago. Can you point me to the part of the plugin which would have handled the creation of the slugs so that I might re-run it manually? In the alternative, can I simply create new slugs? I assume that the slugs must be unique within the wp_x_ngg_pictures table?

@photocrati thanks, I’ve tried that, but the images in question still don’t have slugs. For each of these the image_slug field is empty with a length of 0.

@photocrati the code is unaltered and I’ve just upgraded our development environment to 2.0.66.37 with no change. One thing I did notice, however, is that the images for used in the gallery have no value set in the image_slug column in the wp_x_ngg_pictures. I have no idea why that would be the case, possibly an upgrade went wrong at some point. Is this a potential problem and if so is it possible to regenerate the slugs?

@photocrati sorry my late reply. That’s exactly what the setting looks like in my configuration; there’s no template specified (I don’t have the Display triggers options but I assume that’s part of the pro version). I’ve tried resetting the options and disabling and reenabling the plugin. It has no effect. On upgrading to 2.0.63 or higher the imagebrowser stops working.

@photocrati Thanks for your quick reply. I’m not sure that I follow you. To the best of my knowledge we haven’t customized NGG nor are we using a custom template. I checked the settings for this site and the only thing specified under NextGEN Basic Image Browser is Enable AJAX Pagination. Where should I be looking? Are you saying there’s something in our theme which could be causing the issue?

@photocrati this is an example which works under 2.0.61: https://reslife.lafayette.edu/residence-hall-housing/residence-hall-descriptions/. If we upgrade to 2.0.63 (or higher) it will stop working.

On one of our larger multisites (more than 700 sites) I’ve seen this timeout. Anything in the PHP error log?

Though uncredited in the release notes it does appear that this patch was incorporated in the 2.4.0 release so I’m resolving the thread.

Thanks for the advice; we’ve considered that but would prefer to not manage a child theme if it can be avoided, especially when this feels more like a bug than a design choice. Your help is appreciated but we were hoping to hear from the theme author about why he made this choice.

The background is the only configurable color.