Cristián Lávaque

Right, that is a fix because it removes what’s being wrongly parsed by whatever that’s doing it, but it’s still a parsing problem that’s not present in a new WP installation, so it’s added by a theme/plugin.

If you prefer to edit the button’s template, you can probably remove all HTML comments. And maybe all line-breaks too, since you may be getting those parsed into HTML BR and P tags.

Also remember that if you use the button’s full code in your post, instead of the shortcode, you’ll need a PHP execution plugin for the bits of PHP code there.

It’s better to have parsing working properly and use the shortcode with button encryption enabled. [hilite path]Dashboard -› s2Member® -› PayPal® Options -› Account Details -› Enable Button Encryption[/hilite]

I hope that helps. :)

Hi Jeremy.

I’m emailing Elizabeth in Accounts to send you that. :)

Hi Stephane.

Although the free registration pro-form doesn’t take payments, it’s part of the PayPal pro-forms, so that error comes up. You can just enter fake info in the PayPal fields it asks for, and the error will go away. [hilite path]Dashboard -› s2Member® -› PayPal® Options -› Account Details[/hilite]

If you ever want to use pro-forms/buttons for payments, you need to update those fields with the correct values.

I hope that helps. :)

Hi Michael.

Could you try using an other URL shortening service than TinyURL? [hilite path]Dashboard -› s2Member® -› General Options -› URL Shortening Service[/hilite]

I hope that does the trick.

Thanks for the update, Nordin. Glad you sorted that out. :)

Plugin looks fine. Looking forward to configure it today so I can start using it soon. Thanks

Let us know if you have more questions, we’ll help as we can.

No problem. :)

No, that page would not be secured, since it should be accessible to someone that doesn’t even have an account yet. If you protect it, the person will be redirected to the Membership Options page.

So, no, the free registration pro-form would not be safe there, but you can have there a link to the normal registration page, i.e. wp-login.php?action=register which, if you have registrations closed, will only work for someone that just checked out and was cookied by s2Member on return.

Thanks Andy. Sorry about the delay, I was waiting for you to let me know here that you had sent it and I didn’t notice the email, I missed it in the inbox that day and then it was just pushed out of sight by all the new emails.

I reviewed your pro-form, it looks fine. I looked at the logs and noticed no new tests since the ones you posted, so I did my own test purchases.

I checked out twice with Express Checkout and both times I was returned to the page with the pro-form and not redirected to the success URL. Also, no RTN log is being created, and the IPN log was not populated with the new transactions, only the API log got entries for my tests.

The URL PayPal sent me back to is basically:
http://yoursite.com/gold-membership/?s2member_paypal_xco=s2member_pro_paypal_checkout_return&token=EC-2TR72xxxxxxxxxxx

The [hilite mono]s2member_paypal_xco[/hilite] is “s2member_pro_paypal_checkout_return”, and [hilite mono]token[/hilite] is also there, it doesn’t look like there are vars missing.

I don’t know what’s causing this problem, so I emailed Jason asking for his insight. He may not answer right away, but I’ll let you know as soon as I hear back from him. In the meantime there’s something you could do:

I noticed a lot of plugins installed in your site, and wondered if one of them may be affecting the behavior in some way. As a test, could you deactivate the other plugins one by one, and do a test checkout after each to see if the problem continues? Or install a new WP with just s2Member, configure the PayPal integration and do a test checkout there. This test would be very helpful to determine where the problem may be.

Thanks for the kudos! You’re very welcome. :)

All those have this in the entry for their cancellation:

3 => 's2Member `txn_type` identified as ( `subscr_eot|recurring_payment_expired|recurring_payment_suspended_due_to_max_failed_payment` ) - or - `recurring_payment_profile_cancel` w/ `initial_payment_status` ( `failed` ).',

They were failed payments. :/

I’ve put in the PDT Identity Token.

Cool. :)

Hi Suhasini.

This behavior would be the same in s2Membe Pro.

So you want the user to only see his own groups or photos page, and not the other user’s, is that it? I’m afraid that’s not possible with the current URI restriction, since it works with Levels. Custom capabilities would allow you to customize access for each user, but that still isn’t integrated with the URI restriction (it will in the future).

Another thing you could do is hack your installation a bit so it checks if it’s the user’s own group/photos page and show it based on that or redirect him elsewhere.

I hope that helps. :)

Hi Kirk.

I don’t know how to make the PHP files with the Download Protection. Wouldn’t it work to just use a regular WP page for that?

If it has to be a PHP file then, instead of having it in the s2member-files folder, leave it outside, but include WP into it so you can use conditionals to check the user’s access. Knowledge Base » Protecting Non-WordPress Content with s2Member

I hope that helps. :)

Hi Tara.

You mean podcasts protected by s2Member based on the user’s access? Maybe this video helps: Video » s2Member® File Downloads (Remote Auth/Podcasting)