Support » Plugin: Plugin Organizer » 9.3.2 HTTP 500 error

  • Resolved RK

    (@rirgang)


    Hi

    After update, get 500 error.

    Deactivating all plugins and enable again when activates the plugin oranizer back the 500 error.

    I read that the problem was appearing in 9.3.1 but for me it is still happening in the new version.

    • This topic was modified 5 years, 4 months ago by RK.
Viewing 7 replies - 1 through 7 (of 7 total)
  • I have a similar problem with the update. The website no longer appears, even after switching off the caches. After the rollback the website worked again.

    WP version: 4.9
    PHP Version: 7.0.25
    MySQL Version: 5.6.38
    Previous version Plugin Organizer: 9.2.3

    Plugin Author Jeff Sterup

    (@foomagoo)

    What is the error you are getting?

    Thread Starter RK

    (@rirgang)

    Hi Jeff

    In fact, he did not even have time to see if he had made a error. As the store was with promotions and visits starting in the morning… I tried to reactivate, gave 500 error, I decided to deactivate.

    What I saw is that it activates, it immediately has no more access nor to the admin. everything get http 500.

    Plugin Author Jeff Sterup

    (@foomagoo)

    What is the error message that goes with the 500 error? Every 500 error has a message telling you where the error is. You have to look in your server log.

    Plugin Author Jeff Sterup

    (@foomagoo)

    Have you changed the order of the plugins before? The only thing I can think of is that you hadn’t changed the load order before and now you are being forced to have the plugins ordered differently.

    Thread Starter RK

    (@rirgang)

    Really

    It had a 9.3 version in another store. I installed and in Load Order just saved (not change anything). I did the update to 9.3.2 and it worked correctly.

    I have never change in this order. Unfortunately I have not reached this level 🙂 I use selective loading and it has given a great result in speed with woocommerce.

    Thanks for the tip and congratulations for the plugin.

    Plugin Author Jeff Sterup

    (@foomagoo)

    I’ve released version 9.3.3. It prevents the recreate_plugin_order function from saving the active_plugins array if there are less plugins in it than when it was called. That will prevent it from deactivating plugins if that is what is causing it. I also added a filter call that removes the active_plugins filters before any code from the active plugins is called to prevent them from getting a bad active_plugins array and saving it. Which could also deactivate plugins inadvertently.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘9.3.2 HTTP 500 error’ is closed to new replies.