WPCharitable
Forum Replies Created
-
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!
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!
Hi @krutiw29, thanks for reaching out.
Although it sounds like you might have stumbled on it already, I do want to make sure you know about Charitable’s PayPal troubleshooting page:
https://www.wpcharitable.com/documentation/paypal-ipn-troubleshooting/
You didn’t mention if PayPal got the donation/payment, so as the document above asks – was there any information gleamed from the donation logs? Did you manually update the IPN and double check settings on the Paypal side? Other reminders:
- Verify that the PayPal account you are using has a verified email address.
- Check that PayPal is receiving payments in the same currency as Charitable is set up with.
- If you have a firewall plugin or the Bad Behavior plugin installed, try disabling them temporarily to see if the issue persists.
- Check your permalink settings under Settings > Permalinks. If you are using a Custom Structure that starts with index.php, this is likely to be the issue.
If all of this was done and confirmed, the page above notes:
“If the IPN notification was not successful, it may mean that your web hosting server needs some upgrades; the email you received should have included more details about that.”
Before you turn to the server to investigate, I would suggest the following:
- Enable WP_DEBUG and WP_DEBUG_LOG to catch any possible errors as you further test: https://developer.ww.wp.xz.cn/advanced-administration/debug/debug-wordpress/
- Deactivate all addons and plugins outside of Charitable itself, and attempt a test with a legacy/simple campaign. This includes deactivating Elementor.
- Switch to a default WordPress theme and attempt a test.
- If by now things still haven’t been successful, conduct another test with the PayPal test tool. If the results are the same, see if there’s anything in debug log generated (via step 1 above) that indicates an error or communication issue with PayPal.
Hopefully this helps troubleshoot or narrow down the issue.
@parthgohel001 I’m going to go ahead and close this ticket here because (1) as I mentioned this isn’t the forum for support for paid addons and (2) we have already a communication thread (in fact we just sent you something!) and didn’t want our response times effected by maintaining conversations in more than one place. Thanks!
@diabolikom thanks for reaching out!
While you can update the wording of the suggestions in Charitable settings (if you are using the visual builder for example, go to the settings tab and select the “donations” section to update the amounts and descriptions), there are options to translate these if you are using multiple languages on your site (or other reasons).
- You can use a translate plugin like Loco Translate. We have a page on our site that talks about translations.
- If you have a developer or if you are comfortable working with a little code (or use the WPCode plugin) you can modify the output of the suggestion donation descriptions with this code snippet: https://library.wpcode.com/snippet/rod9n3w2/
I hope this helps answer your question! 🙂
Thank you!
@myntillae – Thanks for the update! Our team attempted to do a few tests and didn’t see the issue either. For now, I will close this ticket but if you see any problems again or if you have any questions feel free to resume this conversation. 👍🏻
@parthgohel001 – thank you for reaching out. Our team is aware of this notice in the Amassadors addon but because this isn’t an error but a notice for future versions of PHP the addon will continue to work as-is. The next release of the addon is planned to remove several notices including the one you mentioned. In the meantime you can not sure the message by turning of debugging display (via setting WP_DEBUG_DISPLAY to false in your wp-content.php which this document details).
Since you are referring to a paid addon supported by a license (and not the core free/lite plugin itself that is available via the WordPress plugin repo), please direct support questions for this to Charitable support system on the site. Once a release date for an update to Ambassadors addon is available or date known, our support team can reach out to you via this support system.
Thank you!
Hi @myntillae – we also observed some text in the AJAX channel for your donation forms that might allow donations to go through but produce an error message similar to what you saw.
Make sure the WP_DEBUG_DISPLAY constant in your wp-config.php is set to false. Also make sure any plugins that might be turning “Debug mode” for WordPress on (especially for display, regardless of other settings) is set to “display logs” off (or deactivate the plugins to see if the problem persists). It’s rare, but sometimes a developer or hosting has these settings on in a production environment. If you need assistance with this in particular feel free to reach out to us and share temp admin credentials privately and securely and we can guide you to do this.
Hi @myntillae – thanks for reaching out.
Can you confirm what version of Charitable you are using? If you recently updated to Charitable 1.8.1 can you check to see if there are any notices to update database tables in your WordPress admin? There should be a message appearing at the top of your admin area? Thanks.
@sccr410 I wanted to follow up on this – our team has a fix in the upcoming 1.8.1 release for receipt pages for block themes like the default Twenty Twenty-Three and Twenty Twenty-Four. If you would like a patch you can contact us (because it would likely involve sharing sensitive information), otherwise in the coming days that fix should be in core. Either way, if that doesn’t help let us know but since we can confirm the issue the fix exists I’m going to close this conversation as resolved at the moment but you are still free to continue the conversation.
@sccr410 Thanks for reaching out and providing the additional information. First thing to check is your WordPress theme in your test – if you are using the Twenty Twenty-Four or Twenty Twenty-Three WordPress theme, switch to any other default WordPress theme (like Twenty Twenty-Two), reset permalinks, and then attempt the same test again and let us know the results.
If nothing changes, if you can provide the same screenshot and we’ll go from there requesting some additional information (gateway being used in the test, if you are in test mode for the gateway, donation form settings in Charitable settings, and your exact permalink settings). Thank you!
Thank you! 🙏🏻
@rosbiffer we got your information and since you are a paying user, we will follow up with paid support and close this ticket so we can keep all information that also includes some confidential information in one place. Thanks!
@rosbiffer It appears that a fatal error is preventing the CSS to load which is causing the campaign to obviously not look right. Since this might be depending on your site setup if you want you can share your site credentials with us securely our team might be able to double check a few things more quickly. Mean time since this is the first time we’ve seen this bug to my knowledge I’ll definitely share this with the team and pass along anything as soon as I hear form them.
@rosbiffer thanks for reaching out!
Since the last mention we have discovered a bug involving embedding and we plan to incorporate the fix in the next version of Charitable.
Meantime, you can use the Charitable Campaign block or the campaign shortcode to embed a campaign on a new or existing page (which is what the embed wizard was going behind the scenes).
For example this is the shortcode for a campaign (with a ID of 123 – you can see the ID when you cover campaigns in the campaign list in the WordPress admin).
[campaign id=”123″]
Hope this helps. Let me know if you have any further questions.