You will need the Pro version of s2Member, in order to have access to the pro-forms.

Go to WP Admin -> s2Member -> PayPal® Pro Forms -> PayPal® Pro / Free Registration Forms, there, copy the shortcode that appears, and paste in the page where you want the registration.

Now the shortcode should be something like this:

[s2Member-Pro-PayPal-Form register="1" level="0" ccaps="" desc="Signup now, it's Free!" custom="your-website-url.com" tp="0" tt="D" captcha="clean" /]

The only thing you really need to change is the level="0", and change it to level="1" (replace the 0 with the level you want to offer).

So now it would look like this:

[s2Member-Pro-PayPal-Form register="1" level="1" ccaps="" desc="Signup now, it's Free!" custom="your-website-url.com" tp="0" tt="D" captcha="clean" /]

You could also offer CCaps in this manner, just modify the ccaps="" and add, between the quotes, the names of the CCaps you want to offer. Remember to separate them by commas.

So it should look like this:

[s2Member-Pro-PayPal-Form register="1" level="0" ccaps="ccap1, ccap2" desc="Signup now, it's Free!" custom="your-website-url.com" tp="0" tt="D" captcha="clean" /]

It is recommended to use the shortcode for security reasons.

The Pro-Forms will grab any custom fields that you have set up under WP Admin -> s2Member -> General Options -> Registration/Profile Fields & Options.

Here is a screenshot of Pro-Form in it's default state (click to enlarge):

<?php
add_filter ("ws_plugin__s2member_aweber_bcc", "s2_aweber_bcc"); function s2_aweber_bcc ()
  {
    return get_bloginfo ("admin_email");
  }
?>

I would suspect that you’ve created a conflict by mistake. s2Member will not allow you to generate a Payment Button that facilitates Specific Post/Page Access, with any Post/Page which is already protected with Membership Level Restrictions (of any kind). WP Admin -> s2Member -> Restriction Options -> Specific Post/Page

Also, please be careful not to create a conflict with other Access Restrictions. If you are going to sell Specific Post/Page Access, you should enter specific Post/Page IDs here; and make SURE that you’ve NOT already protected any of these Posts/Pages with Member Level Access Restrictions. In other words, if you configure s2Member, in such as a way, that a Post/Page requires Membership Level Access, you cannot sell that same Post/Page through Specific Post/Page Access. Doing so, would create a conflict. Customers that purchased Specific Post/Page Access, would be unable to access the Post/Page – without also having a Membership. Not good. So please be careful.

In other words, if the Posts/Pages are not showing up in the Button Generator, it’s most likely because those Posts/Pages are already protected by s2Member’s Membership functionality in some way. I would review all of your s2Member -> Restriction Options to be sure these Posts/Pages (i.e. the ones that are NOT showing up) are ONLY protected with Specific Post/Page Restrictions, and nothing else. Look for anything which includes multiple areas of your site, like Tag Restrictions, Category Restrictions, URI Restrictions, or the special keyword “all”.

So, if you include the Paid Subscr. ID value when you do the import, and your PayPal IPN URL is reporting properly to your installation of s2Member (i.e. yoursite.com/?s2member_paypal_notify=1), s2Member can automate the management of these paying customers.

This includes any associated payments, cancellations, refunds, chargebacks, etc. If s2Member has the Paid Subscr. ID value, and PayPal is sending s2Member IPNs, these events can be handled by s2Member, including any EOTs (End Of Term) events.

Now, in practice. This is not always easy to accomplish. For instance, if your previous membership software used PayPal Button integration, and an IPN URL was established on a per-transaction basis, it might not be possible to update the IPN URL for each of your existing Members before importing them into s2Member (e.g. PayPal has some limitations in this regard).

Another issue is that s2Member expects to receive IPN data with the PayPal “custom” value set to your installation domain name, and with a proper item_number value, matching s2Member’s standardization. Further details on this in your Dashboard under:
s2Member -> PayPal Options -> IPN Integration.

In cases where these technical challenges get in the way of a smooth migration, we recommend that you import your existing userbase with a pre-configured EOT Time. Setting the EOT Time during your import will ensure that s2Member terminates each Member’s access at the correct point in time, based on the data in your import, and without any reliance on existing IPN communication, which might have previously been configured to work with an entirely different software application.

Using a manual EOT Time when importing Users/Members from software applications you used prior to running s2Member, is a very reliable way to deal with things. It leaves little doubt about how s2Member and any existing IPN data might be handled in the future. A pre-configured EOT Time establishes the exact date on which a Member’s account will lose paid access. After import, this value can also be changed by editing the Member’s account from within your WP Dashboard.

It can be found under WP Admin -> s2Member -> Restriction Options -> Brute Force IP/Login Restrictions.

By default, this option is set to "Allow 5 failed login attempts (then punish for 30 minutes)". You might want to adjust this to meet your needs. These restrictions can be easily removed (STRONGLY DISCOURAGED).

This restriction is easily reset, by 1 of 2 ways:

1. If you want to do it on a general scope for all your users, then simply under brute force restriction options, click the button that says "Reset Brute Force Logs".
2. If you only want to do it for certain users, then go to WP Admin -> Users -> All Users, then find the user(s) for which you want to reset the restriction, click "Edit", then scroll down (depending on the size of your screen) to the s2Member section, in there make sure the "Yes, delete/reset IP Restrictions associated with this Username." checkbox is checked, then click "Update Profile" at the bottom of the page.

These restrictions also apply to admin accounts, so make sure to remember your password, or you will be locked down depending on the settings.

Simply put the URL of the photo you want to use between the quotes in the image="" attribute.

So for example:

[s2Member-PayPal-Button ... image="http://mysite.com/images/my-button.png" /]

Now you can use a more stylish button that fits your website, instead of using the default.

For example, if you configure Custom Registration/Profile Fields for Members at Level #1, they’ll only be displayed during registration if your Pro Form is configured to provide access to Level #1. WP Admin -> s2Member -> General Options -> Registration/Profile -> Custom Field -> Applicable Membership Levels

Please use comma-delimited Level #’s: 0,1,2,3,4 or type: all.
This allows you to enable this field – only at specific Membership Levels.

Also, if you’re already logged-in when you test your Pro Forms, you won’t see these fields, because s2Member assumes they’ve already been collected (i.e. you’re already logged in). Please log out before testing.

Please check under WP Admin -> s2Member -> General Options -> Email Configuration.

Here you can customize the name the email appears to be from. You can also customize from which email address it's coming from.

In there, make sure the option at the bottom is in "Yes ( Customize new user emails with s2Member )".

Then just click "click to customize" in each of the two emails in order to customize them.

You will find that you have at your disposal many special Replacement Codes, use them as you see fit in order to customize the email: