Jason (Lead Developer)

Thanks for your inquiry. ~ We appreciate your patience :-)

Please log into your account here at s2Member.com and go to “My Account”. There you will find our recommendation and links to the Quick Cache plugin. Quick Cache will work properly with a default installation, no additional configuration necessary. Quick Cache was developed by us :-)

See also: http://wordpress.org/extend/plugins/quick-cache/

Thanks for the follow-up :-)

When users sign up using this form, they are created as users in the wp-admin area but they never get any user information sent to them for to how to login. The payment does go through and I do receive it but I have to manually add the payment info to their user area in the wp-admin.

So checkout is not fully integrated yet, because paid registrations are not being entirely processed properly yet. It sounds to me like s2Member’s post-processing of the transaction is failing. To determine why, please review your PayPal configuration for s2Member, in this section of your Dashboard.

See: Dashboard -› s2Member® -› PayPal® Options

Also, please enable logging here, so we can help you determine what the underlying issue is.
Dashboard -› s2Member® -› PayPal® Options -› Account Details -› Logging

Once logging is enabled, please submit a Dashboard login for us, and we will run diagnostics for you. Please do that privately, using this form: s2Member® » Private Contact Form

Your Shortcode looks good. Thank you.

All I am looking for is the correct way to configure the s@Member settings to accomplish the goal of:
A completely free blog.
A free membership that accesses free pages that are not part of the blog (ie. basic Buddy Press access “inside” the site)
Paid membership levels designed to give members even more value within the site.

A completely free blog, is a blog that does not protect any of it’s content with s2Member. Or at least, very little. That is, most of your content would NOT be protected by s2Member, and thus, it would be available for public viewing, without any Membership Level Restrictions applied to this content at all.

If you have some content that requires registration (even though you’re not charging for it), if you just want to make sure a public visitor is registered before certain content can be viewed, you would protect that content at Membership Level #0, requiring Free Subscribers. Then you would allow Open Registration with s2Member, and make a Free Registration Form available on your site, so that public visitors can register and become Free Subscribers.

Here are the relevant sections in your Dashboard.
See: Dashboard -› s2Member® -› General Options -› Open Registration
See: Dashboard -› s2Member® -› Restriction Options
See: Dashboard -› s2Member® -› PayPal® Pro Forms -› Free Registration Forms

Additional content can be protected at higher Membership Levels, where you require payment to access specific content within the site. This is achieved by protecting some of your content at Membership Level #1 or higher, and then making a checkout form available on your site so that public visitors and/or Free Subscribers can purchase.

See: Dashboard -› s2Member® -› PayPal® Pro Forms -› Membership Level # Forms

Thanks for reporting this important issue.

When I paste the code onto a page it just displays the code on my site.

Do you mean it displays the Shortcode itself? Or some other code?

If it’s displaying the Shortcode itself, that would indicate to me that one of the following is occurring.

• The ccBill payment gateway is no longer active in your installation of s2Member Pro?
  Please check that here: Dashboard -› s2Member® -› Other Gateways
• The Shortcode is invalid. Please paste a copy of the Shortcode that you’re using, for us to review with you.
• You have a theme/plugin that is preventing WordPress from parsing Shortcodes. That is, the do_shortcode() filter is not being applied by WordPress. Please try to reproduce this on a clean installation of WordPress, running no other plugins, and using the default theme. Is it still a problem?

Please let us know if problems persist :-)

Thanks for the follow-up :-)

I’m sorry. I’m out of ideas on this. I’ve been unable to reproduce this in our lab. If problems persist, please send me a Dashboard login, with a new test installation. An installation that has NO Amazon integration yet. This could be related to a server incompatibility, so if I investigate it this on your server, it might shed light on the issue here. Please send that privately. See: s2Member® » Private Contact Form

Something you can do as well. Please unzip and upload this file to your server and open it in a browser. This is a server scanning tool that we use here at s2Member, that will help detect any issues that s2Member might be having in your environment. Download: http://www.s2member.com/r/server-check-tool/

Thanks for your inquiry. ~ We appreciate your patience :-)

i understand the use of “-all” but does “all” have the opposite effect?

No it does not. I’m sorry. If you want to give all Custom Capabilities, you will need to list those out in comma-delimited format please.

Thanks for the follow-up :-)

I logged out and then back in a the test acct. The system didn’t demote to Level 0. Is there a certain time of the day that happens or am I missing something?

Once the EOT Time has been set, give it 30 minutes or so please. s2Member’s Auto EOT System needs to be enabled for this to work, and it will process any EOTs that exist, based on these EOT Times, every 15 minutes. This is powered by WP Cron, by default.

Please see: Dashboard -› s2Member® -› PayPal® Options -› Automatic EOT Behavior

Please let us know if problems persist :-)

Thanks for your inquiry. ~ We appreciate your patience :-)

1. Let say I use the following code to restrict the premium content in a post. I create 3 posts by using the code below: test1, test2, test3

[s2If current_user_can(access_s2member_level0)]
Some content for Members who are logged in with an s2Member Level >= 0.
[/s2If]
Is it possible to limit how many premium content show to the member? e.g. If a user view test1, then he can’t view the premium conten in test2 and test3.

Your use of s2Member Conditionals here is correct. No problem there. However, s2Member does not provide any functionality that would make it possible for you to disallow access to one page, because a Member has visited another already. That’s something you would need to custom code unfortunately.

2. I will buy the pro version since I want to use the ccbill addon. If a user join my site as a free user first, can he use ccbill addon to upgrade later? Does he require to choose another username after the upgrade?

Yes, this will work just fine. With s2Member Pro installed, please generate a ccBill Payment Button with s2Member, and introduce this to your Users/Members, or to new customers. If the customer is already logged-in when they click the payment button, s2Member will automatically detect they are an existing user, and their existing account will be updated to a paid status, instead of asking the user to re-register. This is something that occurs automatically, as long as the customer is logged-in when they proceed to checkout.

Details received. Thank you!

It appears from your log files that you are running test transactions against a live account that has been placed into TEST mode? Unfortunately, Authorize.Net returns transaction IDs in this mode, always equal to a value of 0, and s2Member will choke on this, which is why you’re experiencing the issues that you’ve reported here.

I’m very sorry about this. I’m going to report this to Authorize.Net again. This has come up in the past, which is why we suggest in your Dashboard, to setup a developer test account instead. Running test transactions against a live account is really a problem for s2Member, because even in TEST mode, s2Member needs to see, at the very least, a fake transaction ID.

Solutions for you…

1. If you’d like to run test transactions, I recommend that you setup a developer test account with Authorize.Net (free), instead of running test transactions against your live account in TEST mode. This problem does not occur when testing against a developer test account.

Setup developer test account here: https://developer.authorize.net/testaccount/
Log into your developer test account here: https://test.authorize.net/

2. Or, you can simply run your test transactions against your live account, but without s2Member being in Sandbox mode. The problems you’re experiencing are occurring only because you’re in TEST mode.

Please let us know if problems persist :-)

Thank you. Details received.

Can you please paste your s2Member Shortcode here for review as well? Or just double-check it please. It appears from your log files that your Shortcode does NOT contain a custom="" attribute, because the IPN log indicates it is missing during post-processing of a transaction, which would explain why emails are not being received either. You should have custom="www.yourdomain.com" in every s2Member Shortcode please.

Thanks for reporting this important issue.

The problem is that even though the user is created, the user is not sent any login information and therefore cannot access the site.

I’m sorry, can you please clarify. The login information is not being sent during Free Registration, or during paid registration? In either case, can you please paste the Shortcode that you’ve used to integrate this registration form that’s not working properly? I’d like to see the underlying Shortcode and we can work from there to help you determine the cause of this on your installation.

How do I configure this to have a page that offers all of the membership options, registers all users (free and paid), creates new users, accepts the paypal payments for paid memberships and still sends the login information to the new member?

NOTE: I just had a thought… Should I be saying no free registrations option and then charge nothing for the first level? (Meaning that the level-0 would then be the read only visitors to the blog, level-1 would be free membership, level-2 would start the paid membership options?)

• No Level at all (i.e. public visitors) can see anything that’s not protected by s2Member.
• Level #0 is generally associated with Free Subscribers (i.e. you’ve allowed them to register, so they have an account), but they did NOT pay you, because they registered for free. These folks generally have access to your Login Welcome Page, but not to any paid content on the site.
• Anything higher than Level #0 generally requires payment, and it will grant access to any content you’ve protected at Level #1 or higher. Just depends on how you’ve protected your content.

With s2Member Pro, I recommend this Pro Form to help you with Free Registration.
Dashboard -› s2Member® -› PayPal® Pro Forms -› Free Registration Forms

Thanks for your patience.

Here is the JavaScript solution I mentioned, which will actually serve you better, since it won’t get wiped out during future updates to s2Member. Please follow the instructions below, and let me know if you have any trouble. This was tested against WordPress v3.5, but should work on any version of WordPress, at least back to v3.2.

Please create this directory and file:
/wp-content/mu-plugins/s2-hacks.php
(NOTE: these are MUST USE plugins, see: http://codex.wordpress.org/Must_Use_Plugins)
(See also: http://www.s2member.com/kb/hacking-s2member/)

Thanks for your inquiry. ~ We appreciate your patience :-)

So if I understand correctly (please correct me if I’m wrong), you want to bypass the Username all together, and use ONLY the email address of the customer as the Username. Is that right?

If so, this is not a feature provided by s2Member. You can search the forums here for some others who have tried this, but it’s not something that we provide support for. Each customer MUST be associated with an Email Address and a Username; because this is an assumption throughout all of s2Member’s source code. s2Member expects that each customer will have both of these values.

Thanks for the follow-up :-)

Gotchya. Well unfortunately, this is not possible with a hook/filter, so it will require some changes to the code directly, which might get wiped out during a future upgrade of s2Member. If you can deal with this, no biggy. I’ll outline it below. If you don’t like this solution, you might consider adding a jQuery-driven script to the Post/Page editing station in the Dashboard, that would set that meta-box drop-down value to a default selection. That way you’re not making changes to the s2Member source code directly, but handling this with JavaScript in the Dashboard instead.

If you’d like to make the changes to the source code, here is what you’ll need to do.

Open this source file please:
/s2member/includes/classes/meta-box-security.inc.php

Find these two snippets of code. One for Pages, another for Posts.

<option value="'.$n.'"'.((in_array($page_id, $pages&#91;$n&#93;)) ? ' selected="selected"' : '').'>
<option value="'.$n.'"'.((in_array($post_id, $posts&#91;$n&#93;)) ? ' selected="selected"' : '').'>

Change these to the following:

<option value="'.$n.'"'.((in_array($page_id, $pages&#91;$n&#93;) || (empty($pages&#91;$n&#93;) && $n === 0)) ? ' selected="selected"' : '').'>
<option value="'.$n.'"'.((in_array($post_id, $posts&#91;$n&#93;) || (empty($posts&#91;$n&#93;) && $n === 0)) ? ' selected="selected"' : '').'>

Please let us know if problems persist :-)