• Resolved dareadel

    (@h2ofilters)


    Version 2.21.0 Update broke my site until I installed and revert to the previous version. I forgot to write down the error message but it’s likely a database-related error message.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Hey there, I’m having the same issue. How to you find an older version to revert to?

    Thread Starter dareadel

    (@h2ofilters)

    Hello @gpbarone87,

    I simply restored my website from a backup 5 days prior to the update, then I updated each plugin one a time. I decided not to update Give before I tested the site again and it turned out to be the culprit.

    I am not sure how to manually revert to a prior update but I used the quick and safest option for me.

    • This reply was modified 2 years, 9 months ago by dareadel.
    • This reply was modified 2 years, 9 months ago by dareadel.

    @h2ofilters,

    Thanks for your insight. Your method is definitely the most thorough route.

    I had a strong feeling WPGive was the culprit, so I researched a bit I downloaded a plugin called WP Rollback and just rollbacked to the last version.

    That fixed it for me. Let’s hope the Plugin Author fixes this in the next update.

    Best,

    Yep the quickest fix is to use “WP Rollback” and set the GiveWP version back 1 step.

    Thread Starter dareadel

    (@h2ofilters)

    I believe by restoring the website I have no need for another plugin. Plus, it took less time to restore from backup than having to install and activate another plugin

    Plugin Support Rick Alday

    (@mrdaro)

    Hi folks,

    Just chiming in here. This issue was resolved in GiveWP 2.21.1.

    To give an idea of the issue, here’s what happened: GiveWP has an awesome new system for retrieving data from the database. It’s faster, optimized, and is being used to improve speed throughout the product. There was one place where a lot of data was being pulled all at once that wasn’t as optimized as it could have been, so on older MySQL instances, or shared hosting servers which have limited MySQL memory, it could throw an “out of memory” error. We tracked this down and made further improvements so it now takes far less memory and is even more optimized (and faster). This will avoid the memory issue.

    Before updating, be sure to make a full backup of your site. We recommend the backup plugin Duplicator.
    https://www.ads-software.com/plugins/duplicator/

    Here’s an article that walks you through accomplishing this: https://givewp.com/backup-for-faster-troubleshooting/

    We also recommend you first make these updates on a staging site before updating on your live site, to make sure everything goes smoothly.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Version 2.21.0 Update Breaking Site’ is closed to new replies.