Raam Dev

Hi Ross,

Yes, the message “s2Member Level/Capabilities updated w/ advanced update routines” would indicate that an upgrade was successfully processed.

This should work:

<?php 
$s2member_last_payment_time = get_user_field('s2member_last_payment_time');
if (!empty($s2member_last_payment_time)) 
	echo 'Last Payment: ' . date('M-d-Y', $s2member_last_payment_time);
	echo 'LEVEL2 1 Month Membership: ' . strtotime(date("M-d-Y", $s2member_last_payment_time) . " +1 month"); 
?>

Hi Mark,

Please read over Dashboard -› s2Member® -› Pro Coupon Codes -› Affiliate Coupon Codes; I believe that will answer most of your questions. (If you have further questions, please let us know.) There is no automatic generation of coupon codes in s2Member; coupon codes must be manually entered by an administrator.

Regarding EOT notifications: We’re working on incorporating that into the next major release of s2Member. We don’t have a release date set, but we’ll make an announcement as soon as we’re ready.

Hi Nathan,

No, not at this time. For a list of supported payment gateways, please see Pre Sale FAQs » What payment gateways does s2Member® support?

Adding this to the top of your theme’s index.php file should do it:

<?php if(is_home()) { define(“QUICK_CACHE_ALLOWED”, false); } ?>

Hi Oriol,

While s2Member is compatible with WordPress Multisite Networking, the sites within a WordPress network are separate and not interconnected. That means you cannot share users, logins, or other data across the sites (including access control).

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.

The s2Member Multisite feature allows you to offer the s2Member plugin to sub-sites, giving your sub-sites the ability to setup and use s2Member on their own. When you upgrade s2Member on the primary site, the s2Member plugin is automatically updated for all your sub-sites. However, things like access restrictions on one WP installation are not shared across WP installations (again, the WordPress Multisite feature itself isn’t designed to work like that).

There are plugins that allow you to get around these WordPress Multisite limitations, however they may or may not work with s2Member.

Also, all of the s2Member Levels are based on the WordPress Subscriber role capabilities, which does not offer any permission to access the WordPress Dashboard or publish/edit content. In other words, s2Member is only designed to restrict access to viewing content, not for controlling access to WordPress back-end features like publishing and editing posts.

Hi Genie,

What’s not working? Which previous instructions are you referring to? Do you have any caching plugins installed (e.g., WP Super Cache, or QuickCache, or W3 Total Cache)?

Also please download this Server Check Tool, upload the PHP file to your WordPress directory, and then load the URL to the file in your browser. It will run a bunch of tests to determine if there’s anything amiss on the server-side.

Hi Scott,

Please see the following from Dashboard -> QuickCache -> MD5 Version Salt:

Quick Cache can also be disabled temporarily. If you’re a plugin developer, you can define a special constant within your plugin to disable the cache engine at runtime, on a specific page, or in a specific scenario. In your PHP script, do this: define(“QUICK_CACHE_ALLOWED”, false). Quick Cache is also compatible with: $_SERVER[“QUICK_CACHE_ALLOWED”] = false, as well as define(“DONOTCACHEPAGE”, true), which is backward compatible with the WP Super Cache plugin.

Please see this thread.

Hi David,

All of that can be done with CSS. You can write CSS styles that set various elements to display:none; to hide them.