Cristián Lávaque

Hi Lovell.

s2Member can control the initial/trial term for this, but if you want to modify a subscription that’s already going, you’ll need to see if PayPal lets you. I’m not sure how it’s done, you’ll need to ask them. :/

Hi Justus.

Yeah, that’s odd. What’s that Hostme entry at the bottom? I don’t see it in the plugins list.

Did you try changing the theme to the default one as a test? Sometimes the theme, although for the front, does affect the admin side.

Hi James.

Yeah, it’s definitely a nicer option to use. We’ll let you know when this is ready. :)

Hi Ed.

The confirmation email is always sent, even if everything goes fine, but it is a safe net in case s2Member doesn’t hear back from PayPal immediately and so that message is given, asking the person to check for the email later, after s2Member does hear from PayPal and can proceed.

Did you double check your PayPal integration? [hilite path]Dashboard -› s2Member® -› PayPal® Options[/hilite]

Could you post the log entries related to this transaction, x’ing out any private info, please? [hilite path]Dashboard -› s2Member® -› PayPal® Options -› Account Details -› Logging[/hilite]

Thanks!

In the page with the problem, if you go to the HTML and find the URL to s2Member’s JavaScript, copy it and try opening it in your browser. Do you get the JS or an error?

Did you enter the IDs to protect those pages with the Specific restriction? If you didn’t, then the PayPal button generator won’t list them. [hilite path]Dashboard -› s2Member® -› Restriction Options -› Specific Post/Page Access Restrictions[/hilite]

Also:

please be careful not to create a conflict with other Access Restrictions. If you are going to sell Specific Post/Page Access, you should enter specific Post/Page IDs here; and make SURE that you’ve NOT already protected any of these Posts/Pages with Member Level Access Restrictions. In other words, if you configure s2Member, in such as a way, that a Post/Page requires Membership Level Access, you cannot sell that same Post/Page through Specific Post/Page Access. Doing so, would create a conflict. Customers that purchased Specific Post/Page Access, would be unable to access the Post/Page – without also having a Membership. Not good. So please be careful.

If you log out of your account and try loading the page, do you get taken to the Membership Options Page? If so, the URL will include variables that you can read to find what restriction is being applied. [hilite path]Dashboard -› s2Member® -› API / Scripting -› Membership Options Page Variables (MOP Vars)[/hilite]

Sorry, I didn’t know you had many options.

Hmm… You could have the options in a step before the registration, and then customize the pro-form dynamically. http://www.primothemes.com/forums/viewtopic.php?f=36&t=1604

I haven’t tried this, but you could test it, is generate a pro-form for each option, changing only the success attribute, and copy the HTML each outputs in the page where it is. All would be the same except for the [hilite mono]s2member_pro_paypal_registration[attr][/hilite] field. Change its type from hidden to a dropdown and for each option use the field values you got from their respective forms. paste the form in the HTML editor and try it.

Hope that helps.

• This reply was modified 4 years, 8 months ago by  Cristián Lávaque.

Hi Miike.

You can hide them with CSS. Use Firebug to help you see their exact ID (e.g. label.s2member-pro-paypal-form-card-type-maestro-label) and style them it with [hilite code]display: none;[/hilite].

I hope that helps. :)

With a MySQL query. I’m not very familiar with multisite. As far as I know, all the network users are in the same table, and they have a blog ID to know to which one they belong. If that’s correct, then do a query in phpMyAdmin to udpate those with blog ID __ to blog ID __.

You’re welcome. I’m glad you found the problem.

For the PayPal tests I suggest that you enable logging. [hilite path]Dashboard -› s2Member® -› PayPal® Options -› Account Details -› Logging[/hilite] ;)

Hi Buck.

Since your URI restriction has a trailing slash, the URL without it won’t have a match. Try removing all the trailing slashes and see if that solves your problems:

URIs That Require Level #0 Or Higher:
/groups
/group-forums
/activity
/profile
/settings

URIs That Require Level #1 Or Higher:
/members
/blogs
/messages
/friends
/forums
/forum

Actually, /forum will take care of /forums too. And /group would take care of /groups and /group-forums.

I hope that helps. :)

Cool.