[nullsignature]

You guys are great! Thank you!

[nullsignature]

Yes, I would prefer to hardcode one of my own addresses as the primary recipient if that’s possible.

[nullsignature]

Hmmm. I need to execute some custom code when the button is clicked. What function/file is executed when this occurs? If I find that I should be able to make do.

[nullsignature]

Thanks for the responses. Is there a shortcode/function that can get the number of remaining downloads for a user?

[nullsignature]

Or I could just have the hook execute the upgrade. I really overthought that one.

Is there a hook for when a product is purchased, and then a way to get the product ID of what was purchased?

Here’s some pseudo code to demonstrate what I’m asking:

add_action(UpgradeMember, wp_estore_item_purchased)

function UpgradeMember($member, $product_id){

if($product_id == 3){

$member[membership_level] = “Plan 2”;

}

}

[nullsignature]

I want their subscription to expire from the original date of purchase, regardless of when they upgrade. It could be a week after they purchase or a week before they expire.

Plan 2 is the same as Plan 1, except it includes links to some digital downloads. So basically, by upgrading from Plan 1 to Plan 2, all they’d be doing is buying these downloads- not really buying an upgraded subscription with different access levels. I want to keep the digital download tied to membership (and not standalone products) due to how the site is structured and accessed.

Am I correct in that the shortcode [wp_eMember_upgrade_membership_level_to level=”#”] does not extend the expiration?

I’m thinking of using a hook that generates a random code for a user when they purchase that upgrade, then they enter that code in order to execute the upgrade shortcode. I just need a way to get the random code to the user. Does the post payment action add-on support variables in emails?

[nullsignature]

Thanks for the responses!

If two different memberships are added to a checkout cart and purchased, how does it determine which one will be primary?

[nullsignature]

Edit: figured it out. $member_data is an array that doesn’t need to be passed by add_action. Here’s my code for any future searchers. This inserts the newly registered user’s ID into a table called user_question_history.

function handle_eMember_registration_complete_event($member_data)

{

global $wpdb;

$wpdb->insert('user_question_history', array('user_id' => $member_data['member_id']));

}

add_action('eMember_registration_complete','handle_eMember_registration_complete_event');

[nullsignature]

Thanks! I’ll give this a shot.

[Author]

Posts