By default, s2Member will retain all of it\'s Roles, Capabilities, and your Configuration Options when/if you delete s2Member from the Plugins Menu in WordPress. However, if you would like for s2Member to erase itself completely, please choose: No (upon deletion, erase all data/options). See also: s2Member Uninstall Instructions
No (upon deletion, erase all data/options)
Yes, safeguard all data/options
s2Member uses an encryption secret to encrypt and validate certain sensitive values. If you leave this setting blank, s2Member automatically uses the WordPress salts via wp_salt(). You can instead configure a separate Security Encryption Key for s2Member, giving you independent control over this secret and making it easier to preserve across site moves or restores when you keep the same key.
wp_salt()
Once a site is in use, avoid changing its effective encryption key unless you intend to invalidate or recover data encrypted with a previous key. Existing Specific Post/Page Access Links, Registration Access Links, registration/tracking cookies, pending transaction-return data, and values encrypted through s2Member\'s encryption API may depend on it. If you configure a key here, keep a secure backup of it.
'.esc_html(strtoupper(c_ws_plugin__s2member_utils_strings::random_str_gen(64))).'
'.implode('
', $GLOBALS["WS_PLUGIN__"]["s2member"]["o"]["sec_encryption_key_history"]).'
For normal encryption/decryption, a custom key supplied by code takes precedence. Otherwise s2Member uses the Security Encryption Key configured above; if this setting is blank, it falls back to the WordPress salts via wp_salt().
Many encrypted values are short-lived, but some can remain valid much longer. Changing the effective key will invalidate existing data that was encrypted with the previous key, which can include Specific Post/Page Access Links, Registration Access Links, registration and tracking cookies, pending transaction-return data, and values created through s2Member\'s encryption API. If this setting is blank, changing the WordPress salts will likewise invalidate data encrypted with the previous salts.
If you\'re developing your site in a localhost environment, running something like WAMP/MAMP, or EasyPHP, please add this line to your /wp-config.php file: define("LOCALHOST", true);.
localhost
/wp-config.php
define("LOCALHOST", true);
This lets s2Member know definitively that your site is in a localhost environment. s2Member will adjust itself accordingly, maximizing functionality during your developement. s2Member can usually auto-detect this, but in cases where your localhost installation runs on something other than 127.0.0.1/localhost, you need to tell s2Member definitively, by adding that line to your /wp-config.php file. For instance, s2Member needs to know when your server IP is the same as all User IPs.
127.0.0.1/localhost
Once your site goes live, please remove the line. If you\'re already on a live server connected to the web, please ignore this section.
By default, s2Member will load it\'s CSS/JS libraries on every page of your site. However, you may wish to enable lazy-loading here (i.e., only load when absolutely necessary).
Tip: Do you need s2Member\'s CSS/JS on every page? If not, you can turn lazy-loading on. If you need s2Member\'s CSS/JS on a given Post/Page, you can insert an HTML comment into the Post/Page content like this: <!--s2member-->. If a Post/Page contains the word s2member or an [s2* Shortcode, this will automatically trigger s2Member\'s lazy-load routine (no matter what you configure here). Thus, it\'s an easy way to force s2Member to load it\'s CSS/JS on specific Posts/Pages where you deem this necessary. There is also a WordPress filter available: add_filter("ws_plugin__s2member_lazy_load_css_js", "__return_true"); for developers. This could be incorporated into more dynamic scenarios.
<!--s2member-->
s2member
[s2*
add_filter("ws_plugin__s2member_lazy_load_css_js", "__return_true");
When s2Member needs to generate CSS or JavaScript dynamically, this controls the preferred dynamic route. If Static CSS/JS Delivery is enabled but current hooks or configuration specifically require the normal WordPress environment, s2Member uses the Full WordPress Dynamic Loader for compatibility instead.
s2member-o.php
These beta options build CSS and JavaScript files ahead of time under the WordPress uploads directory, so the web server can serve them directly without starting PHP and WordPress for each request. Framework and Pro files remain separate by default, with optional combining and minification for further optimization.
After enabling these options, test your membership, registration, profile, and payment pages. If static delivery cannot be used, s2Member switches to dynamic delivery automatically. Compatibility requirements that need normal WordPress hooks use the Full WordPress Dynamic Loader; Asset Health explains the active route and reason.
Some s2Member messages and labels are shown or updated by JavaScript—for example, form validation and password feedback—so JavaScript needs access to that text too.
Load with each WordPress page is unavailable: update s2Member Pro to a version that supports page-loaded JavaScript text. If your site needs different JavaScript text between languages before updating Pro, set Static JS Delivery to No so WordPress generates the JavaScript dynamically.
When s2Member logging is enabled, important static and dynamic CSS/JS events such as generation, refreshes, delivery problems, fallbacks, and recovery are recorded in css-js.log. Routine page loads are not logged.
css-js.log
* Static assets marked Not generated yet or Pending rebuild will be created or rebuilt automatically on a later admin or frontend page-load, or immediately with Refresh Static Assets.
Recheck Asset Health
s2Member keeps the latest 10 distinct Asset Health issues here until cleared. Repeated occurrences of the same issue on the same page are grouped together and keep up to 10 recent occurrence times. Clearing Last issue or Latest Issues does not change Current Health or its recent scoring history. Recheck Asset Health safely resets recent scoring history after current delivery and its fallback verify healthy. Enable s2Member logging for more detailed CSS/JavaScript troubleshooting history.
Page-load results: Each relevant frontend page-load gets one result with a score from 1 to 4. If a page uses several s2Member CSS or JavaScript assets, the least healthy result is used for that page.
Not generated yet / Pending rebuild: These are not delivery failures. The static asset either has not been created yet or needs to be rebuilt after a configuration, plugin, upgrade, or other change. s2Member normally handles this automatically on an admin or frontend page-load. You can also rebuild them immediately with the Refresh Static Assets button in this section.
Current Health: s2Member combines recent results from the last 10 page-loads with requests from the last 10 minutes. Newer activity carries more weight, so Health can improve again as successful requests replace older problems.
Fallback health: When preferred delivery is working but its Full WordPress fallback is unavailable, that failed fallback check is averaged into Current Health because the safety net would not be available if needed.
Health status: The combined result is shown as one of these health levels:
Examples: One Late result followed by normal page-loads may briefly show Recent issue and then return to Healthy. Repeated Fallback results can move Health to Working, review suggested. Repeated Failed results can move it to Needs attention.
Longer-term review: A Late result is only a diagnostic signal; it does not make s2Member load another copy of the CSS or JavaScript. A current Needs attention status can trigger an immediate admin notice. If Health does not return to Healthy within six hours, s2Member also reviews activity across that period and may suggest a review when the longer-term result remains substantially degraded.
s2Member can render different output depending on logged-in state, access level, conditionals (e.g., [s2If]), and nonce-based forms. If a cache stores a page generated under one context and serves it to another, visitors may see incorrect content or stale nonces. These options control when s2Member sends HTTP no-cache headers (Cache-Control: no-cache) to reduce that risk while allowing caching where appropriate.
[s2If]
Cache-Control: no-cache
ws_plugin__s2member_no_cache_headers_selective
Enable no-cache debug header?
'."\n"; echo ' No '."\n"; echo ' Yes, add a debug header.'."\n"; echo 'This adds a Server-Timing header to help troubleshoot why no-cache headers are being applied or not. This header includes the following variables:'."\n"; echo '
Server-Timing
mode
always
selective
evaluative
no_cache
1
0
headers
This is the name/address that will appear in outgoing email notifications sent by the s2Member plugin.
mailto:support@your-domain.com
'.esc_html(home_url("/contact-us/")).'
Conflict warning: You have another theme or plugin installed that is preventing s2Member from controlling this aspect of your installation. When the pluggable function wp_new_user_notification() is handled by another plugin, it\'s not possible for s2Member to allow customization of New User Emails. This is NOT a major issue. In fact, in some cases, it might be desirable. That being said, if you DO want to use s2Member\'s customization of New User Emails, you will need to deactivate one plugin at a time until this conflict warning goes away.
wp_new_user_notification()
This email is sent to new Users/Members who did not set a Custom Password during registration.
↑ NOTE: You currently have Custom Passwords enabled in your s2Member Registration/Profile Field options. Therefore, this email is not going to be sent; i.e., it is only sent to users who need it for the purpose of obtaining their password.
BuddyPress: please note that BuddyPress does NOT send this email to Users that register through the BuddyPress registration system. This is because BuddyPress sends each User an activation link; eliminating the need for this email altogether. However, you CAN still customize s2Member\'s separate email to paying Members. See: s2Member → PayPal Options → Signup Confirmation Email.
(The purpose of this email is to send the user a password-setup link; i.e., %%wp_set_pass_url%%)
%%wp_set_pass_url%%
'."\n"; //250615 Visual editor for HTML emails. if (empty($GLOBALS['WS_PLUGIN__']['s2member']['o']['html_emails_enabled'])) { echo ''.format_to_edit($GLOBALS["WS_PLUGIN__"]["s2member"]["o"]["new_user_email_message"]).''."\n"; } else { c_ws_plugin__s2member_utilities::editor('new_user_email_message'); } echo 'Message Body used in the email sent to new Users/Members.'."\n"; echo 'You can also use these special Replacement Codes if you need them:'."\n"; echo '
%%user_pass%%
%%role%%
(subscriber, s2member_level[0-9]+, administrator, editor, author, contributor)
%%label%%
(Subscriber, s2Member Level 1, s2Member Level 2; or your own custom Labels—if configured)
%%level%%
(0, 1, 2, 3, 4)
%%ccaps%%
music,videos,free_gift
%%user_first_name%%
%%user_last_name%%
%%user_full_name%%
%%user_email%%
%%user_login%%
%%user_ip%%
$_SERVER["REMOTE_ADDR"]
%%user_id%%
%%wp_login_url%%
%%date_of_birth%%
date_of_birth
%%street_address%%
street_address
%%country%%
country
%%etc, etc...%%
%%cv0%%
%%cv1%%
custom="'.esc_html($_SERVER["HTTP_HOST"]).'|cv1|cv2|cv3"
custom="'.esc_html($_SERVER["HTTP_HOST"]).'|christmas-promo"
Advanced Customization: Further customization is possible with the ws_plugin__s2member_welcome_email_sbj and ws_plugin__s2member_welcome_email_msg filters from a plugin or theme.
ws_plugin__s2member_welcome_email_sbj
ws_plugin__s2member_welcome_email_msg
This email notification is sent to you, each time a new User/Member registers.
"Name" <user@example.com>; admin@example.com; "Webmaster" <webmaster@example.com>
Advanced Customization: Further customization of the recipients, subject, and message is possible with the ws_plugin__s2member_admin_new_user_email_recipients, ws_plugin__s2member_admin_new_user_email_sbj, and ws_plugin__s2member_admin_new_user_email_msg filters from a plugin or theme.
ws_plugin__s2member_admin_new_user_email_recipients
ws_plugin__s2member_admin_new_user_email_sbj
ws_plugin__s2member_admin_new_user_email_msg
On the Main Site of a Multisite Network, the settings for Open Registration are consolidated into the s2Member → Multisite (Config) panel.
s2Member supports Free Subscribers (at Level #0), along with four Primary Levels [1-4] of paid Membership. If you want your visitors to be capable of registering absolutely free, you will want to "allow" Open Registration. Whenever a visitor registers without paying, they\'ll automatically become a Free Subscriber at Level #0.
Yes
The default Membership Levels are labeled generically; feel free to modify them as needed. s2Member supports Free Subscribers (at Level #0), along with several Primary Roles for paid Membership (i.e., Levels 1-4), created by the s2Member plugin.'.((!is_multisite() || !c_ws_plugin__s2member_utils_conds::is_multisite_farm() || is_main_site()) ? ' s2Member also supports unlimited Custom Capability Packages (see s2Member → API Scripting → Custom Capabilities)' : '').'. That being said, you don\'t have to use all of the Membership Levels if you don\'t want to. To use only 1 or 2 of these Levels, just design your Membership Options Page, so it only includes Payment Buttons for the Levels being used.
TIP: Unlimited Membership Levels are only possible with s2Member Pro. However, Custom Capabilities are possible in all versions of s2Member, including the free version. Custom Capabilities are a great way to extend s2Member in creative ways. If you\'re an advanced site owner, a theme designer, or a web developer integrating s2Member for a client, please check your Dashboard, under: s2Member → API Scripting → Custom Capabilities. We also recommend this video tutorial.
See also: These KB articles: s2Member Roles/Capabilities and Simple Shortcode Conditionals.
no
The button to the right, is a nifty tool, which allows you to reset s2Member\'s internal Roles and Capabilities that integrate with WordPress. If you, or a developer working with you, has made attempts to alter the default internal Role/Capability sets that come with s2Member, and you need to reset them back to the way s2Member expects them to be, please use this tool. Attn Developers: it is also possible lock-in your modified Roles/Capabilities with an s2Member Filter. Please see this KB article for details.
These settings customize your Standard Login/Registration Pages:('.esc_html(c_ws_plugin__s2member_utils_urls::wp_register_url()).')
The Main Site of a Multisite Blog Farm uses this Form instead, powered by your theme.('.esc_html(c_ws_plugin__s2member_utils_urls::wp_signup_url()).')
BuddyPress: BuddyPress will use its own Registration Form, powered by your theme.('.esc_html(c_ws_plugin__s2member_utils_urls::bp_register_url()).')
These settings are all focused on your Login/Registration Fonts.
These settings are all focused on your Login/Registration Background.
These settings are all focused on your Login/Registration Logo.
title=""
This field accepts raw HTML'.((!is_multisite() || !c_ws_plugin__s2member_utils_conds::is_multisite_farm() || is_main_site()) ? ' (and/or PHP)' : '').' code.
Some fields are already built-in by default. The defaults are: *Username*, *Email*, *First Name*, *Last Name*.
*Username*, *Email*, *First Name*, *Last Name*
Custom Fields will appear in your Standard Registration Form, and in User/Member Profiles:('.esc_html(c_ws_plugin__s2member_utils_urls::wp_register_url()).')
The Main Site of a Multisite Blog Farm uses this Form. s2Member supports Custom Fields here too.('.esc_html(c_ws_plugin__s2member_utils_urls::wp_signup_url()).')
BuddyPress: BuddyPress will use its own Registration Form here.s2Member can integrate your Custom Fields with BuddyPress too, please see options below.
Regarding Registration: Custom Fields do not appear during repeat registration and/or checkout attempts (i.e., they do not appear for any user that is currently logged into the site). Please make sure that you test registration and/or checkout forms while not logged in (i.e., please test as a first-time customer). Existing users, members, customers may update Custom Fields by editing their Profile.
Name
Note: Custom Passwords are easier for users. However, this has an impact on site security. Enabling Custom Passwords disables the New User Notification email that contains a password-setup link for each user. In other words, enabling Custom Passwords effectively disables any sort of email verification procedure, because the user is allowed to set their password during registration, instead of doing that via email confirmation—which is the default WordPress behavior.
* For security purposes, Custom Passwords are not possible on the Main Site of a Blog Farm. [?]
* Does not affect BuddyPress registration form (always yes with BuddyPress registration).
yes
Tip: Minimum length and password strength also impact profile updates, so it\'s a good idea to configure these even if you\'re not using Custom Passwords during registration.
info,help,admin,webmaster,hostmaster,sales,support,spam
Enter a comma-separated list of user fields that these shortcodes may display from a user account other than the person currently viewing the page. This applies to [s2Get user_id="" /] and [s2Member-List show_fields="" /].
[s2Get user_id="" /]
[s2Member-List show_fields="" /]
Only allow fields that are appropriate to reveal about other user accounts wherever these shortcodes are used. If either shortcode tries to display an unlisted field from another user account, that cross-user field value will be blocked and s2Member will show administrators a security notice with the fields that need review.
display_name, avatar, first_name, last_name, full_name
Please create and/or choose an existing Page to use as the first page Members will see after logging in.
BuddyPress: s2Member integrates with BuddyPress. Your Login Welcome Page affects BuddyPress too.
Always Private: This Page will always require a logged-in User/Member. In fact, this Page will be protected from public access by s2Member automatically. Note: for technical reasons, your Login Welcome Page cannot be set to your Front Page (i.e., your Home Page); or your Posts Page (i.e., your main Blog page). Please create a separate dedicated Page in WordPress, and then designate it as your Login Welcome Page below.
See also: This KB article: Customizing Your Login Welcome Page.
Welcome To Our Members Area
http://
https://
Please create and/or choose an existing Page that showcases your Membership Options. This special Page is where you\'ll insert the Payment Button(s) generated for you by s2Member (or Pro-Forms; if you\'re running s2Member Pro). This Page serves as your lead-in signup page (i.e., you\'ll give visitors one or more registration options here, and they\'ll pay for the option they choose).
Your Membership Options Page should detail all of the features that come with Membership to your site, and provide a Payment Button (or Pro-Form; if you\'re running s2Member Pro) for each Level of access you plan to offer. This is also the Page that anyone could be redirected to (by s2Member), should they attempt to access an area of your site that requires access to something they\'re currenty not allowed to view.
Tip: If you allow Open Registration (i.e., Free Subscribers), you might want to place a link on your Membership Options Page, which points directly to your free Registration Form, instead of routing a Customer through your Payment Gateway first. It\'s a matter of preference though. For further details, please check the section above: s2Member → General Options → Open Registration.
BuddyPress: Even with BuddyPress, s2Member still needs a Membership Options Page. This is where your Payment Buttons (or Pro-Forms; if you\'re running s2Member Pro) will go, giving people the ability to pay you. And again, this is also the Page that anyone could be redirected to (by s2Member), should they attempt to access an area of your site that requires access to something they\'re currenty not allowed to view.
Always Public: This Page must be public at all times. In fact, s2Member will not allow this Page to be restricted in any way. Note: for technical reasons, your Membership Options Page cannot be set to your Front Page (i.e., your Home Page); or your Posts Page (i.e., your main Blog page). Please create a separate (dedicated) Page in WordPress, and then designate it as your Membership Options Page below.
Membership Signup
Yes, enable MOP Vars
s2Member can be configured to redirect Members away from the default Profile Editing Panel that is built into WordPress. When/if a Member attempts to access the default Profile Editing Panel, they\'ll instead be redirected to the Login Welcome Page that you\'ve configured with s2Member. Why would I redirect away from the default Profile Editing Panel? Unless you\'ve made some drastic modifications to your WordPress installation, the default Profile Editing Panel that comes with WordPress is not suited for any sort of public access.
So instead of using this default Profile Editing Panel, s2Member provides you (the site owner) with a special Shortcode: [s2Member-Profile /]. You can insert this into your Login Welcome Page, or any Post/Page for that matter (even into a Text Widget). This Shortcode produces an Inline Profile Editing Form that supports all aspects of s2Member, including Password changes; and any Custom Registration/Profile Fields that you\'ve configured with s2Member. Alternatively, you can send your Members to a special Stand-Alone version. The stand-alone version makes it possible for you to open it up in a popup window, or embed it into your Login Welcome Page using an IFRAME. Code samples below.
[s2Member-Profile /]
BuddyPress: BuddyPress already provides Users/Members with a Profile Editing Panel, powered by your theme. If you\'ve configured Custom Registration/Profile Fields with s2Member, you can also enable s2Member\'s Profile Field integration with BuddyPress (recommended). For further details, see: s2Member → General Options → Registration/Profile Fields.
/wp-admin/
Shortcode (copy/paste), for an Inline Profile Modification Form:'."\n"; echo '
Stand-Alone (copy/paste), for popup window:
/", c_ws_plugin__s2member_utils_strings::esc_refs(home_url("/?s2member_profile=1")), file_get_contents(dirname(__FILE__)."/code-samples/current-user-profile-modification-page-url-2-ops.x-php"))).'" onclick="this.select ();" />
In a few special cases, long URLs generated by s2Member (i.e., those containing encrypted authentication details) will be shortened. A shortened URL prevents issues with very long links becoming corrupted by a Customer\'s email application. For instance, the Signup Confirmation Email that s2Member sends out to a new paying Customer may contain a link which is shortened to prevent corruption by email applications. By default, s2Member uses its own built-in short links, stored temporarily on your site. You can also choose a third-party URL shortener, configure a custom shortener, or disable shortening.
(i.e., GET request)
%%s2_long_url%%