• Resolved fmgguy

    (@fmgguy)


    I also have 30+ other WP sites, some on this same server, that do not work and I have had to roll back to PHP version 5.6. Why does this one work, and those don’t? BTW.., I have read the post “PHP versions 7.0.26 and 7.1.12 have a known issue”, and the “Still problems with php 7.2” post.

    The page I need help with: [log in to see the link]

Viewing 15 replies - 1 through 15 (of 22 total)
  • Thread Starter fmgguy

    (@fmgguy)

    BTW, I am running NextGen Gallery Version 2.2.14

    Is v2.2.14 immune to the PHP 7.x bug? Looks like it does.

    Thread Starter fmgguy

    (@fmgguy)

    Please disregard. I have now switched the site to use Foo Gallery, as I am doing with all my WP sites.

    Plugin Contributor Imagely

    (@imagely)

    @kent-brockman – Versions of NextGEN Gallery after 2.2.14 (currently up to 2.2.18) have precautionary code implemented to test for the PHP versions we are aware of that may cause the site’s server to crash.

    Thanks!

    – Cais.

    ok @imagely, version 2.2.10 should work without issues, right? It’s currently easier to downgrade the plugin than to downgrade the server’s PHP version ??

    @kent-brockman you try it? Nextgen v2.2.10 works with “problematic” PHP versions?

    • This reply was modified 6 years, 12 months ago by aldon.

    Hi @aldon, v2.2.10 looks good. The site I’ve tested it in, is very simple. Just a couple thumbnails with lightbox…

    Thank you @kent-brockman. Anyone from nextgen support team to confirm that?

    Plugin Contributor Imagely

    (@imagely)

    @aldon – The relevant code in NextGEN Gallery has not changed in a very, very long time. The issue is with the PHP versions as noted and the bug that was found in it.

    In theory, you could use version 2.2.14 as it was the last release without the precautionary code disabling NextGEN Gallery although that is essentially the only difference between it and the versions currently released afterward.

    We are erring on the side of caution just in case, we do not want to see our users site’s crash because they are using NextGEN Gallery and a PHP version that has this bug.

    Thanks!

    – Cais.

    ok. FYI: v2.2.10 is working like a charm in the effected PHP versions. As a workaround, you should suggest users to downgrade the plugin version an link to a tutorial on how to do that. That’s better than having empty galleries due to a third party mistake ??

    v2.2.10 didn’t work for me. Upon activation, it immediately crashed a test site I tried it on.

    I’m not sure how much longer we’ll have to wait for a patch. An ETA would be nice. Today? Tomorrow? End of the week?

    While I recognize this isn’t completely the dev’s fault, I’m being forced to start the process of migrating sites away from NextGen and cancelling subscriptions.

    @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.

    @edanzer

    I appreciate your replies here and on other threads.

    I should mention that on some sites, we used Nextcellent and it’s working perfectly. Strange how Nextcellent works but NextGen breaks.

    Regardless, my phone has been ringing consistently over the past 2-3 days with clients upset, rightful so, that their galleries are gone.

    Some have demanded an immediate switch to a different solution and the rest are quickly growing impatient. After all, this has now being going on for about a week.

    The longer this drags on, the more likely we’re all going to abandon NextGen completely and our subscriptions with Imagely. Therefore, it’s important that an update/patch is provided ASAP.

    Once I start the work in moving them away from NextGen, there’s no coming back.

    Plugin Contributor Imagely

    (@imagely)

    @paradime – We do appreciate this is a significant issue and as noted we are working through the PHP code as that is where we see the problem.

    As it is, you should be able to temporarily downgrade to a lower PHP 7.x branch than those listed and/or PHP 5.6.x latest release without any significant issues and have the NextGEN Gallery installations in working order.

    You are also welcome to send us a Bug Report (https://imagely.com/report-bug/ … please reference this topic) so we can get a better look under the page at your site (or sites as the case may be if the issue is more complex in your instances).

    Please include as many details as you can and the issue at hand so we can move on this as fast as possible and/or include you for a future reference.

    Thanks!

    – Cais.

    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.

Viewing 15 replies - 1 through 15 (of 22 total)
  • The topic ‘I’m confused. I have a NextGen install that is working on 7.0.26’ is closed to new replies.