Membership 2 Pro: 500 Error After Updating Settings

After editing the payment processor options (Stripe) in Membership 2 Pro, the site returns a 500 response. I've temporarily renamed the plugin folder to membership_

I've granted support access.

  • Adam Czajczyk

    Hello David,

    I hope you're well today and thank you for your question!

    I accessed the site and took a "look around" but I didn't risk enabling the Membership 2 Pro plugin again because in case it took the site down I wouldn't be able to revert that using only a support access.

    I can see though that the WP Memory Limit is already set to 128M which should be enough so the next step would be to give it another try but with WordPress debugging enabled. To do this, please:

    1. add following lines to the "wp-config.php" file of your site

    define('WP_DEBUG', true);
    define('WP_DEBUG_LOG', true);
    define('WP_DEBUG_DISPLAY', false);

    Make sure please that these lines are located above the "/* That's all, stop editing... */" line in the file.

    2. Then try replicating the issue and after it happens check for the "debug.log" file inside the "/wp-content/" folder of your server. If it's there, please download it, rename to "debug.txt" and attach to your response here.

    Hopefully this will give us a clue on what is happening on the site and causing the issue.

    Best regards,

  • Dimitris

    Hey there David Meindl,

    I trust you're doing good today and please excuse our late reply here, it's been quite busy in our forums lately and we try to follow up each single thread here!

    If you attempt to reach website after the frozen state and get the error 500, there's still no /wp-content/debug.log file created?
    Please advise!

    Could you please try to activate Chrome's dev tools to get any console error whilst updating the Stripe API keys? Please let us know about any messages there.
    Here's official documentation site about Chrome's dev tools

    If all these steps comes down to nothing, could you please try to deactivate all other plugins, revert to a default theme like TwentySeventeen and try once more?
    If this resolves the issue, please continue by enabling them back one-by-one and change API keys each time until you get the conflicted combination.
    Here you can find a nice flow chart that can help you with the conflict test
    (just scroll down a bit to see the image)

    It also seems that the support access period has expired (it auto-expires for security reasons).
    Could you please re-grant it for us via WPMUDEV Dashboard plugin?

    Warm regards,

Thank NAME, for their help.

Let NAME know exactly why they deserved these points.

Gift a custom amount of points.