Support » Plugin: GiveWP - Donation Plugin and Fundraising Platform » The latest v2.5.x release branch causes Errors 500 in the Plugins menu

  • Resolved Nephalem

    (@nephalem)


    I have discovered another serious issue with the newest version of Give. When I install the Give Donation plugin into my WordPress, everything looks fine. But when I want to go to the Plugins menu in the WordPress dashboard, the list of installed wordpress plugins will never load and after 5 or 7 seconds later the webpage goes white in my browser and the Error 500 is displayed.

    Since that moment I canĀ“t install or uninstall any plugin in WordPress, because the Plugin menu never loads in my browser, it ends up with the 500 Error. The only solution is to remove the Give Donation plugin manually via FTP from the plugins folder in the wordpress installation.

    Now here comes the temporary solution: When I install the previous 2.4.x branch, (the latest 2.4.7), everything works ok in my WordPress dashboard.

    The newest 2.5.x branch is therefore inoperable on my site. I need your help.

    My config is PHP 5.6.40 and WordPress 4.9.10.

Viewing 1 replies (of 1 total)
  • Plugin Support Ben Meredith

    (@benmeredithgmailcom)

    Hi there,

    We’ve isolated an issue with Give 2.5.1 and users on versions of WordPress core older than 5.0 that is causing issues for some users.

    We are working to patch the issue.

    In the meantime, the only workaround is to either update WordPress itself to version 5.2.2 (which we recommend anyways for all of the GREAT diagnostic tools included in 5.2) or to temporarily roll back Give itself to an older version.

    If the Gutenberg editor included in 5.x of WordPress is the reason you’re holding off on updating, we’d recommend either the Classic Editor plugin or the Disable Gutenberg plugin to mitigate any issues with Gutenberg. That will get you the benefit of the imporvements to WordPress that have happened over the past months without worrying about Gutenberg breaking your site!

    We are definitely going to patch this issue very shortly, but I wanted to give a full picture of your workaround options.

Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this topic.