WPCharitable

@nwdco Thanks for reaching out.

Can you go into more detail on this issue?

Can you share the step by step process you used to export data for donations? When you say “it’s not being fetched now” does that mean the column is being displayed empty, or the column isn’t being displayed at all (or only for some). When did you observe this stop working?

How was the Pan Number added to the donation form initially, and is there a reason why i’m not seeing it as part of the donation form now? Where is this being entered?

The donation export feature CSV should only export the basic donation information, and Pan Numbers might not be included in this especially if the information is never entered on the Charitable side to begin with (if it’s entered in your payment gateway it might not be stored by Charitable or a part of the export). But with some additional information we can clarify and confirm a few things to better respond. Thank you.

@exposurefoundry Let’s try a different approach. Paste this code snippet into the functions.php of your active theme (be careful to copy this as-is, otherwise you might get a fatal or major error for typos).

add_filter( 'charitable_donation_form_fields', 'test_charitable_donation_form_fields', 10, 1 );
function test_charitable_donation_form_fields( $fields ) {
	$fields['donation_fields']['legend'] = 'Select your sponsorship amount';
	return $fields;
}

I confirmed this works in our standard testing environments.

Hello @exposurefoundry,

You can change the donate button text in one of two ways.

1. First off without coding you can use a plugin like Loco Translate (https://ww.wp.xz.cn/plugins/loco-translate/) to locate and change ‘Donate’ string.
2. Look in the templates/donation-form/ folder at the templates that exist in there. It sounds like you might be looking for donation-amount-header.php or donation-form.php. If you modify these templates you need to copy and paste them into your child theme first (example: copying to yourtheme/charitable/donation-form/form-donation.php).

If you don’t find the text in either method clarify exactly what text you mean and we’ll try to put you in the right direction. 🙂

@steph-n you’re welcome! I’m going to close this ticket but let me know if you have any more questions from what we discussed and our team will have the adjustment in the next release of Reach as we discussed.

@steph-n thanks for sharing that link. I did a view source and saw where the website stopped after about 53 lines of code.

<style>@media screen and (min-width: 50em) {
	.site-navigation{
		margin-top: NaNpx;
		margin-top: 

Although an error log out help, I can determine at least where your theme is stopping. The code is located in this file in Reach:

/themes/reach/inc/class-reach-theme.php – around line 732.

		public function setup_header_styling() {
			$offset = get_transient( 'reach_navigation_offset' );

			if ( ! $offset ) {
				return;
			}

			?>

It looks like some value involving navigation offset wasn’t pulled from the database. Short-term you can prevent this function from causing the fatal if you add “return;” to line 723 (right before the if “( ! $offset )” line. Don’t forget the semi-colon after “return” (no quotes):

public function setup_header_styling() {
			$offset = get_transient( 'reach_navigation_offset' );
                        return; // add this.

			if ( ! $offset ) {
				return;
			}

			?>

Again, error logs would be helpful but based on looking at what we have so far this is our guess and i’ll take this to the time to see if they can apply a better patch for Reach and publish an update.

• This reply was modified 3 years, 2 months ago by WPCharitable.

Hi @steph-n,

So when you say “3rd time” are you saying things are normal… then it you get a grey screen… where? On the front end of the site, are you able to access the admin screen? This sounds like a fatal error (but random or when something in particular happens, otherwise you would get it and it would stay that way)… it could be you did nothing at all… this could still be a conflict, an update on your server (PHP), or something else.

The best way to determine what’s going on is to turn debugging on for your site. Mainly you can do this by adding WP_DEBUG and WP_DEBUG_LOG to true in your wp-config.php and looking at the generated log to see what (likely a fatal PHP error) it is reporting and go from there and share that particular error here.

Here’s a link that goes into debugging in WordPress and WP_DEBUG in particular: https://ww.wp.xz.cn/documentation/article/debugging-in-wordpress/

Your host might also have ways to log errors or be able to turn on logs and go through logs for you.

Sounds good @taxick. I’ll still rely this conversation to our team to see in the future how we can get customizations through their API.