WPCharitable
Forum Replies Created
-
@nameless_dream Thanks for reaching out.
Our instructions for Paypal setup are here. See if you can follow these: https://www.wpcharitable.com/documentation/setting-up-paypal/
We recommend PayPal business accounts so you can get access to certain features. If you can get IPN with personal account in theory it should work but you can also look at these troubleshooting tips: https://www.wpcharitable.com/documentation/paypal-ipn-troubleshooting/
@kalymastudio in attempt to display and more meaningful error message, can you add/enable WP_DEBUG_DISPLAY so that instead of the generic WP error display in the ajax reponse we can get something more detailed?
This would need to be added or placed in your wp-config.php:
define( 'WP_DEBUG_DISPLAY', true );If nothing changes, then the php error reporting settings for PHP or the server might need to be double checked. Thanks!
@kalymastudio Thanks for the information.
- I can pass along the deprecated function notices to our team, but these are notices and not errors (technically) so they shouldn’t be a result of the 500 you reported.
- Just now we attempted to reproduce the issue with the link you provided with Stripe and got a “missing keys” message which prevented the form from being submitted to test for the 500. Is it possible for you to set settings so we can see the 500 for ourselves?
- Was there anything else in the debugging logs (or anything your hosting company might be able to provide, hosting support usually has additional debugging files beyond the debug.log that WP_DEBUG can generate) that was documented at the time of you experiencing the 500 in the ajax?
- You said “it worked” before the PHP 8.2 update – do you mean there was no 500 or are you referring to the messages you shared in the log?
- We still want to confirm you deactivated ALL non-Charitable plugins (leaving only Charitable activated) AND switched to a default WordPress theme, cleared cache, and tried the form.
We were hoping to rely on error logs to give us a specific error message to work with, so this is very odd.
@kalymastudio thanks for reaching out. If you are getting the “Your donation could not be processed. Please reload the page and try again.” message and seeing an issue in the ajax request, then based on what you’ve done already the next step would be to enable debugging on your site to get more detailed reports in debug.log on what is happening during that time. You might also want to check with your host if they have made more detailed error logs as well (make sure the host isn’t blocking any outgoing communications to payment gateways). Finally in your tests – test both logged in making a donation and without.
@haroonahmad At first glance, I would check with Elementor documentation or support since that text is appearing within Elementor code when we do a view source of that over there. I hope this helps!
@haroonahmad When you say it doesn’t work, have you confirmed (after clearing any cache and confirming you placed the file in the correct place in your child/current theme) that your template is actually being used (do you see the link in the source code)? If not, then walk through where you are seeing the donation button on your site with urls to make sure we are talking about the same button/location. Thanks.
I’m 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!
@haroonahmad Thanks for reaching out.
In theory, you can change the donation button on Charitable’s campaign pages. Depending on Charitable’s settings, the button can launch a modal window or submit a form on a campaign page that brings the user to Charitable’s donation page. A template and some custom coding can change the behavior and you can add a button to link externally. Here’s the template in the Charitable plugin (which you would copy in your child theme, instructions in the comments of the file):
/charitable/templates/campaign/donate-button.php
Of course with this method Charitable wouldn’t be auto managing your donations or much else outside of the campaign landing page.
Hope this helps!
@marco203 Agreed that the error message is coming from Charitable but that shouldn’t continue to happen if you did a new updated install. Sadly it’s not something we can troubleshoot well without access (which you can provide to us securely at the previously provided link – don’t ever share access info on these forums).
We don’t like mysteries – and you’re probably correct that there is another issue whose effects were the error message. Feel free to reach out and we can have someone look into this. Have a good rest of the day!
I’m 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!
@marco203 Thanks for the response.
So this is getting more odd, because if it’s the same error then that file if it was missed should have been added in any new zip install. The only our possibility might be that there is some sort of permissions issue for that file/folder on your server (it’s impossible for us to test this currently, although your host might be able to confirm if you share with them the error).
Regarding deactivating Charitable: It seems like you have admin access. If you don’t and you have FTP access you can simply pull the plugin out of the plugins directory to deactivate it – this effectively deactivates the WordPress plugin and gives you access to your site. This is an online guide that goes into this in detail:
If you don’t have FTP access, check with your hosting control panel or your hosting support. If you don’t have much experience with FTP or don’t know a developer who can do this for you, your hosting support should be able to do remove/deactivate the plugin as well.
In any case once Charitable is deactivated you can reach out and privately share access information with us via this form and we can repeat the install and determine if/why this error is still happening and confirm via FTP in your system, but please try the above steps first.
@marco203
Thanks for reaching out! Seems like there is a missing file inside the Charitable plugin for some reason – did you move or copy the plugin from another location? In any case since the plugin is 1.7.0.4 we highly recommend you update to the latest version. We would recommend you deactivate the current version of Charitable and from there update to the latest. One way to do this is by downloading the zip from ww.wp.xz.cn:
https://downloads.wp.xz.cn/plugin/charitable.zip
…and preforming a manual update (so you can confirm the latest version is overwriting 1.7.0.4). At the same time you should have no fatal errors involved missing files (which wasn’t something that was an issue in the past oddly enough).
If you don’t know how to uninstall the plugin or if it’s preventing site admin access your host should be able to assist (or we can help as well if you share access, but you should try the host first). Let us know if we can answer any additional questions.
I’m 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!
@fixing2022 happy to hear that… especially since that wasn’t Charitable code (something to note – just remember your theme might be producing that area). Have a good day!
@fixing2022 without access to your site, hard to say why that snippet might not work. We would suggest going with the first option, and here’s more about translations on our site including a bit more details on some more options and Loco Translate.
https://www.wpcharitable.com/documentation/translating-charitable/