Unable to create donor accounts on a donor's behalf - even when I log out, and create a donation in someone else's name and email address, it still comes up with my own, and I get the receipt. Is this a bug, or a program failure? I cannot see how to get round this at all. All I want to do is create and generate a receipt that goes to my donor and it seems impossible!

Having secondary sorting parameters would be helpful when using shortcodes and blocks. As an example: The current [give_form_grid] shortcode has the ORDERBY parameter. The options are date (default), title, amount_donated, number_donations, menu_order, post__in, closest_to_goal. If you chose the amount_donated parameter, forms with the same amount donated are then sorted alphabetically from Z=>A, with no option to change that. Have a secondary sort parameter would allow users to have control or that.

As an admin, I'd like to use AsianPay with GiveWP.

Settings should have the option whether or not to add the Fee donated to the goal amount

As and admin, I'd like to have a reset password link displayed in the donor dashboard, so that registered users can access that efficiently while in their dashboard.

As an admin, I want to add additional custom fields on the donor dashboard.

Currently, renewals have a generic Opportunity Name of "Donation #donationId (Recurring Installment)". As an admin, I would like to be able to customize this. The current snippet to modify the Opportunity Name does not work for this purpose: https://givewp.com/documentation/add-ons/salesforce/sending-custom-data-to-salesforce/

As an admin, I'd like to create more custom recurring periods to allow donors to choose what is the best option for them. As an example, I could have a subscription to charge people for every 10 days, or for every 15 days. Being able to create my own custom periods would allow me to create the best subscription options for my users.

As an admin, I want to automatically follow up with donors who abandoned their donation so they are more likely to complete it.

Currently, when site admins set the form to use custom currency amounts (not the exchange rate) on individual levels, while also using 0 as the number of decimal places, switching the currency overrides the decimal settings and displays zeros. If not using the exchange rate, there's no need to override the decimal places.