Jason (Lead Developer)

Thanks for the follow-ups.

I’ve just read back through your thread here, and it appears that s2Member is behaving properly. Specific Post/Page Notifications are being processed when they should be.

* Please NOTE: The result of any action that’s suppose to be taken by your custom script (i.e. the one connected to the API Notification that s2Member sends) goes beyond the scope of what we’ll provide support for. That’s code that you’ve written.

That being said, we’ll be happy to help you track down the source of the issue.
Here are some things that I’d take a look at please.

1. Post a copy of the configuration line that you have for this API Notification. The one which shows the Replacement Codes that you’re sending to your custom script. Perhaps there is a problem there, like your script is not yet configured to receive all the values that it needs?

2. In the API Notification that you’re connecting to, enter an email address as well. Do you receive an email? API Notifications can be sent to either a URL, or just to an email address, or to both. So during your tests, I recommend that you have it sent to your email address and also to your custom script.

Debug log received. Thank you.
~ Investigating.

Let’s also take a look at your underlying PayPal IPN log file. All transactions are ultimately processed by s2Member’s core PayPal IPN processor, which is where Specific Post/Page Sale Notifications are processed. Please post the contents of your /s2member-logs/paypal-ipn.log file with the related entries. Or you can send them via email through this private contact form:
http://www.s2member.com/contact/

Hi there. Thanks for your inquiry.

Interesting. What you’ve described is already built-in. Any Custom Registration/Profile Fields that you configure as “required”, should be validated by s2Member during the initial registration.

It’s possible that you have a JavaScript error being introduced somewhere else on your site, which might be affecting s2Member’s ability to validate this input. Have you taken a look at your site in Firebug to check this? If not, please post a URL to your checkout form so we can have a look :-)

Hi there. Thanks for your inquiry.

Nothing jumping right out at me that’s related specifically to s2Member. Notices in DEBUG mode are to be expected. Current versions of s2Member are not designed to run in full DEBUG mode yet. See this article please: http://www.primothemes.com/forums/viewtopic.php?f=36&t=2692

I do see that you’re running out of memory. It looks like you’re hitting the current limit of 64MB. Have you tried raising that limit yet? See this article please: http://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP

Hi there. Thanks for the follow-up.

Thanks for sharing those details from Siteground. I can’t say that I sympathize with them in this regard. Apache 1.x is VERY old news, and this is a perfect case-in-point why Apache 1.x should be upgraded as soon as humanly possible. Apache v2.x has been available since the year 2000, and was adopted fully around 2004.

http://www.apachehaus.com/index.php?option=com_content&view=article&id=119&Itemid=104

As a developer who constantly works with security-related issues and PCI compliance, I can tell you there are more security issues related to Apache 1.x than just mod_status. While this company might be actively working with a custom variation of this software, I can’t advise that you run s2Member with this host. You might try MediaTemple.net, HostGator, BlueHost, or another WordPress-recommended hosting provider. See: http://wordpress.org/hosting/

All of that being said… if this is all that’s causing a problem for you; you can simply omit it, as you’ve already done. This is only required if you’re running protected File Downloads with s2Member. Either that, or you might try this slight variation to see if it helps any.

# BEGIN s2Member GZIP exclusions
#
# RewriteEngine On
# RewriteBase /
# RewriteCond %{QUERY_STRING} (^|?|&)s2member_file_download=.+
# RewriteRule .* – [E=no-gzip:1]
#
# END s2Member GZIP exclusions

Hi there. Thanks for your inquiry.
It looks like that CAPTCHA is being introduced by another 3rd-party plugin?
If that’s correct, I would suggest that you modify the tabindex value in that 3rd-party plugin to a higher value. It’s currently set to a value of 30, which comes after the password fields.

By the way. As an s2Member Pro Customer, you have the ability to use Pro Forms, which include this functionality already. If you’re going for free registration, please see:
s2Member -> PayPal Pro Forms -> Free Registration Forms

I’ve also done a video here which might be of some assistance to you.
http://www.s2member.com/videos/330982E83739ABDF/

Hi Grace. It is possible to configure Custom Registration/Profile Fields in different ways, where each Field that you create will appear only at certain Membership Levels. For instance, if you create a Custom Registration/Profile Field and specify Level #1 only, that field will ONLY appear on Pro Forms associated with access to Membership Level #1.

In addition, it is also possible to configure a Custom Registration/Profile Field so that it only shows up during registration, or only during profile edits, or only during registration and then hidden (i.e. not shown in Profile edits). See screenshot below please.

* Please note. Once a customer is registered (i.e. they have an account), s2Member Pro Forms will NOT display your Custom Registration Fields again on future visits to a Pro Form. If the customer is already logged-in, s2Member assumes this information has already been collected. The customer can edit their Profile of course to change these values.

* If you require some additional functionality that goes above and beyond what I’ve discussed here, you might consider modifying your Pro Form template files in more creative ways. Pro Form template files may also contain PHP code, making them very versatile. See: http://www.s2member.com/faqs/#s2-faqs-pro-form-template-mods

We’ll be happy to assist in any way that we can. Feel free to invite the developer of this other plugin to write in through our Community Support Forums, or investigate the core WP function I mentioned.

Hi there. Thanks for your inquiry.
Try it like this please, with the inline specification. Does this help?

http://rockitscience.com/wordpress/wp-content/plugins/s2member-files/s2member-file-inline/howtopresentourlessons.pdf

* Please test in the latest release of s2Member v120213, which resolved some issues with GZIP conflicts, related to protected file downloads.

Changelog here: http://www.s2member.com/changelog/

If problems persist, please let me know what web server you’re running. Is it Apache?

Hi there. Thanks for your inquiry.
~ I sincerely apologize for the delayed response.

Importing existing Members with s2Member allows you to include the Subscription IDs associated with any existing Members, so that s2Member can receive future communication about these Members from PayPal’s IPN service.

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.

Feature requests received. Thank you!

Hi there. Thanks for your inquiry.

Users/Members are NOT shared across the Network. Each child blog or sub-site in a Network runs its own instance of s2Member®.

Yes, that is correct. Each Child Blog within a Network has it’s own instance of s2Member, so it’s not going to work in the scenario that you laid out. While this type of installation is not currently supported by s2Member, we do have clients working around this issue through existing functionality within WordPress, which can test a Customer’s permissions on the Main Site.

In other words, you might have s2Member installed only on your Main Site, and you grant all sorts of access there. If you need to grant permission to something on a Child Blog, test permissions on the Main Site from other Child Blogs using one of these functions.

Here are some functions that I would recommend to you.
http://www.s2member.com/codex/stable/s2member/api_functions/package-functions/#src_doc_current_user_is_for_blog()
http://codex.wordpress.org/Function_Reference/current_user_can_for_blog

For example, on a Child Blog, you might have something like this:

<?php
if(current_user_can_for_blog(1, "access_s2member_level1"))
	{
		echo 'You are a paid Member of our Main Site.';
	}
?>

• This reply was modified 4 years, 10 months ago by  Jason (Lead Developer).