Support » Plugin: GiveWP - Donation Plugin and Fundraising Platform » Fatal error: Uncaught Error: Too few arguments to function

  • Resolved Paul H. G.

    (@paulhengold)


    Fatal error: Uncaught Error: Too few arguments to function Give\Revenue\Listeners\DeleteRevenueWhenDonationDeleted::__invoke(), 1 passed and exactly 2 expected
    in /var/www/vhosts/domain.com/httpdocs/assets/plugins/give/src/Revenue/Listeners/DeleteRevenueWhenDonationDeleted.php on line 32

    Call stack:

    Give\R\L\DeleteRevenueWhenDonationDeleted::__invoke()
    call_user_func_array()
    assets/plugins/give/src/Helpers/Hooks.php:37

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

    (@benmeredithgmailcom)

    Hi @paulhengold

    Can you give me a bit more context for where you are seeing this error?

    It looks like you are trying to delete a donation, and then seeing that error. Is that correct? If not, can you give me the steps you took before you saw that error?

    I’d be interested in seeing the rest of that call stack shows.

    Here’s what I can tell you about that error from what I see there: it is saying that some function calling delete_post in the context of a donation is only sending 1 parameter instead of 2. All of the instances of that function in GiveWP code should be calling with two parameters. So if you have some custom code or something calling that function, it might be causing the problem.

    We’re more than happy to help!

    Plugin Contributor Ben Meredith

    (@benmeredithgmailcom)

    Hey @paulhengold

    We’ve gotten several reports of this error now, and are looking for a way to reproduce it. Any tips you can give on how to make that error happen would be great. Here’s where you can see the latest on the issue: https://feedback.givewp.com/bug-reports/p/givewp-should-not-be-throwing-fatal-errors

    Because we’ll be keeping track of the issue over there, I’m going to mark this post as resolved. You can stay up to date on the issue at that link!

    Thanks!

    Plugin Contributor Ben Meredith

    (@benmeredithgmailcom)

    Hey @paulhengold

    We isolated the issue here. Updating WordPress to version 5.5 resolves the issue. For more detail, see the link in my previous message.

    Thanks!

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