Raam Dev

Hi Deyson,

Please check to make sure the emails are not going to spam. You might also want to try changing the email address to see if you start getting them.

I’m still receiving the notifications, so that would indicate there’s a problem with the email routing between s2Member.com and your email provider (or possibly that the emails are going to spam).

Hi Joanne,

That is correct, you can use WP Super Cache with s2Member.

Also, the Reset Roles/Capabilities does not change the status or role assigned to any users. It simply resets the default internal Role/Capability sets that come with s2Member.

If you’ve used a role editor to manually change the role/capabilities (e.g., what the s2member_level1 role is allowed to do within WordPress), or if another plugin corrupted those default roles/capabilities like Jason suggested may be the case, then you can reset those changes back to the way s2Member expects them to be using that button.

As long as you haven’t intentionally used something like a Role Editor plugin to make changes to those default s2Member roles/capabilities, using that button will be safe. But as with anything, it never hurts to do a database backup beforehand if you’re unsure. :)

Glad to hear it! :) Thank you for the update.

Hi David,

I heard back from the lead developer and here’s what he had to say:

Although not ideal, that’s a serialized array of details submitted during registration for that particular Custom Field. If a site owner configures a Custom Field that collects multiple option values submitted as an array, s2Member will serialize that array into a string before emailing administrative notifications. Its always been like that. Not a bug, just one of those weird behaviors in administrative notifications. I’ll have this resolved in the next major release of s2Member.

In the mean time, if a customer needs to receive a more customized email message, API Notifications connected to a custom script would accomplish this.

You can learn more about API notifications in Dashboard -› s2Member® -› API / Notifications.

Hi Nigel,

This is not a supported feature. s2Member is a WordPress plugin and it inherits the limitations imposed by WordPress, namely that user login sessions are not carried over from one domain to another. This is even true with the WordPress Multisite feature. Please see the following from WordPress.org:

The sites in a multisite network are separate, very like the separate blogs at WordPress.com. They are not interconnected like things in other kinds of networks (even though plugins can create various kinds of interconnections between the sites). If you plan on creating sites that are strongly interconnected, that share data, or share users, then a multisite network might not be the best solution.

There are of course ways around this problem, but they would not be supported by s2Member.

Thank you for the update, Will. Let us know if you experience this again. Any additional information you can provide will be helpful. :)

Hi Mike and Ryan,

s2Member integrates with ClickBank to support Buy Now & Recurring Products. However, s2Member does not support or integrate with Warrior Plus.

If you have any questions regarding ClickBank integration with s2Member, please post a support thread in our Customer Support Forum.

Hi David,

I just tested the same button generator and it works correctly for me.

Keep in mind if you’re using the HTML version of the button code, you’ll need to install and activate a plugin like Exec-PHP so that the PHP snippets in that code are run properly.

Hi Rich,

Yes, s2Member integrates with Aweber and we also support Content Dripping (I assume that’s what you mean by ‘sequential updating of content’).

Hi James,

If s2Member is not part of the purchasing process, s2Member won’t know who should be allowed to register and who shouldn’t. In other words, if you leave Open Registration enabled and simply point people to s2Member, anyone (even people who haven’t paid) will be able to register and gain access to the videos.

If you must have customers pay through another system, you’ll need to find a way to integrate that system with s2Member. Such a custom integration would be outside the scope of our support policy (please see s2Member® » Support Policy » Outside Scope).

The most simple workaround to this problem would be to allow anyone to register as a Free Subscriber and then manually “upgrade” the accounts of those who have made a purchase (you’d simply edit their profile and change their account role from Free Subscriber to Level 1).

Then, you can protect your videos page by requiring Level 1 access and only those people who’ve purchased access would be allowed to see the videos. This is of course a lot more time consuming on your end, but the other option requires a custom integration.

If you’re open to abandoning your current shopping cart system, then you could use s2Member for the entire process.

Hi Ryan,

s2Member sets a cookie in the user’s browser after they’ve successfully made a payment. If you have Open Registration disabled (Dashboard -› s2Member® -› General Options -› Open Registration), that cookie must be present to allow them access to the registration page. If Open Registration is enabled, anyone can visit the registration page.

With the regular s2Member payment buttons, s2Member generates an email after registration (Dashboard -› s2Member® -› PayPal® Options -› Signup Confirmation Email) that contains a special link to register. That link sets the cookie and then redirects them to the registration page.

If you want to manually generate those cookies, you’ll need to dig into the s2Member code and go from there (all of the source code is available for both the free and Pro version of s2Member). This is outside the scope of our support policy (please see s2Member® » Support Policy » Fine Lines), so you’d need to make that custom integration on your own.

You’re most welcome! Thank you for sharing your solution.

Hi Joanne,

Please provide any log entries related to the transaction in question (the transaction that should’ve gone to Level 1 but remained a Free Subscriber) from both authnet-api.log and authnet-ipn.log. The information in those logs will help us diagnose the problem.

To keep the formatting clean, you can wrap the log entires in code tags before posting them. Also, please x-out any private information (such as email addresses).