edanzer

Thanks @joshbiz for the detailed input. I’ll share with team for discussion, and have us experiment with some changes to keep the feel but improve on accessibility/contrast.

@anna-blume – thanks for adding your vote.

If anyone else lands here with same concerns, please post your vote/support as well.

Erick (CEO at Imagely)

@garlof – Hmm. Usually a white screen means there is a PHP fatal error. You can get the error to show by going to your websites root folder, and finding the wp-config.php file. Find the line that says define( ‘WP_DEBUG’, false ); and change false to true.

All that said, if there was a PHP fatal error, you’d be seeing the issue everywhere, not just Firefox. Given it’s just Firefox, it has to be connected to the browser somehow. Probably obvious – but other sites are working in Firefox right? I recall reports of FF showing white screens for all sites.

Assuming it’s just FF, and it’s just this one site, I’m actually not quite sure what to suggest. I’ll ping our team to see if they have thoughts.

I see, you have an album (id 1) that has a lot of galleries. But the latest gallery with id 52 isn’t showing.

As far as I know, I don’t think there is a limit on galleries in an album. That being said, I also don’t think we’ve ever specifically tested very large numbers of galleries in an album. I do wonder – given this issue occurred right at the round number of 50 galleries – if there anything that unintentionally tries to set pagination above a that number of galleries in a single album just to avoid excess page load, and maybe that’s not working correctly on the front end.

I’m not quite sure how to trouble shoot though, short of logging in and looking.

Sounds like you may trying a work around. If you have other questions as you work on it, let us know.

@uldis23 – Any chance you can provide either:

a) a screenshot of what you’re seeing so we can diagnose

b) access to your site so we can troubleshoot? If you’re open to this, you can submit a bug report (https://www.imagely.com/report-bug/) with your WordPress credentials. Put “For Erick” in the subject to be sure it gets my attention.

The update has had 80K downloads and very few tickets today. That means its working for most people, and its likely very specific. That’s why more detail (or access) on your specific site would help.

Thanks.

Erick

Hey @jeroenverplancke – Few quick thoughts.

1) You can download older versions from the Advanced page here: https://wordpress.org/plugins/nextgen-gallery/advanced/

2) I want to emphasize that so far today, we’ve had over 80,000 downloads of the new update, and a grand total of 7 support tickets. Of those, one had nothing to do with the update, and 2 were caching. That leaves 4. I know it doesn’t help you to say it, but as far as a big update goes, that’s actually amazing. It means the update is working very well across almost our entire user base. If there were widespread issues, the forums here would be blowing up.

3) With all that in mind, we’d actually love to troubleshoot what’s happening with your site. It likely your issue is very specific – server side caching, theme/plugin conflict, etc. It may be a while before someone else finds the issue, which means whatever it is, it will stay broken for you.

If you are open to it and willing to send creds, I’ll look at it myself this evening. Just submit a report at https://www.imagely.com/report-bug/ with site details and put “For Erick” in the subject line so I see it.

I sense you may just want to get working. If so, I do totally understand . You can still grab the last version from the link above and downgrade, and try again once we’ve got a couple more 3.0.x versions out.

Thanks.

Erick

@oldman55 Yes, we would like to take a look at this if you are open to it. Can you submit a report here with the site details, including WordPress login and FTP credentials if you are willing?

https://www.imagely.com/report-bug/

In the Subject, please add “For Erick” at the beginning just to be sure I see it.

Thanks for reportina and possibly giving us the chance to evaluate. We obviously want to be sure the update stays smooth.

Erick

@omi54 – we did have one other user report this. He had the issue in Chrome, but not Safari. We didn’t get a chance to troubleshoot to find out way, but that might work.

I suspect it’s some kind of javascript error being generated by a plugin (ours or another) that’s breaking the javascript components of our insert gallery window.

If you’d like to troubleshoot a bit more….are you familiar with the javascript console? Just go into the menu of your browser and look for something like View > Developer > Javascipt console in Chrome or Develop > Show Javascript console in Safari.

When you open it, it will look like this:
https://monosnap.com/file/VngO8stfqQ6u3UwlHBPFOU8yJwkkUo

If you can find that and send a screenshot we may be able to identify what’s causing the error, it may help us see more exactly what the problem is.