Bug passing metadata direct_stripe_before_success_redirection

Hi, thanks for your reply (and for the great plugin).

Unfortunately, I no longer have access for debugging purposes to the installation where I installed the custom function. (Actually, that installation no longer exists, as it was a staging site that the client decided to remove. I don’t have access to the live site’s filesystem.)

Before I wrote you, hoping that you might already have a solution in hand to this problem, I did test to make sure that $post_id and the other four variables were available. I also made sure that I could pass a string to the metadata key-value pair, and in fact pass one of the five variables. I used $button_id because I could also set its content dynamically in functions deploying the Direct Stripe shortcode.

So, my kludge looks like

1. Add shortcode via filter function with dynamically updating button_id
2. Save button_id to Stripe object metadata

In the latter, as per my initial example, the string “Sample Post” saved as variable $sample_post_title could be passed to Stripe as metadata.

$post_id, received via the direct_stripe_before_success_redirection action could also be passed through and saved to the Stripe Object.

But, $sample_post_title as in $sample_post_title = get_the_title( $post_id ); or in any other function based on $post_id failed in the manner indicated, producing the $token over on the Stripe dashboard under metadata, instead of the expected content. As mentioned, it’s also possible to save $button_id as received to the Stripe Object.

At this point, I’m asking as much out of curiosity and for possible future use of the plugin. Are you able to save dynamic variables to the Stripe Object using your action?

Simplifying what I was trying to accomplish (which wasn’t really very complicated):

/**
 * SAVE POST TITLE AS METADATA TO STRIPE OBJECT
 */
function add_post_title_to_stripe($chargeID, $post_id, $button_id, $user_id, $token) {
	
	$title = get_the_title( $post_id );
	
 	//Retrieve Stripe Charge and update it
 	$ch = \Stripe\Charge::retrieve($chargeID);
 	$ch->metadata[title]=$title;
 	$ch->save();
 
}

add_action( 'direct_stripe_before_success_redirection', 'add_post_title_to_stripe', 10, 5 );

Every time I tried anything like the above, I’d get the token over on the Stripe side.

That makes sense, although it doesn’t completely explain all of the behavior (why the functions return the token instead of NULL or FALSE or empty, for example).

Needless to say, I haven’t examined this matter to the same depth that you have. I’m not sure whether there are other methods conveniently available for passing information to the Stripe Object.

What I did with $button_id qualifies as a hack, since I’m using the button’s html ID to store data. I’m not sure my explanation above was clear, but I wrote a function that prints the shortcode to post content, with the $button_id set dynamically using the post object via WordPress functions.

It occurs to me that I could store a long string in $button_id, with elements separated by one or another special character, then explode it as an array, and get the data I wanted that way. So, the html would show something looking like id="Made_Up_Title|1029876432|10" etc.

Having data attributes to work with would be a lot cleaner. Or maybe you could save the data to a cookie – which might be a little more complicated initially, but would be more correct and potentially more flexible.

I can’t test these alternatives easily now, since I no longer have access to the installation I was working on, and I don’t have a pressing need for this – although I do see people working with Stripe more often than I used to, so may be returning to this matter again in a practical context. I’ll be curious to see what you come up with!

• This reply was modified 8 years, 2 months ago by CK MacLeod.