edanzer
Forum Replies Created
-
Hey all – We’ve been working on this and finally have a work around for the PHP bug.
The following copy of NextGEN 2.2.20 should run with any version of PHP (including the bugged versions: 7.0.26, 7.1.12, 7.2RC6, and 7.2.0). Feel free to give it a try and let us know if you have issues.
https://imagely.com/wp-content/staging/nextgen-gallery.2.2.20.zip
We’d like to get a few confirmations before we release it officially.
Hey all – We’ve been working on this and finally have a work around for the PHP bug.
The following copy of NextGEN 2.2.20 should run with any version of PHP (including the bugged versions: 7.0.26, 7.1.12, 7.2RC6, and 7.2.0). Feel free to give it a try and let us know if you have issues.
https://imagely.com/wp-content/staging/nextgen-gallery.2.2.20.zip
We’d like to get a few confirmations before we release it officially.
Hey all – We’ve been working on this and finally have a work around for the PHP bug.
The following copy of NextGEN 2.2.20 should run with any version of PHP (including the bugged versions: 7.0.26, 7.1.12, 7.2RC6, and 7.2.0). Feel free to give it a try and let us know if you have issues.
https://imagely.com/wp-content/staging/nextgen-gallery.2.2.20.zip
We’d like to get a few confirmations before we release it officially.
Hey all – We’ve been working on this and finally have a work around for the PHP bug.
The following copy of NextGEN 2.2.20 should run with any version of PHP (including the bugged versions: 7.0.26, 7.1.12, 7.2RC6, and 7.2.0). Feel free to give it a try and let us know if you have issues.
https://imagely.com/wp-content/staging/nextgen-gallery.2.2.20.zip
We’d like to get a few confirmations before we release it officially.
@paradime – I also responded to you separately, but I’d emphasize the same thing I did in my original response. This is, very specifically, a bug introduced by PHP. There’s nothing we could have done to prevent it, and we’ve had devs looking at it around the clock since PHP released it.
Here’s the bug report from PHP: https://bugs.php.net/bug.php?id=75573
–
In any case, for both of you, even though we didn’t cause it and PHP has already patched it, we’ve still been working on it and finally have a work around for the PHP bug. The following copy of NextGEN 2.2.20 should run with any version of PHP (including the bugged versions: 7.0.26, 7.1.12, 7.2RC6, and 7.2.0). Feel free to give it a try and let us know if you have issues.https://imagely.com/wp-content/staging/nextgen-gallery.2.2.20.zip
We’d like to get a few confirmations before we release it officially.
@rederstreet We’ve been working on this and finally have a work around for the PHP bug. The following copy of NextGEN 2.2.20 should run with any version of PHP (including the bugged versions: 7.0.26, 7.1.12, 7.2RC6, and 7.2.0). Feel free to give it a try and let us know if you have issues.
https://imagely.com/wp-content/staging/nextgen-gallery.2.2.20.zip
We’d like to get a few confirmations before we release it officially.
@oldman55 Your issue is, we believe, related to the broader bug in PHP that you may have seen in some other threads here. We’ve been working on this and finally have a work around. This copy of NextGEN 2.2.20 should run with any version of PHP (including the bugged versions: 7.0.26, 7.1.12, 7.2RC6, and 7.2.0). Feel free to give it a try and let us know if you have issues.
https://imagely.com/wp-content/staging/nextgen-gallery.2.2.20.zip
We’d like to get a few confirmations before we release it officially.
@labres We’ve been working on this and finally have a work around. This copy of NextGEN 2.2.20 should run with any version of PHP (including the bugged versions: 7.0.26, 7.1.12, 7.2RC6, and 7.2.0). Feel free to give it a try and let us know if you have issues.
https://imagely.com/wp-content/staging/nextgen-gallery.2.2.20.zip
We’d like to get a few confirmations before we release it officially.
@cohistorian @aliarslangorsi – This issue resulted from a bug introduced by PHP. The consequence of the PHP bug were severe so rather than risk running NextGEN Gallery we were deactivating it.
We believe we’ve now come up with a work around. This copy of NextGEN 2.2.20 should run with any version of PHP (including the bugged versions: 7.0.26, 7.1.12, 7.2RC6, and 7.2.0). Feel free to give it a try and let us know if you have issues.
https://imagely.com/wp-content/staging/nextgen-gallery.2.2.20.zip
@paradime – I can understand the frustration. But does it seem correct to penalize us for a bug introduced by and in PHP itself?
As a side note, we’re about to post a patched version of NGG that works around the PHP bug. But with or without that, doesn’t seem quite right to penalize us for things that are effectively outside of our control…
Hey all – just wanted to post an update here. While the main original PHP bug was fixed in 7.2.0, there is a separate, secondary bug in PHP 7.2.0 that triggers similar symptoms. We’ve got a dev working all day, every day trying to pin down the bug, but we’re having to troubleshoot PHP itself and it’s not proving simple to find.
Once we find it, we’ll report the bug so they can patch it on their side, and that patch would then be included in PHP’s next release. Once we find the bug, we’ll also try to implement a work around for our side. If we can do that, we’ll push a release on our side immediately.
For now, neither us nor PHP has been able to identify the bug, so we’re still diagnosing. We’ll keep you updated.
@paradime – To review the situation. The main PHP bug causing issues was actually fixed in 7.2.0. Unfortunately, there is a secondary bug that’s still there in 7.2.0. We’ve got a dev on this all day every day trying to trace it, but we’re basically having to trouble shoot a deep, obscure bug in PHP, and it’s not proving simple to do. Once we find it, we’ll:
a) report it to PHP so they can patch it
b) hopefully be able to come up with a work around – whether we can do this will depend on the nature of the bug. If we can do it, we’d try to turn around a release more or less immediately.In any case, right now, the trouble is that neither we nor PHP have been able to clearly identify the bug that’s still causing issues in 7.2.0.
We will keep you posted.
@haydrionrayel – “PHP 7 is not problematic” – Quite to the contrary, the issues we are seeing here are CAUSED BY BUGS IN PHP. PHP recognized and fixed the main bug in 7.0.26 and 7.1.12 already. You can see our other post about this for links to the PHP site and discussion and patching of the bug by PHP. There is yet another PHP bug still present in 7.2.0.
And the bug in PHP were/is affecting systems well beyond NextGEN Gallery. Your point might be that many plugins aren’t affected by the PHP bug. That’s generally true, and great. But that doesn’t change the fact that the issues are are the direct result of a bug introduced in PHP that breaks some of PHP’s core logic.
Also, to clarify: there are only a few specific versions affected here, not all of PHP 7. It’s PHP 7.0.26, 7.1.12, 7.0RC6 for the main bug. 7.2.0 has a secondary bug that affects fewer people, but still has similar symptoms. Other versions of 7.0.x and 7.1.x work fine.
Hey all – Just wanted to clarify… 7.2.0 does actually resolve the original main bug. But unfortunately, it seems to introduces another one. We’ve got a dev working on this pretty much around the clock. Unfortunately, it’s complicated – we’re now troubleshooting a bug in PHP itself rather than NextGEN Gallery. We’ll need to identify it and report it to PHP. They’ll need to patch and release.
Once we do identify it, we’ll also be trying to see if we can come up with our own immediate work around for the bug. We won’t know if that’s possible until we can fully identify what the bug in PHP is exactly.
We’ll update when we can.
Ok, thanks for the explanation. It wasn’t clear that you’d rolled back.
We’re looking at this now. For us, 7.2.0 is working and we have not been able to duplicate any issues in the 7.2.0 release version. So we’ll need to see if we can do so, before we can try to fix it.
We’ll keep you posted.