Support » Plugin: GiveWP - Donation Plugin and Fundraising Platform » Version 2.29.1 Gives me an error

  • Resolved calebprenger85


    This is what I see when the plugin is active:

    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 /public_html/wp-content/plugins/give-form-field-manager/src/FormFields/Fields/WPEditor.php on line 19

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Contributor Ben Meredith


    Hey @calebprenger85

    That’s certainly not what we want! Apologies for the slow turnaround on this reply. I’m hoping you’ve resolved this by now, but definitely here to help if not.

    The error you are seeing there is related to an older version of the Form Field Manager Add-on. Update to the latest version of that add-on (2.1.1) and the issue is resolved.

    Of course, you can only update to the latest version of a premium add-on if you have an active license. We’re technically not even allowed to provide support for premium add-ons here, so if you need continued support we’ll need to take this to a different channel at

    For that reason, I’m marking this issue as “resolved” but definitely reach out there if it’s not.

    In the meantime, deactivating the Form Field Manager add-on will resolve the problem.

    Thank you for giving the steps to correct this problem. HOWEVER, for me it shows that GiveWP could do better with its programming guidance. This error could have been caught in code and instead of a website wide PHP fatal error, your code could have looked for the condition caused by Form Field Manager and instead given a softer notice, one that warned of the need to update that plugin; or, not updating the main Give plugin unless the Form Field Manager plugin was updated first; or, …(your developers should be able to come up with a better outcome than what you have now).

    Crashing a website because your coding standards don’t catch a fatal error and deal with it effectively is a red flag.

    I hope you can change your programming policy/guidelines to avoid this in future releases.

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