edanzer

@aigar – Can you confirm, with certainty, that you are running the 7.2 release version and not 7.2RC6? So far our tests on 7.2 have been fine, and everyone else above who has said they are running 7.2 was, as far as we can tell, actually running 7.2 RC6.

@digbymaass – in your case, your issues are still certainly due to the fact that the PHP bug continues to existing on PHP 7.2 RC6, so that won’t resolve thing.

Hey all – As far as we know, and from our own testing, the fix for the original bug was including in 7.2.0.

@carlos-revilla – the PHP warning you note is something we saw as well, and is newly introduced with PHP 7.2.0. It’s something we’ll fix in an upcoming release. But that warning would never produce the broader symptoms you are seeing (500 error across site). I’ll be honest and say it’s not immediate obvious what would be causing that 500 error – it’s not the same bug, which was fixed; and it’s not something we’re duplicating. We’ll need to do more assessment to figure out what’s going on. We’ll have a dev looking at it today.

@karpin – “i tested and have the same problem” – can you clarify, are you seeing the PHP warning, the 500 errors, or both?

@aeternal – We’ll look into it.

@kent-brockman – First, I want to be clear, the issue here is not with our plugin. It is a bug in specific PHP versions. There are only two versions we know have the bug: 7.0.26, and 7.1.12. If you use any other 7.0.x or 7.1.x version of PHP, you should be fine. Our tests of of 7.2.0 are also fine, though obviously some users in this thread seem to be seeing something different.

Hi all. Update: From what we can see, including a test to confirm on our side, this issue is fixed in PHP 7.2.0, released this morning. We’ve also just released a NextGEN release that deactivates most functionality of NGG when it’s run on the two problem versions of PHP.

Hi all. Update: From what we can see, including a test to confirm on our side, this issue is fixed in PHP 7.2.0, released this morning. We’ve also just released a NextGEN release that deactivates most functionality of NGG when it’s run on the two problem versions of PHP.

• This reply was modified 8 years, 5 months ago by edanzer.

I also wanted to repost a longer response of my own that I added to another thread here for everyone:

Hey all – CEO of Imagely here. I wanted to post an additional note on this. The root cause for this is a bug in two specific versions of PHP. The powers that be have already patched this on the PHP side, though have not yet released it.

The nature of the bug means that it would be an epic task for us to ‘fix’ it in NextGEN Gallery. The bug relates to PHP logic that we use throughout the plugin.

All that means that we do not intend to fix it on our side, but rather wait for PHP to release its own patch.

In the meantime, we are going to push a release that deactivates most NextGEN Gallery functionality on any servers that are running the two problem versions of PHP. This fix is being tested now, and will be released in the next couple of hours.

–

As a side note, I should emphasize that the PHP bugs have ramifications well beyond NextGEN Gallery. Mixed with a variety of other products or environments, the PHP bugs can cause server crashes. We know from internal conversations that Cloudways, for example, tried updating to 7.1.12 and then rolled back due to related issues. So if your servers are running the problem versions, they *should* be rolled back, or upgraded once the patches are released – in general and not just because of NextGEN Gallery.

If you have further questions, let us know.

– Erick

I’m reposting this in a few relevant threads:

Hey all – CEO of Imagely here. I wanted to post an additional note on this. The root cause for this is a bug in two specific versions of PHP. The powers that be have already patched this on the PHP side, though have not yet released it.

The nature of the bug means that it would be an epic task for us to ‘fix’ it in NextGEN Gallery. The bug relates to PHP logic that we use throughout the plugin.

All that means that we do not intend to fix it on our side, but rather wait for PHP to release its own patch.

In the meantime, we are going to push a release that deactivates most NextGEN Gallery functionality on any servers that are running the two problem versions of PHP. This fix is being tested now, and will be released in the next couple of hours.

–

As a side note, I should emphasize that the PHP bugs have ramifications well beyond NextGEN Gallery. Mixed with a variety of other products or environments, the PHP bugs can cause server crashes. We know from internal conversations that Cloudways, for example, tried updating to 7.1.12 and then rolled back due to related issues. So if your servers are running the problem versions, they *should* be rolled back, or upgraded once the patches are released – in general and not just because of NextGEN Gallery.

If you have further questions, let us know.

– Erick

@lyniaer – While we’re sad to see you didn’t have a great experience, we appreciate the effort to provide detailed feedback.

Some of the issues you note – like storing data and keeping ID’s unique – are quite intentional, and born of past user frustrations of various kinds. These are essentially safety measures, and while some users find them excessive, historical experience has shown them to be the right approach – greatest good for the greatest number.

I doubt you’d find those particular issues to be so problematic, though, if the rest of the plugin was working for you. I think that’s the bigger issue. Obviously, creating a simple gallery with 40 images and being able to open it in a lightbox is standard gallery behavior. It should be easy, and yes, obviously, it’s working for most users.

I won’t say it’s your fault, per se, but just if you’re having an issue that others aren’t, there’s a good chance it’s something related to your environment. It’s hard to know what without troubleshooting.

I will say that this is one of the greatest challenges – for us and all plugin developers – in the WordPress environment. Our plugins are loaded in so many thousands of different kinds of environments – different servers, security measures, PHP versions, WordPress configurations, etc – that it is basically impossible to get something working flawlessly working in every possible instance.

I have to assume that in your case, we’ve just stumbled on an environment that has some variable that we haven’t seen or accommodated yet. Given the sheer number of installs we have, this just happens from time to time.

Given it’s not working for you, your review is justified. If you want to try again, and post your issue in the forum, we may be able to guide you to solving it. If not, we understand and we hope you find another gallery solution that works for you.

Thanks,
-Erick (CEO, Imagely)

• This reply was modified 8 years, 5 months ago by edanzer.