Raam Dev

Hi,

Please see Dashboard -› s2Member® -› API / Scripting -› Pro Login Widget (via PHP).

Hi Tim,

You need to make sure that when you create the Custom Registration Fields that you set “Applicable Membership Levels” to all, or to the Level Pro-Form that you want the field to show up on.

Hi Jeffry,

You could use Payment Notifications (see Dashboard -› s2Member® -› API / Notifications -› Payment Notifications) to retrieve the total payment amount for each transaction. Will that work?

Hi Stuart,

This is not currently possible with the Pro-Coupon codes. However, we will take that feature into consideration for a future version of the plugin.

Hi Hamid,

The first thing I noticed is that you have two extra double-quotes on the success= attribute.

This:

success=""http://www.domain.com/thank-you/?email=%%user_email%%&fname=%%user_first_name%%&gender_title=%%gender_title%%""

should be:

success="http://www.domain.com/thank-you/?email=%%user_email%%&fname=%%user_first_name%%&gender_title=%%gender_title%%"

Regarding the email issue: Can you tell me what “Allow Custom Passwords during Registration?” is set to in Dashboard -› s2Member® -› General Options -› Registration/Profile Fields?

Regarding passing Custom Registration Fields in the success URL: You should be able to use %%gender_title%%. Please see Dashboard -› s2Member® -› PayPal® Pro Forms -› Custom Return URLs Upon Success.

Hi Kevin,

While s2Member is compatible with WordPress Multisite Networking, the sites within a WordPress network are separate and not interconnected. That means you cannot share users, logins, or other data across the sites (including access control).

Please see the following from WordPress.org:

The sites in a multisite network are separate, very like the separate blogs at WordPress.com. They are not interconnected like things in other kinds of networks (even though plugins can create various kinds of interconnections between the sites). If you plan on creating sites that are strongly interconnected, that share data, or share users, then a multisite network might not be the best solution.

The s2Member Multisite feature allows you to offer the s2Member plugin to sub-sites, giving your sub-sites the ability to setup and use s2Member on their own. When you upgrade s2Member on the primary site, the s2Member plugin is automatically updated for all your sub-sites. However, things like access restrictions on one WP installation are not shared across WP installations (again, the WordPress Multisite feature itself isn’t designed to work like that).

There are plugins that allow you to get around these WordPress Multisite limitations, however they may or may not work with s2Member.

Hi John,

Please see the example script (/s2m-pro-extras/paypal-central-ipn.php) inside s2m-pro-extras.zip. The comments in that file contain instructions for setting this up.

Hi Alexander,

Another support member gave me a few ideas for how you’d be able to make this scenario work with s2Member:

You could use Custom Capabilities and create a Custom Capability for each music file.

You’d need to create an upload feature for the musicians that uploads their song into a folder in plugins/s2member-files/ so that the song is protected by s2Member. Then, you’d have your musicians create PayPal buttons using their own PayPal accounts but following these instructions to integrate their button with your s2Member installation (they’ll also need to add the Custom Capability for that song to the PayPal button when they create it).

When a purchaser uses one of those PayPal buttons to purchase a song, the IPN message from PayPal indicating the purchase was complete will also include the Custom Capability for that song and the Custom Capability will be added to that users account, thereby giving them access to download the song (you’d have a page set up with a download link for the song that requires the Custom Capability for that song).

You could use Advanced Download Restrictions to protect the download links on the download pages (see Dashboard -› s2Member® -› Download Options -› Advanced Download Restrictions).

I’m not sure why it’s not working, but I found where you can remove it manually: plugins/s2member/includes/s2member-min.js

You’ll want to make a backup of your changed file so that you can restore it after s2Member upgrades.

If you want to disable file download confirmations altogether, you can add this to your s2-hacks.php file:

<?php
add_action ("ws_plugin__s2member_before_sc_get_file","s2file_skip_confirmation_by_default");
function s2file_skip_confirmation_by_default($vars){
	if (!array_key_exists("skip_confirmation",$vars&#91;"attr"&#93;)) $vars&#91;"attr"&#93;&#91;"skip_confirmation"&#93;="yes";
}
?>

Hi Greg,

The is_singular() conditional tag checks if a singular page is being displayed. The code above will only ever return a singular page, so there really isn’t any point in checking that.

I’m not sure where the has_media_embed() function comes from (it’s not a WordPress function), but if you needed to add it, you’d do the following:

<?php

$_g = stripslashes_deep ($_GET);


if (isset ($_g&#91;"_s2member_seeking"&#93;&#91;"post"&#93;) && has_media_embed()) {

	$post_id = esc_html ($_g&#91;"_s2member_seeking"&#93;&#91;"post"&#93;) ;
	
	$post_object = get_post( $post_id );

	echo $post_object->post_title;
}
?>

Hi Stéphane,

s2Member does not handle the creation of sub-sites, this is handled by WordPress itself.

While s2Member is compatible with WordPress Multisite Networking, the sites within a WordPress network are separate and not interconnected. That means you cannot share users, logins, or other data across the sites (including access control).

Please see the following from WordPress.org:

The sites in a multisite network are separate, very like the separate blogs at WordPress.com. They are not interconnected like things in other kinds of networks (even though plugins can create various kinds of interconnections between the sites). If you plan on creating sites that are strongly interconnected, that share data, or share users, then a multisite network might not be the best solution.

The s2Member Multisite feature allows you to offer the s2Member plugin to sub-sites, giving your sub-sites the ability to setup and use s2Member on their own. When you upgrade s2Member on the primary site, the s2Member plugin is automatically updated for all your sub-sites. However, things like access restrictions on one WP installation are not shared across WP installations (again, the WordPress Multisite feature itself isn’t designed to work like that).

There are plugins that allow you to get around these WordPress Multisite limitations, however they may or may not work with s2Member.

If you wanted to automatically create a sub-site upon the completion of a new s2Member membership on your primary site, you could certainly add that functionality by hooking into s2Member (you’d probably use one of the s2Member PayPal hooks).

Just to clarify: the s2Member Multisite integration extends usage of the s2Member plugin to your sub-sites, giving those sub-sites the opportunity to set up a membership site of their own. The s2Member Multisite integration does not handle the configuration or creation of your sub-sites in a multisite installation.

James,

I took a look at your site and here’s what I discovered: The JavaScript that prefills the fields on your upgrade form is not loading the logged-in user’s details. That would indicate there is a JavaScript conflict somewhere, most likely caused by one of your other plugins but even possibly by your theme.

I noticed you’re running the Shortcodes Ultimate plugin. That plugin is known to conflict with s2Member (a quick search will turn up several threads about this).

I recommend disabling the Shortcodes Ultimate plugin and testing again to see if the upgrade form prefills.

Glad to help! :)