The donation amount on the dashboard should change to reflect the updated amount for recurring donations using the fee recovery
complete
Jason Adams
complete
Happy to share this has been resolved in GiveWP Fee Recovery 1.9.8. Please update and let us know if you run into further issues!
Jon Waldstein
ready for release
Jon Waldstein
in progress
Kyle Johnson
under review
Ian Anderson
Kyle Johnson: Thanks for looking at this Kyle. Ideally, the payment_meta for Renewals should include "_give_fee_donation_amount" and
"_give_fee_amount" if the donor chose to cover the fees when updating their subscription amount. At the moment, the payment_meta for Renewals gives us no indication at all if the donor chose to cover the fees or not. Thanks.
Kyle Johnson
planned
Ben Meredith
under review
Our team is taking a look at this. This is a fairly edge-case issue that has only been reported once so far, so we'll hold off on prioritizing it until there are more reports of it being a problem.
Ian Anderson
Ben Meredith: Hi Ben. I appreciate you looking into this. Your support is great, but I struggle with the lack of resolution on many of the bug reports. This particular issue is significantly affecting our donation process since we send the donation amount to our accounting software. But because of this bug, we have had to disable the front end ability for donors to update their subscription amount. This has been reported to your team, replicated by your team, but according to your reply, looks unlikely to be resolved.
Ian Anderson
Ben Meredith: What's the point of having an "Update Amount" option if it doesn't change in the dashboard, and therefore we can't export the data for our reporting needs? Really frustrating.
Ben Meredith
Ian Anderson: We hear you for sure. This issue has been marked for the next cool-down (the last two weeks of an 8-week cycle) for the team to have a look. We just started a new cycle, so it'll be a month or so, but the team will definitely have a look.
Thanks for looping back around to this. We take your feedback seriously, and are always trying to balance the tension between new features, small edge-case bugs, and our limited development resources.