Community Support Forums

1. Am I correct that s2Member will use PDT information to set a user's Level (before IPN comes through)?
2. By not using /?s2member_paypal_return=1, am I losing this capability (such that IPN is then the ONLY way level will be upgraded)?

Code: Select all

[s2Member-PayPal-Button ... success="http://www.example.com/my-thank-you-page/" ... /]

Code: Select all

/?s2member_paypal_return=1&s2member_paypal_return_success=http://www.example.com/my-thank-you-page/

success="" Success Return URL ( optional ). s2Member handles this automatically for you. However, if you would prefer to take control over the landing page after checkout ( i.e. your own custom Thank-You Page ), you can. If supplied, this must be a full URL, starting with http://. Note, s2Member will NOT use this value if an existing account holder is being modified. s2Member handles account updates ( i.e. billing modification ) in a more dynamic way. Your Success Return URL is only applied to (new) Customers.

Code: Select all

<?php
add_filter ("ws_plugin__s2member_redirection_url_after_modification", "my_redirection_url_after_modification");
function my_redirection_url_after_modification ($s2member_default_value, $vars = array ())
    {
        return ($my_custom_url = "http://example.com/thanks-for-upgrading/");
        // print_r($vars); for debugging, if you need more information before creating this URL.
    }
?>

Jason Caldwell wrote:Hi there. Yes, you are correct in both A and B assumptions.

A "modification" takes place any time an existing User/Member is going through the checkout process, period. In other words, anytime s2Member is "modifying" an existing account within WordPress ( i.e. if they already have a User ID in the database, all transactions are modifications, because s2Member is modifying an existing account. ).

Jason Caldwell wrote:This forces s2Member to do the following after PayPal checkout:

Code: Select all

/?s2member_paypal_return=1&s2member_paypal_return_success=http://www.example.com/my-thank-you-page/

In other words, s2Member processes PDT, and then redirects the Customer to your own custom page, specified in the success="" Shortcode Attribute, which ends up in the query string like you see here.

What is the best, most cost effective way to help get members through the payment process, registered, and able to use the site?

By default, s2Member will send a Customer directly to PayPal®, and only after checkout is completed does the Customer have the ability to register a Username/Password for access to your site. This process works very well in most cases, and it has the benefit of increasing conversion rates; because there are fewer obstacles for the Customer on their way to the actual checkout process at PayPal®.

That being said, we believe the "ideal" approach is a combined Checkout/Registration process; in just one simple step ( available with s2Member Pro via PayPal® Pro integration ). But even with PayPal® Standard integration, there is a way to accomplish (registration before checkout), thereby reversing the process — if you prefer it that way. This is accomplished by turning Open Registration (on), and then making a PayPal® Button available to Free Subscribers at Level #0. In other words, you can let visitors register for free at Level #0, then charge them for access to higher Member Levels [1-4]. For further details, please check your WordPress® Dashboard under: s2Member -> General Options -> Open Registration. If you're running a Multisite Network, see: s2Member -> Multisite (Config) -> Registration Configuration.

s2Member's Simple Conditionals can help you further integrate this process, by allowing you to integrate a special PayPal® Button on your Login Welcome Page; one that will be seen only by Free Subscribers at Level #0. Please check your WordPress® Dashboard under: s2Member -> API Scripting -> Simple Conditionals. We also suggest reading over the documentation on PayPal® Modification Buttons. See: s2Member -> PayPal® Buttons -> Subscription Modifications.

Jason Caldwell wrote:Or, you can use this Filter, perhaps something like this:

Create this directory and file:
/wp-content/mu-plugins/s2-hacks.php

Code: Select all

<?php
add_filter ("ws_plugin__s2member_redirection_url_after_modification", "my_redirection_url_after_modification");
function my_redirection_url_after_modification ($s2member_default_value, $vars = array ())
    {
        return ($my_custom_url = "http://example.com/thanks-for-upgrading/");
        // print_r($vars); for debugging, if you need more information before creating this URL.
    }
?>

[i]Using this Filter, makes it possible for you to redirect an "existing" User/Member after they complete checkout ( i.e. after a modification takes place ), and s2Member's PDT processing WILL still take place, even though you're re-routing the Customer to your own custom URL here. This Filter is the recommended way to handle "existing" User/Member modifications, with your own custom URL, like you see here.

Cristián Lávaque wrote:Kregg, that variable that Jason suggested, would go in the return URL you enter in your PayPal settings. PayPal -> Account Profile -> Website Payment Preferences -> Auto-Return URL