Raam Dev

If you want to change the color of the username that shows up after they’ve logged in, you’ll need to do something like this:

.ws-plugin--s2member-pro-login-widget-profile-summary-name { color: red; }

That should go at the bottom of your theme’s style.css file, probably found in wp-content/themes/your-theme-name/. You should also be able to access that file by simply going to Dashboard -> Appearance -> Editor in WordPress and then selecting the style.css file on the right column.

Simeon,

If you need to use multiple membership levels but you don’t want higher levels to have access to lower level content, then you need to use Custom Capabilities in addition to the levels.

For example, you would restrict all Level 1 content to both Level 1 membership and a Custom Capability called level1. Then you would configure your Level 1 signup form or button to automatically assign the level1 Custom Capability to anyone who signs up for Level 1.

You would repeat that process for each of the levels, restricting content to both a membership level and a Custom Capability and configure your signup forms to also assign a Custom Capability specifically for that level.

Then, when a Level 2 member logs in, for example, he won’t have the level1 Custom Capability, so he won’t have access to the Level 1 content.

Hi Simeon,

Unfortunately the downloads feature relies on the Membership Level to set different download limits. There is not currently any way to configure a Custom Capability that gives specific restrictions on downloads. (See Dashboard -› s2Member® -› Download Options -› Basic Download Restrictions; only Membership Levels can be used there.)

The scenario you’re describing would rely heavily on Custom Capabilities to separate out different users within the same level (e.g., Level 1 user with ccap1, Level 1 user with ccap2, etc.). However, since your ‘groups’ are offering different types of download access, you cannot use Custom Capabilities without adding custom code that adds such a restriction feature to Custom Capabilities.

If you’re referring to the label “Username”, then you’d add something like this:

.ws-plugin--s2member-pro-login-widget-username { color: red; }

If you’re referring to the username input box itself, you’d add something like this:

#ws-plugin--s2member-pro-login-widget-username { color: red; }

Could you copy/paste the full URL they are incorrectly redirected to on the Membership Options Page? That URL will contain details about why they were redirected and if you share that here we can explain where the problem lies.

It looks like maybe your WordPress install is having trouble using the s2Member constants (i.e., S2MEMBER_CURRENT_USER_PAID_REGISTRATION_DAYS). The next step is to disable all other plugins except s2Member and see if it works then. If that doesn’t fix it, I suggest also trying to switch to the default WordPress theme (e.g., TwentyEleven).

These code samples work (I’m personally using them on my own site), so the problem is somewhere with your site or server configuration. We just need to keep narrowing it down until we figure out where the problem is.

When I tested the checkout and I was redirected to PayPal, selected my funding source and I was successfully redirected back to your site. At this point your website should have an option to submit the payment. It look like this is what is missing.

That actually doesn’t make sense. Once you’re sent to PayPal, you do not get returned to your site until the payment has been completed on PayPal’s side. It wouldn’t make sense to go to PayPal, then back to your site, then back to PayPal again.

I just tested your signup using PayPal. I filled out the registration form on your site, selected PayPal, clicked “Checkout with PayPal”, was redirected to PayPal’s website, logged into my PayPal account, and got to the point where I could click “Pay Now”. (I didn’t click “Pay Now”, but I would’ve expected that once payment was made, I’d get transferred back to your site. To get transferred back to your site after payment is made is normal behavior.)

Are you seeing something different?

Tracy,

The problem is still that your page is not “processing” the PHP code. Installing and activating the PHP Execution plugin should’ve been enough to tell WordPress to process the PHP code on that page, but apparently something else is going on. I believe the plugin has settings that allow you to define who is allowed to run PHP code. Have you checked those settings? If the “Collectable Membership Subscriptions” page was created by someone who doesn’t have permission to run PHP code, the PHP code on that page won’t get processed.

Another thing I recommend trying is using the s2Member PayPal Button Shortcode instead of copy/pasting the HTML Form code (which is what it looks like you’ve done… however I could be mistaken). If you’re using the HTML Code version, I recommend trying to the Shortcode version (simply regenerate the button in Dashboard -› s2Member® -› PayPal® Buttons and copy/paste the resulting shortcode).

If you do “View Source” when viewing your “Collectable Membership Subscriptions” page, you should not see any PHP code in there. PHP code is supposed to be processed on the server and turned into regular HTML and text before it ever gets to your browser, so if you’re seeing PHP code anywhere except in your WordPress editor, then the problem is that your server is not processing the PHP.

Kerry,

The next step is to check your logs for any hints as to what else might be causing the problem. Have you enabled logging in Dashboard -› s2Member® -› PayPal® Options -› Account Details -› Logging? Please run another test and then copy/paste the relevant logs for that specific transaction from the log files in wp-content/plugins/s2member-logs/ here for us to check. (Be sure to X-out any private information, such as email addresses.)

As Jason mentioned in the other post, what’s most likely happening is that you’re setting the EOT and then as part of the upgrade process s2Member is deleting the EOT. So, you need to make sure you’re updating it after that point.

Perhaps try ws_plugin__s2member_during_paypal_return_after_subscr_signup_w_update_vars. You can also look through the code to see what makes the most sense.

Hi Genie,

Please see Dashboard -› s2Member® -› ClickBank® Options -› Signup Confirmation Email. The user will receive that email after signing up and that email includes a registration link where they will be able to create their account.

John,

It sounds like there might be a problem with your server sending emails to GMail addresses. You’d need to contact your web host to have them check on that for you.

Another helpful thing you can do is install the Email Log plugin. That plugin keeps a record of all the emails sent through WordPress so you can see exactly what got sent.

Another very useful thing is to configure an SMTP server for WordPress so that all emails are sent through another server instead of the one your site is on. I personally have a GMail account that I use as my primary WordPress address and I installed the WP SMTP plugin and configured it to use the GMail SMTP server to send all my emails. It works great.

You can learn more about both of these things here: Knowledge Base » Troubleshooting Email Delivery Problems