Raam Dev

Hi Tyron,

As Jean-Michel explained, you can use the s2Member conditionals (Dashboard -› s2Member® -› API / Scripting -› Simple/Shortcode Conditionals and Dashboard -› s2Member® -› API / Scripting -› Advanced PHP Conditionals) to restrict access to content, but there is not currently any feature for specifying a CSS class that should be restricted.

Hi Tyron,

You can create Custom Registration/Profile fields in Dashboard -› s2Member® -› General Options -› Registration/Profile Fields and then when you display a Pro-Form (Dashboard -› s2Member® -› PayPal® Pro Forms -› Quick Start Guide) those fields will appear there.

Hi Gary,

s2Member includes a feature called Custom Registration/Profile Fields. That allows you to create custom profile fields and display them during registration. Those fields are editable through the Edit User option within the WordPress Dashboard. You can also use the inline s2Member Profile Modification form (Dashboard -› s2Member® -› General Options -› Member Profile Modifications) to give your users the ability to edit their profile.

Hi Chris,

Thank you very much for all the detailed information. I’m going to forward this thread to Jason, the lead developer, to get his input. To my knowledge, PayFlow is only applicable to recently opened PayPal Pro accounts.

A few months ago PayPal changed the API for newly created PayPal Pro accounts, while leaving older PayPal Pro account running under the older API. As a result, s2Member needed to accomodate both scenarios (old PayPal Pro accounts and new PayPal Pro accounts), which is why you see both options in there. If you have a Payflow account, you simply ignore the PayPal Account Details section and fill in the Payflow Account Details section.

If you see a DPRP is disabled error, I believe that indicates that your PayPal account doesn’t have the service required for what you’re trying to do. If you’re trying to process a recurring subscription with your PayPal Pro account, please contact PayPal and make sure that your PayPal Pro account also has the Recurring Billing option (it’s an add-on to PayPal Pro and must be specifically requested).

So at this point it looks like the latter may be your only problem. If you successfully created a PayPal Subscription using the Payflow settings, that would indicate that you do have a Payflow account. Since credit card subscriptions did not work and you received the DRP is disabled error, I suggest contacting PayPal with this error message and asking them to confirm your account has everything it needs.

I do not currently know of any issues with s2Member’s PayPal integration, whether using PayPal Express, PayPal Pro, or Payflow. However, I will forward this message to Jason to see if he can offer any further advice. He’s a lot more familiar with the various gateway integrations and should be able to explain things with more detail than I can. Thank you for your patience.

Hi Quentin,

Thank you very much for the screenshot. Could you please also show us exactly what code you’re using for this hack? I would like to double-check that there are no bugs that might be causing this problem.

Hi Gary,

The majority of your integration and above questions revolve around the usage of the Gravity Forms plugin. I’m not familiar with how that plugin works, so I cannot comment on its usage. However, I can say that s2Member uses the WordPress userbase, meaning all s2Member users are effectively WordPress users with an s2Member “Role” (i.e., s2Member Level).

For giving each member different capabilities, you can use the s2Member Custom Capabilities feature. Any validations you need to do with regards to checking if a user ID exists would be done using WordPress functions (e.g., username_exists(), docs here).

With s2Member Pro, you can also use our Import/Export feature to build a Excel CSV file that contains all your user data and import everything all at once.

Let us know if you have any other questions.

Hi Mike,

Yes, you are correct that it’s not working because you’re using the Authorize.net forms. The code in that original post is for customizing the default WordPress registration page (you can tell because it hooks into the login_head action).

However, since writing that post, I’ve also customized this hack to work on a PayPal Pro-Form on my website; you can see that code below:

<?php
add_action ("ws_plugin__s2member_pro_before_sc_paypal_form", "s2_customize_pro_form", 1000);
function s2_customize_pro_form ($vars = array())
    {
	/*  Don't pre populate when/if the Pro Form has just been POSTd, and/or if it's a Modification Form 
		with modify="1", because s2Member already pre populates Pro Forms in that scenario, with the 
		User's existing Email and Username. */
	if(empty ($_POST&#91;"s2member_pro_paypal_checkout"&#93;) && empty($vars&#91;"attr"&#93;&#91;"modify"&#93;)) {
?>
        <script type = "text/javascript">
		function getParameterByName(name)
		{
		  name = name.replace(/[\[]/, "\\\[").replace(/[\]]/, "\\\]");
		  var regexS = "[\\?&]" + name + "=([^&#]*)";
		  var regex = new RegExp(regexS);
		  var results = regex.exec(window.location.href);
		  if(results == null)
		    return "";
		  else
		    return decodeURIComponent(results[1].replace(/\+/g, " "));
		}
		
            (function ($) /* Wraps this `$ = jQuery` routine. */
                {
                    $.fn.swapWith = function (to) /* Utility extension for jQuery. */
                        {
                            return this.each (function ()
                                {
                                    var $to = $ (to).clone (true), $from = $ (this).clone (true);
                                    $(to).replaceWith ($from), $ (this).replaceWith ($to);
                                });
                        };
                    /**/
                    $(document).ready (function () /* Handles email-to-username on keyup. */
                        {	
								
						/* Generate random number to append to username, 
                        hopefully making it unique (yes, this isn't perfect!) */
                        var randomNum = Math.ceil(Math.random()*999);

                        if($('input#s2member-pro-paypal-checkout-email').length) {
							var email = 'input#s2member-pro-paypal-checkout-email';
							var login = 'input#s2member-pro-paypal-checkout-username';
							//$('#s2member-pro-paypal-checkout-form-username-div').hide();
						} else {
							var email = 'input#s2member-pro-paypal-registration-email';
							var login = 'input#s2member-pro-paypal-registration-username';
							//$('#s2member-pro-paypal-registration-form-username-div').hide();
						}
						
						

                        /* Fill hidden username field with first part of email address
                            and append randomNum to hopefully make it unique. */
                        $ (email).keyup (function ()
                            {
                                $(login).val ($.trim ($ (email).val ().split (/@/)[0].replace (/[^\w]/gi, '')) + randomNum.toString());
                            });								
                        });
                }) (jQuery);
        </script>
<?php
		}
    }
?>

You’ll notice that the main difference is at the top, where you can see the action being hooked into (ws_plugin__s2member_pro_before_sc_paypal_form). That causes this code to run on the PayPal Pro-Forms for membership levels (Dashboard -› s2Member® -› PayPal® Pro Forms -› Membership Level # Forms).

You will need to locate the correct hook for the Authorize.net form that you’re using (probably ws_plugin__s2member_pro_before_sc_authnet_form) and change that in the hack.

You’ll also need to do “view source” when displaying your Authorize.net Pro-Form on a page and locate the correct names of the email and username fields (e.g., input#s2member-pro-paypal-checkout-email should be changed to whatever it’s called on the Authorize.net Pro-Form) and then update those names in the hack.

Finally, you’ll notice that I commented out the following on lines 44 and 48:

//$('#s2member-pro-paypal-registration-form-username-div').hide();

That code hides the Username section. I recommend leaving those lines commented out so that you can see if the username is actually being automatically generated when you type in the email address. Then, once you’re sure that it’s being generated, you can hide that section by uncommenting those lines (remove the leading //).

This code should go in a PHP file in your wp-content/mu-plugins/ folder. If that folder doesn’t exist, you should create it. You can call the PHP file anything, but I recommend naming it s2hacks.php. Any PHP files in that directory will automatically be loaded every time you load a WordPress post/page.

Glad to hear you solved this, Jason. I will go ahead and close this ticket.

Hi Donn,

s2Member does not currently have a renewal notifications feature, but we’re working on it for the next major release of the plugin. For now, you may want to use MailChimp or AWeber schedule renewal notifications or you might want to try one of the renewal notifications hacks created by other s2Member users (here and here).

Genie,

The URL that comes up after checkout contains extra information about the transaction. It’s not going to be the exact same URL that you enter in s2Member. So, that part is correct. Nothing wrong there.

You have enabled logging. Good. Now we need to look at those log files to see if they can offer us any clues as to what is going on here.

The log files are located in wp-content/plugins/s2member-logs/. Can you please use FTP, download the log files in that directory, open them up with a text editor (such as Notepad), and locate the entries related to your test transactions. The best way to locate those entries is by searching for the Transaction ID or Subscription ID associated with the transaction. Then, you can copy/paste them here (please enclose the entries in code tags to keep the formatting).

Hi Johnny,

Not sure…how would I know which is which?

Can you copy/paste here the URL to the login page that’s give you the 404 error?

Is it mandatory to get Paypal Payments Pro ?

No, it’s not mandatory. Please see the following from Dashboard -› s2Member® -› PayPal® Pro Forms -› Quick Start Guide:

*PayPal® Pro is NOT Absolutely Required* s2Member is very flexible. It is now possible to integrate Pro Forms without a PayPal® Pro account, whereby the enhanced Form Shortcodes that s2Member provides can be integrated ONLY with PayPal® Express Checkout. In other words, if you get declined for PayPal® Pro service, you can still use s2Member Pro Forms. Ask PayPal® to activate Express Checkout for you. ( it’s free ). Once Express Checkout is enabled, you will have access to your PayPal® API Credentials. Log into your PayPal® account, and navigate to Profile -> API Access (or Request API Credentials). You’ll choose ( Request API Signature ). Now … here is the tricky part; whenever you generate a Pro Form Shortcode with s2Member, be sure to change accept=”paypal,visa,mastercard,amex,discover,maestro,solo” to just accept=”paypal”; thereby excluding the on-site credit card processing functionality; which is available only with PayPal® Pro.

Johnny,

You don’t want files to be downloaded inline… inline means it will try to load in the web page or in the default player. Try removing everything from Dashboard -› s2Member® -› Download Options -› Inline File Extensions and testing again.

Hi Emmanuel,

There might be a problem with the umask on your web hosting account. I suggest contacting your web hosting company to see if they can fix it for you. You can try changing the permissions on the folder yourself by taking a look at what permissions are assigned to the wp-content/plugins/s2member-files/ folder and copying those.

Also, please keep in mind that for this line:

return '/server/path/to/other/download/directory';

you must use the full path to the folder, not the relative path. You cannot use /wp-content/uploads/members/. You must use the full path, such as /home/username/www/wp-content/uploads/members/. If you don’t know the full path, you can get that from your web hosting company.