Raam Dev

ALL Custom Capabilities are removed upon demote, regardless of how they were added.

We understand this creates several limitations, so we’ve changed how this works in the next major release of the software.

Hi Tammy,

Yes, depending on what you’re using (buttons or forms) they will either create their password during checkout (Pro-Forms), or they will be emailed a link to register after payment (Buttons).

No, they will not have administrative access. All of the s2Member Levels are based on the WordPress Subscriber role, which only allows viewing of content (i.e., no access to the administrative backend). If you also want to redirect members away from the default WordPress Profile editor, you can set that in Dashboard -› s2Member® -› General Options -› Member Profile Modifications.

Hi Addison,

Does that page still exist? What happens if you disable s2Member and then try visiting that page?

Hi Ganaxi,

The best, and only, way to test those would be to change the expiration to something shorter, as you mentioned.

When you create the Custom Registration field in Dashboard -› s2Member® -› General Options -› Registration/Profile Fields, you can set the “Allow Profile Edits” option to No ( uneditable & totally invisible, both during & after registration ) and it won’t show up during registration or on any front-end profile editing pages.

Hi Rob,

I recommend creating a Must-Use Plugin that checks if $_GET[‘s2member_paypal_proxy’] is set and then pull the stuff you need from $_POST (you probably want $_POST[‘txn_id’]).

You can use print_r() to see what’s inside $_POST like this:

<?php
 if ($_GET&#91;'s2member_paypal_proxy'&#93; === 'clickbank')
    {
        print_r($_POST);
        exit;
    }
?>

Hi Addison,

I got a 404 (not found) error when trying to visit that link. Have you tried switching to the default TwentyEleven theme to see if that fixes the problem? Also, you may want to take a look at Knowledge Base » Common Troubleshooting Tips.

Hi Tony,

Yes, all of this can be achieved with s2Member. You will need to make extensive use of two features in particular: Content Dripping and Custom Capabilities.

Download Restrictions come in two flavors: Basic (see Dashboard -› s2Member® -› Download Options -› Basic Download Restrictions) and Advanced (see Dashboard -› s2Member® -› Download Options -› Advanced Download Restrictions). With Advanced download restrictions, you can create URLs that contain a unique, automatically generated key which expires 24 hours from generation.

The Custom Value field will get overwritten upon payment. It gets overwritten by whatever is in the custom=”” attribute of your shortcode.

You have the right idea though. You could instead create a Custom Registration Field (Dashboard -› s2Member® -› General Options -› Registration/Profile Fields) that is hidden from the user (i.e., only you can see it), and then use that to store your “elr”. Then, your conditional on the Login Welcome Page can check that Custom Field: see S2MEMBER_CURRENT_USER_FIELDS in Dashboard -› s2Member® -› API / Scripting -› PHP/API Constants).

Hi Geoffrey,

If you’ve already changed the names of the Levels in Dashboard -› s2Member® -› General Options -› Membership Levels/Labels but you’re still seeing the old names, please try clearing your web browser cache and temporary files.

If that doesn’t fix the problem, you may want to try deactivating and reactivating the s2Member plugin (make sure Deactivation Safeguards are enabled first in Dashboard -› s2Member® -› General Options -› Deactivation Safeguards).

Hello,

s2Member does support the sale of individual products. Please see Dashboard -› s2Member® -› PayPal® Pro Forms -› Specific Post/Page (Buy Now) Forms. You may also be interested in watching the s2Member (Specific Posts/Pages) video, which describes this feature.

Glad I could help! Let us know if you have any other questions. :)

If nothing is being logged since this morning, even though you’re still doing tests and logging is still enabled, that would indicate something else is going on, i.e., a permissions issue in writing to the log file or communications issues between your server and PayPal.

I would try disabling s2Member and then reactivating it (make sure Deactivation Safeguards are enabled in Dashboard -› s2Member® -› General Options -› Deactivation Safeguards). I would also try disabling all other WordPress plugins and testing again to rule out a conflict with another plugin.

If you recently changed servers, then keep in mind that changes to the DNS system were made as well. Servers and routers on the internet cache (i.e., keep a copy) of the DNS information and only update that cache every 24-72 hours. It’s possible that MailChimp’s servers, or a router in between your server and MailChimp, have an old DNS cache and it’s trying to communicate with the IP address associated with the old server.

However, if you’re not even getting anything logged in the s2Member logs, then something is wrong “closer to home”, i.e., on the server itself, so I’d start there.