some subscribers are not assigned the right l

When I have upgraded a subscriber by hand (as they are showing as paid at paypal but not on system) to a level member they are not assigned a Paid Subscr. ID, Does this matter?
If they are not assigned a Paid Subscr. ID, then s2Member will not be able to process cancellations or payment failures from PayPal. Normally s2Member receives IPN messages from PayPal indicating that someone’s payment failed or they canceled their recurring subscription.

When this happens, s2Member receives the IPN message from PayPal, searches the users for the matching Paid Subscr. ID, and then processes that s2Member account based on your settings in Dashboard -› s2Member® -› PayPal® Options -› Automatic EOT Behavior.

So, if you want that integration, you will need to make sure the user’s account has the matching Paid Subscr. ID and the payment gateway (e.g., PayPal) selected on their account.

Hi we are still having trouble with signups. Some go through ok while others are not assigned the correct level. I am investigating if this is only occurs if they are upgrading from free membership. I cannot reply to the last thread so have requoted your reply above. Where do i find the Paid Subscr. ID to add to the members I upgrade by hand? Also why are some getting assigned automatically but others are not? It is getting frustrating for the user and me that I have to let this fail, then they report it, then I have to do it by hand.

Where do i find the Paid Subscr. ID to add to the members I upgrade by hand?

You can find it on your PayPal account by viewing one of the payments from that member, or on your PayPal Recurring Payments Dashboard. The Paid Subscr. ID is the PayPal Transaction ID or Subscription ID.

Also why are some getting assigned automatically but others are not?

That’s hard to say without more information. Do you have logging enabled (Dashboard -› s2Member® -› PayPal® Options -› Account Details -› Logging)? The log files might shed some light as to what’s going on. You can search the log files by the Paid Subscr. ID to look for events related to a transaction that you think didn’t go through properly.

Hi Raam,

It seems from doing some investigation that if somebody signs up they get given the right membership level. However if somebody upgrades they are left at subscriber. Shall i send you the error log or is there a setting i am missing to allows this?

Marcus

Marcus, was the user logged in when he paid the upgrade? He needs to be logged in to the account that’ll be upgraded when he loads that page with the s2Member shortcode for the button/pro-form.

Could you do a test upgrade for 1 cent while logged in to a test subscriber account to see if you can reproduce what the user reported?

Hi Cristian/Raam,

Right from looking at the logs I think I know the cause of issue. The site was set up on a test domain address. (s15XXXX435.websitehome.co.uk/burrelleducation/ Then it was transfered to the live address: http://www.burrelleducation.com

This has caused members who bought items in the shop or signed up to a membership to be assigned the old test domain address and cause this error:

0 => ‘IPN received on: Mon Aug 6, 2012 8:43:00 pm UTC’,
1 => ‘s2Member POST vars verified through a POST back to PayPal®.’,
2 => ‘Unable to verify `$_SERVER[“HTTP_HOST”]`. Please check the `custom` value in your Button Code. It MUST start with your domain name.’,
),

Now all new members are assigned the right domain as this is now set in the custom field.

However members that have (curiously bought things from the shop (These are also logged in the s2member log)) but also signed up for previous memberships have no domain in their custom field showing but must have it stored as the old domain.

To fix this do I add the right new live domain to all members in their custom field in the PayPal section (i.e. all the subscriber members who signed up for free) so when they upgrade the system will use this and correctly assign them their membership as the domains will match?

Marcus

Right. That would definitely cause the issues you’re experiencing.

A few things to keep in mind:

1) Any buttons that you generated on the test site should be regenerated on the live site to ensure they’re generated with the correct domain in the custom=”” attribute.

2) Anyone who signed up for a recurring subscription with a button that had the wrong domain in the custom=”” may still have that wrong domain associated with the subscription on PayPal’s end. To the best of my knowledge, when you use a PayPal button to create a subscription, PayPal stores all the settings of that button on their servers and uses those settings for future messages related to that subscription. So, if someone signed up with a button that had an incorrect custom=”” attribute, the only way to fix it is to have them cancel that subscription and create a new one using the correct button.

3) The s2Member upgrade/downgrade process that occurs with a Billing Modification form works by canceling the previous subscription and creating a new one. So, if an existing member used a bad button to sign up, but then upgrades using a good button (i.e., a button with a correct custom=”” attribute), the old (bad) subscription profile will be canceled and replaced with a new (good) subscription profile.

I’m fairly certain that the custom=”” attribute in a signup button/form overrides whatever is in the Custom Value field on their profile, but it certainly wouldn’t hurt to update that field on their profiles with the correct value.