WPCharitable

@jozuakunn I wouldn’t remove any classes Charitable sets, especially on the donation form. Functionality and styling might rely on those classes. Increase the priority (number of ways to that, I’m sure you might be aware but if not please ask) would be my suggestion. ?? ????

@jozuakunn Thanks for reaching out. The template was “hardened” a bit so that bad HTML or JavaScript wouldn’t show through. I’ll share this information with the team and likely we will add a wp_kses type of filter (a filter already exists so that might be modified). Expect this change in an upcoming version.

Meantime the template that displays that is here:

/charitable/templates/donation-form/donation-amount-wrapper.php

Override this template by copying it to yourtheme/charitable/donation-form/donation-amount-wrapper.php (you want to remove the esc_html around the $legend variable).

That should resolve your issue. Let us know if you have any further questions.

@mrn007 Thanks for reaching out. Your screenshot (and request) seem to involve the Fee Relief addon which is a paid addon and there isn’t supported in the www.remarpro.com forums. Please reach out to the support for the pro plugin / addons at wpcharitable.com (‘support’ link at the top navigation). Thanks!

@heartenmade no problem at all. if you want to keep an eye out in the changelogs starting in the new year any updates will be mentioned there (and of course you can reach out to us).

Have a good weekend! And btw, that is a great site!

@heartenmade Thanks for the response and the info. It helped us confirm a few things.

What is happening is that because you are using more than one way via Charitable to insert an ability to open a donation form on the same page, some duplication of Stripe’s forms/code is happening and the CC field isn’t opening for the second one because of this. Having multiple Stripe forms on a single page is actually being developed/tested now – but there are few workarounds until this is ready for release in public:

1. You can have one of the donation buttons go to a page with the donation form.
2. You can create a custom button (insert the HTML into a template via another block, etc.) that would look like the same button but via JavaScript would click the single donation button on the site. We couldn’t test this on your site, but based on what we saw, this should be close (it’s PHP that inserts the JavaScript into the page, it’s the JavaScript that is key. Notice the custom CSS for the “fake button”: https://pastebin.com/j5tdquVa) If you haven’t inserted code snippets before, we recommend WPCode but any decent snippet plugin should be able to insert this.

Hope that helps. If you have further questions please let us know.

@heartenmade Thanks for reaching out.

Can you confirm what Charitable shortcodes (or other methods) you are using to insert the two buttons into the custom page/template (and if you are using a page builder, etc)?

Also if possible can you copy and paste the information in Charitable’s Tools->System Info into pastebin.com and share with us that link?

Thanks!

@charitieshelp thanks for the kind words. Appreciate your support and hope you continue to enjoy it into 2025. ??

Thank you for the kind words. We are glad you find the plugin amazing – thanks for the recommendation and thank for using Charitable! ??

@mabusasebobane Thanks for reaching out.

Can you do some things so our team can take a closer look?

1. First can you provide step by step instructions on what you’re doing to reproduce the issue? Includes exactly when it “freezes” (feel free to even seen a screenshot if there’s a UI or spinner then it “freezes”).
2. Can you also try the same steps with all plugins but Charitable (including page builders, etc.) deactivated and on a default WordPress theme?
3. Copy and paste the information in Charitable’s Tools->System Info into pastebin.com and share with us that link.

Thanks for saying the plugin is great, so let’s make this even better and try to see what might be the problem.

Thanks!

We are going to go ahead and close this thread for now. But if you’d like us to assist further, please feel welcome to continue the conversation.

Thanks!

@emgb_520 Charitable offers a “standard transaction” setting in PayPal settings when you activate it via the gateway settings, with the other choice being “donation” (Business account).

Hope this helps! Let us know if you have any further questions.

Hello @ukiukivalue – thanks for the reply. Yes, you can hide notices in that way and that’s a short term solution. If you just installed Charitable that’s an odd message because this usually means you installed an older version and the plugin is upgrading… or there is something in your system that is preventing (permissions, etc.) Charitable from doing something (even if that something is confirming an update is completed) and it’s caught in a loop. If that’s the case it might be difficult to troubleshoot from a distance unless we can reproduce.

Since you resolved it currently, i’m closing this ticket… If you revisit further and have additional information, let us know. Also providing us the additional System Info information we suggested Charitable’s Tools->System Info might give us insight. Our team will be on the lookout for any similar reports. Thank you!

@ukiukivalue Thanks for reaching out. Any message like this one would refer to upgrading some aspect of the code or database and not refer to upgrading a plan.

Initially I would recommend (make a backup first just in case, since what is causing this is currently unknown) turning off any caching AND temp deactivating any non-Charitable plugins THEN attempting to click on the message to see if that resolves.

Then if you can provide some additional information so we can look further, that will help us troubleshoot this. If you can copy and paste the information in Charitable’s Tools->System Info into pastebin.com and share with us that link.

In addition can you enable logging as shown on this page. Edit wp-config.php on your WordPress root directory and add:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

When you’ve done this, visit a few pages to generate the message and you can share the debug.log file that should have been generated (or share the errors in that file you see) with us. You can paste this into https://pastebin.com/ or https://gist.github.com and share a link with us.

Finally if you can provide some background in terms of when this message appeared – did it appear when you first installed Charitable? Did you preform an upgrade from an older version (maybe a year old version) of Charitable?

Thanks.

We are going to go ahead and close this thread for now. But if you’d like us to assist further, please feel welcome to continue the conversation.

Thanks!

@daaniilka Thanks for reaching out!

Charitable has been made compatible with the GDPR.

https://www.wpcharitable.com/charitable-1-6-user-privacy-gdpr-better-refunds-and-a-new-shortcode/
https://www.wpcharitable.com/documentation/charitable-user-privacy/

As the post notes by default, all personal data stored for donations made within the last two years will be retained. Personal data is not automatically removed when the data retention period is passed; it is erased when a user specifically requests to have their data erased. You can adjust the setting in the privacy tab.

Basic personal information is retained for tracking donations, reporting, etc. in Charitable (similar to how a name and an email address is kept when someone leave a comment on a blog). Tax and government record keeping are also reasons, depending on where your live.

The ability to add make the consent box required was added to 1.8.3.4 which was just released. You’ll find this setting in the privacy tab in Charitable settings. You can give that a try and let us know if you encounter any issues or if that matches what you were looking for.

Hope this helps. Have a good day!