• Resolved nerdymind

    (@nerdymind)


    Hello! When updating to GiveWP 2.29.1, I was hit with the following error:

    Fatal error: Declaration of Give\Framework\FieldsAPI\Concerns\ShowInReceipt::showInReceipt($showInReceipt = true): Give\Framework\FieldsAPI\Concerns\ShowInReceipt must be compatible with Give\Framework\FieldsAPI\Field::showInReceipt($showInReceipt = true): Give\Framework\FieldsAPI\Field in?***/wp-content/plugins/give-form-field-manager/src/FormFields/Fields/WPEditor.php?on line?19

    Rolling back to the previous version, 2.25.1, fixed the issue.

    • This topic was modified 1 year, 9 months ago by nerdymind.
Viewing 1 replies (of 1 total)
  • Plugin Support Matheus Martins

    (@matheusfd)

    Hi, @nerdymind.

    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.29.0 and Form Field Manager 2.1.0).

    First, if your site is broken, I would restore a backup of your site so you are up and running again.

    Then, I’d deactivate the Form Field Manager add-on, update GiveWP, update the Form Field Manager add-on, and then activate it again.

    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!

Viewing 1 replies (of 1 total)
  • The topic ‘Update 2.29.1 causes fatal error’ is closed to new replies.