GiveWP Fundraising Plugin
Roadmap
Bug Reports
288
Powered by Canny

Bug Reports

Please Read before posting
Please reach out to support first so we can help you with your issue. Only the support team can post bugs to this board.
GiveWP should not throw deprecation notices for PHP versions 8.2 and higher and break the WordPress dashboard menu
As of GiveWP 3.17.0, GiveWP throws a lot of deprecation notices and even breaks the display of the main WordPress dashboard menu.
0
VFB forms generate Invalid Form ID error.
In subdirectory WP installations, VFB forms return an Invalid Form ID error and fail to record the donation in the backend.
1
[give_totals] shortcode should not cause an error or a massive slowdown of the page when a lot of forms are queried
The give_totals shortcode uses a nested query that slows things down significantly if the shortcode queries a lot of forms.
0
Entering a custom amount then pressing keys should not result in zeros being added to the amount
On desktop, when you enter a custom amount on any forms made using the Visual Form Builder, random zeros are added when you press “k”, “b” or “m” in your keyboard.
0
The Donate Now button should be visible when PayPal Advanced Credit Card fields are showing.
GiveWP version 3.17.1 introduced a feature that hides the Donate Now button when PayPal Donations is selected - the Smart Buttons are used to complete donations. When Advanced Credit Card fields are shown (so: the credit card fields show instead of the black debit/credit smart button), the Donate Now button is needed to complete a donation. Workaround: Please go to Donations >> Settings >> Payment Gateways >> PayPal Donations and change the Payment Field Type to Smart Buttons Only
0
Visual Form Builder + Fee Recovery Translation: The Strings “Cover Donation Fees” and “Ensures 100% of your donation reaches our cause” should be translatable
For VFB Forms with Fee recovery enabled, the strings “Cover Donation Fees” and “Ensures 100% of your donation reaches our cause” are not being translated. There is no workaround at the moment.
1
Visual Form Builder: Not Having a Meta Key in a Custom Field Block should not publish the form
Not having a meta key for a custom field block publishes the form but results in critical error on the front-end. This also results in a spinning loader on the Design tab in the Visual Form Builder.
0
Powered by Canny