Philly

Hi Eva,

Notice

‘Unable to verify POST vars. This is most likely related to an invalid ClickBank® configuration. Please check: s2Member -> ClickBank® Options.

I would double check your ClickBank® Account Details in s2member and in your ClickBank® account and the same for ClickBank® IPN v2.1 Integration

Did you also remember to input your ClickBank® IPN/Secret Key you didn’t mention that in your first post.

Hope that helps

Hello Andrea,

In a text widget in the sidebar, or in your s2member pro login widget in the Additional XHTML/PHP Code? section ( when logged-in ) you could use:

[s2If current_user_can(access_s2member_ccap_clientA)]
        Display links for Client A
[/s2If]
[s2If current_user_can(access_s2member_ccap_clientB)]
        Display links for Client B
[/s2If]
[s2If current_user_can(access_s2member_ccap_clientC)]
        Display links for Client C
[/s2If]

You can find out more under s2Member® API / Scripting > Advanced/PHP Query Conditionals or Custom Capabilities

Hope that helps

My advice would be to do as follows

The Subscription Signup/Registration Process

1. Internet Users will go to your Membership Options Page ( which you’ll need to configure on the s2Member General Options panel ). On this Membership Options Page, that YOU will create in WordPress®, you’ll insert the PayPal® Subscription Buttons that were generated for you by s2Member.

2. An Internet User will click on a PayPal® Subscription Button from your Membership Options Page. They will be transferred over to PayPal® in order to agree to your Membership terms and pricing. You can customize the Checkout Page Style, Pricing, Payment Periods, and more – whenever you generate your PayPal® Buttons through s2Member.

3. Once a User has completed the Subscription Signup Process at PayPal®, they’ll be returned to your site, where they’ll be activated by s2Member instantly, and given the opportunity to register a Username & Password for their Membership. ( Note: they’ll be allowed to register a Username & Password, even if you’ve set ‘Anyone Can Register’ to `Off` in your General WordPress® options; because s2Member identifies the User as having paid for Membership access through PayPal® ).

s2Member will also send the User an email with instructions on how to register their Username & Password, just in case they missed the instructions after checkout. That email will be sent to their PayPal® email address. Much of this is handled through the PayPal® IPN service behind-the-scene, where PayPal® and s2Member communicate with each other.

4. Once a User has completed checkout and registered a Username & Password, they’ll be able to log in. The first page they’ll see after logging in, will be your Login Welcome Page ( which you’ll need to configure on the s2Member General Options panel ). Your Login Welcome Page can contain whatever you like. You’ll need to design this Page in WordPress®, and be creative!

It looks like you already have everything setup so all you need to do is put the paypal buttons on your membership page instead of directing users to the pro form on your monthly-payment.

I know its not the solution you want but without the ssl certificate you either have to get customers to register before or after payment and I guess in your case its better afterwards. When you have some money coming in you can always purchase a certificate and go down the pro forms route.

I’m not sure what they use perhaps its

<?php wp_logout(); ?> 

or Logout and Redirect to Current Page

<a href="<?php echo wp_logout_url( get_permalink() ); ?>" title="Logout">Logout</a>

Can you please also post the contents of your

header.php

Firstly though I can see in your other post your having trouble logging out, you may want to find out if the theme your using is compatible with s2member? Can you disable your plugins, clear the browser cache then try logging out, if that fails to work can you switch to the default wordpress theme and see if your able to log out

Richard,

This is your javascript file created by s2member, Notice that your login welcome page is set to

'http://ringertown.com/login'

which does not exist

S2MEMBER_LOGIN_WELCOME_PAGE_ID = 28,
S2MEMBER_CURRENT_USER_PROFILE_MODIFICATION_PAGE_URL = 'http://ringertown.com/?s2member_profile=1'
,S2MEMBER_MEMBERSHIP_OPTIONS_PAGE_URL = 'http://ringertown.com/tournaments-list-all',
S2MEMBER_LOGIN_WELCOME_PAGE_URL = 'http://ringertown.com/login',
S2MEMBER_LOGOUT_PAGE_URL = 'http://ringertown.com/wp-login.php?action=logout&_wpnonce=cd81a49109',
S2MEMBER_LOGIN_PAGE_URL = 'http://ringertown.com/wp-login.php',

If your settings under s2Member® General Options > Login Welcome Page do not match those above then you have a javascript conflict. As Cristián said if you deactivate other plugins one by one and try to find which one is causing the problem, it may well be your theme that is conflicting so try using the default theme too.

[s2If is_user_logged_in()]
    Content for anyone that is logged in, regardless of their Membership Level.
[/s2If]

[s2If !is_user_logged_in()]
    Some public content. They're NOT logged in.
        A leading !exclamation means false.
[/s2If]

What happens when you connect s2member to S3 without using cloudfront? Is that working or are you also getting an error message

• This reply was modified 4 years, 8 months ago by  Philly.

I think its something like this

1:1:http://mysite.com/members/%%current_user_login%%/profile/edit/group/1

Yes

In wordpress > users > all users

tick the checkbox next to username, that will checkbox all users on the current page, then the drop down box that says ‘change role too…..’ select ‘s2member level 1’ and click change.

Also if you have many pages of users there is a setting under screen options to display more on one page

Have you tried using a different bucket also don’t forgot to press the refresh button within cloudfront

Hi Tuhin,

Are you trying to re-configure?

I find it quicker and easier to first go into cloudfront via AWS console then disable and delete the distributions s2member set manually. Then when thats done 15mins approx, go back to your site and try and run auto-configure again, it sometimes take more than one attempt.