Latest update (2.28.0) broke my website

Same here. Also urgent. Webpage is antisemitism.org

Really dismal performance – you should stop describing your plugin as robust. We were able to get our website back online by rolling back to a previous version. Please let us know when you have got a properly tested solution working but from now on we’ll be treating any plugin updates from you with extreme caution.

Hi, @donkrisho & @antisemitism.

Glad you reached out. I can help you fix this error.

We released a new version of GiveWP and Form Field Manager that fixes the issue you are facing (GiveWP 2.28.0 and Form Field Manager 2.1.0).

To fix it, you need to update both GiveWP and the Form Field Manager add-on. In this case, you can click on Plugins > Installed Plugins and click to update your plugins. If you do not see an update for it, it’s just the cache. You can navigate to Dashboard > Updates and click on Check Again. It will check for the updates and clear the cache and you’ll be able to update the plugin.

Before taking any steps for troubleshooting or updating, I highly recommend taking a good backup of the site you can confidently restore from. Having a backup of your site is essential to a solid workflow, and will allow you to restore to a previous version of the site if you run into any issues. You can read more about our top recommendations for taking a backup here: https://givewp.com/backup-for-faster-troubleshooting/

Your success with online donations is our number one priority. Looking forward to helping you get to the bottom of this!

I’m facing the same thing with my site but I can’t log in at all. Is there a place I can download these plugins and manually upload them to my site? I’m really stuck. I’ll have to manually remove these plugins if I can’t update them.

Current versions:

• Give – 2.28.0 (updated yesterday)
• Give Form Field Manager – 2.0.4 (not updated since May 3)

• This reply was modified 1 year, 5 months ago by davidpotter.

It is complete amateurishness, compounded by arguing over whether this constitutes “crashing” our website. Our website went from fully functional to inaccessible front end and back end thanks to you releasing an update which caused a “critical error”. Saying you crashed our website and probably many thousands of others, causing charities all sorts of costs to set things right is probably the most generous way we could have described it.

Since I paid for a Plus plan with GiveWP, I was able to log in to their site and download 2.1.0 of the Form Field Manager and then FTP it to my site which fixed my problem.

Hi, @davidpotter.

Putting myself in your shoes, I would restore a backup of your site so you are up and running again, receiving donations on your website.

Then, I’d deactivate the Form Field Manager add-on, update GiveWP, update the Form Field Manager add-on, and then activate it again. Some people needed to follow this process.

Can you let em know if it works for you? Also, since you are using the Form Field Manager add-on and is a paid user, you can reach out to our team via Priority Support here https://givewp.com/priority-support/.

Looking forward to helping you get to the bottom of this!

Hey, @davidpotter.

It looks like we were typing our messages at the same time! I’m glad you were able to upload the plugin and it’s working.

Next time you have issues, reach out via Priority Support and our team will happily help you.

Thanks for using GiveWP! Have a great day.

Hi Matheus

With respect, I’m not sure that you realise the seriousness of this. Like @davidpotter, our website was down both front and back ends. The issue appears to arise if core Give updates first and FFM doesn’t. It causes a critical compile error. I was eventually able to log in as an admin using WordPress recovery mode and then install the new FFM I’d downloaded from the GiveWP website.

There must be a significant proportion of the user base who have been affected by this.

Can a check be added to the core Give update to determine if FFM is installed and either warn or force update of FFM first?

Hi Matheus,

Thank you for also replying to me via email. Here is where I am at: The WP Rollback now worked, therefore, I could revert back to the old GiveWP version. Obviously, I had the FFM addon deactivated. Then I updated the core plugin, and it worked. However, I can’t update the FFM addon plugin – it shows v2.0.4, and no updates are available with WP updates page. I refreshed it several times, cleaned the server cache, cleaned the CloudFlare cache, it is still not coming up. Naturally, when I activate it, it crashes the website.

Am I supposed to wait for that FFM update to show up, or is there a link to download it and update manually via FTP? We are using several specific additional fields in a couple of donation forms.

Thanks!

Resolved. At the same time this problem occurred, my password didn’t work (we have your full plan, with all add-ons), and I made too many attempts to connect. So finally, I have reset it, and downloaded the FFM add-on, and installed it manually.

There were already some problems in the past (such as me spending 8+ hours manually setting existing recurrent donations with Stripe, because of an update bug). In this case, maybe releasing the updates which depend one on another (with the risk to crash websites) should be done in a timely manner, not as a bulk. I wasn’t frustrated at all when that previous issue occurred – it happens, I know something about it, but this issue – again – required hours of work, and the donations being down on the website for a moment.

Do I have to check if we missed some recurrent donations?

With give-form-field-manager 2.1.0:

PHP Fatal error: Uncaught TypeError: Return value of GiveFormFieldManager\FormFields\ValueObjects\FieldType::getFieldsApiType() must be of the type string, null returned in […]/wp-content/plugins/give-form-field-manager/src/FormFields/ValueObjects/FieldType.php:73

getFieldsApiType is declared to return a string and then the action_hook option returns an explicit null. Changing “null” to “”” (empty string) at least keeps it from exploding.