Cristián Lávaque

Hi Christopher.

You mean having Google Checkout as an option in the PayPal pro-form? I’m afraid that’s not possible yet, but we have it in our to-do. You can have a Google Checkout button in the same page as the pro-form, though, it wouldn’t cause a conflict.

About making it possible to customize the order in the pro-form so you don’t need one per plan, this is also in our to-do list. For now, one way to use the same pro-form would be to reload the page with a var that you’d use to customize the pro-form’s shortcode as explained here: Knowledge Base » Using Variables In A Shortcode

I hope that helps.

No, the billing modification would be for subscriptions, which is not what you’d sell with buy-now pro-forms. Just use the same pro-form the user purchased with originally, if you have the auto-extend setting enabled it’d work.

khoi nguyen said:
do i still need blog farming license to have my members area in a subdomain? I have set up multisite enabled. I guess you can say that member.mysite.com will be a child blog that i will maintain. The members that sign up on mysite.com will have access to the child blog.

Then yes, if the users will have a child blog, then the blog farming license would be needed.

http://www.s2member.com/prices/#s2-terms-blog-farming

If you operate a WordPress® Multisite Network, and your Network DOES make it possible for users/members to create child blogs or sub-sites (in any way), we consider your installation to be a Multisite Blog Farm. Please note, many site owners run a Multisite Network for the purpose of maintaining their OWN child blogs or sub-sites. The term Multisite Blog Farm does NOT apply to a Network that hosts multiple child blogs or sub-sites, all of which are operated by a single site owner. A Multisite Blog Farm (in the eyes of s2Member®), is a Network that makes it possible for its users/members to create child blogs or sub-sites; where one or more of these child blogs or sub-sites is administered by a user/member (e.g. if you offer blogs or sub-sites to your customers, for free or otherwise).

No, if they cancel their subscription, PayPal would notify s2Member about it and s2Member would set an EOT time for the user. This is independent of the user’s role. When the EOT time is up, the Auto EOT Behavior would happen, which by default is a demotion to Level 0. [hilite path]Dashboard -› s2Member® -› PayPal® Options -› Automatic EOT Behavior[/hilite]

Cool. :)

Hi Govo.

Yes, you can protect them with button encryption: [hilite path]Dashboard -› s2Member® -› PayPal® Options -› Account Details -› Encryption[/hilite]

Or generate a button over at PayPal (doesn’t work for upgrades, only new signups): Knowledge Base » Using Buttons Generated @ PayPal.com

I hope that helps. :)

For your 1st paypal payment subscription you use the s2member module a way it is using the ECRP API (ExpressCheckout RecurringPayment).

However, in order to upgrade your subscription previously created with the API, you are using a subscription button (cmd=_xclick-subscriptions) : That is not possible.

He’s saying there that you created a subscription with Express Checkout and then were trying to upgrade it using a PayPal Standard button.

– For the 1st signup and paypal subscription I’m using the S2MEMBER Paypal(c) ProForm engine (=>Pro Form Generator For Level #1 Access).
– After that, for the Upgrade, I’m using the Paypal(c) Buttons engine (=>Button Code Generator For Subscription Modifications)

What you are saying here is what the PayPal rep said too. Created the subscription with Express Checkout and then tried upgrading with PayPal Standard.

If you create a subscription with Express Checkout you have to modify it with Express Checkout. If you create one with PayPal Standard, you modify it with PayPal Standard.

Since you created the subscriptions with Express Checkout, please try a modification pro-form. [hilite path]Dashboard -› s2Member® -› PayPal® Pro Forms -› Billing Modification Forms[/hilite]

I hope that helps. :)

Thanks. Got the email.

I tested the registration with the pro-forms for levels 1, 9 and 13, and they all went without a problem. The new accounts are in the Users list, with first and last names, and with the correct s2Member level.

Are you still having this problem? Could you give me a step-by-step to reproduce the problem please? Thanks!

No problem. :)

Hi Michelle.

When you tested opening the post, did you first make sure you weren’t logged in to your account?

When you go to edit that post, in the s2Member metabox, does it say the post is restricted at a certain level or with a certain custom capability?

Could you submit your site’s info so I take a look? Please include the name of the page you’re having this problem with. s2Member® » Private Contact Form

Let me know when you did so I take a look. Thanks! :)

Custom is clearly there and correct.

Yes, that looks correct in the shortcode.

That’s odd about the duplicate IPN calls though… why would those be happening? And they contain different data too…

Yeah, I’m not sure either. I’ll ask Jason about it.

The API username I’m using is an API-only (API_FULL_TRANSACTIONS) user, so as not to expose the admin login credentials to our PayFlow account. This seems to be legit, and PayPal confirmed that it’s okay to do… If you think I should change it to the standard admin account, I can give that a shot and see what happens.

You can test it if you want, but I think it’s fine. I just wanted to make sure that the credential was actually valid and not just a mistake.

Also, why are you storing full CC account and user/pass info in plain text in the reg-handler.log?! That seems a bit shady, if you ask me.

I don’t know. I’ll ask Jason about this too.

I’ll let you know as soon as I hear back from him. Thanks for your patience. :)

I’ll set up a clean environment and test out the plugin shortly to see if we still have issues or not.

Did you get around to test this? Is this clean installation what you’ve been testing with?

Hi Benjamin.

s2Member serves those securely when you use force SSL with the post’s custom field. Pre Sale FAQs » Is WordPress® compatible with SSL enabled?

If you had trouble with it, I suspect a plugin/theme conflict. Make sure you don’t have other things trying to force the SSL too, since that usually causes trouble. You can also test for a plugin/theme conflict following the tips here: Knowledge Base » Common Troubleshooting Tips.

I hope that helps.

Hi Chase.

I’ll have to ask Jason about this one. I’m leaving him a message now and I’ll let you know as soon as I hear back from him. Thanks for your patience.

In the meantime, could you please post more info about what you tried? Could you explain where you used [hilite mono]attach_s2member_query_filters()[/hilite]? And could you submit your site’s info so Jason can take a look at your installation in case it’s needed? s2Member® » Private Contact Form

And just to rule out a theme/plugin conflict, could you test your theme and plugins to see if that’s not the source of the problem? See: Knowledge Base » Common Troubleshooting Tips.

Thanks!