Jason (Lead Developer)

Please see: https://github.com/WebSharks/s2Member/issues/35
This update will come in the next maintenance release. Thanks for reporting this important issue.

What I still don’t get is why is this problem unique to S2Member? Is there something about the implementation that has caused this? Maybe it uses some PPal functions that are being deprecated?

This problem is not unique to s2Member; it is a problem with encrypted buttons on the PayPal side of things. We have made attempts to bypass the issue across multiple API versions without success.

Turning off security seems like a very very bad idea these days and I don’t want to really do that.

Some alternatives to this may include:

Use s2Member Pro Forms w/ PayPal Pro instead of Buttons.
http://www.s2member.com/kb/pro-forms/

Or, use a PayPal-generated button that is a “hosted button”; which you can select when you generate a PayPal Button at PayPal.com. These do not need to be encrypted. See also: http://www.s2member.com/kb/using-paypal-created-buttons/

Or, use an unencrypted button and just monitor incoming sales for any fraudulent activity (e.g. incorrect prices, etc). Unencrypted buttons expose their source code, so savvy users who wish to commit fraud may be allowed to do so; if your buttons are unencrypted. This is a risk, but it’s one that can be monitored for fraudulent activity and any fraudulent transactions can be identified; e.g. you should probably terminate their account access if you find that a transaction was indeed fraudulent.

@halasyt

Hi Jason, Cristián,

I would like to ask that when you become aware of such a huge problem that possibly affects everyone, please send out a letter to all of your customers notifying them of this.

I was wondering why I didn’t have any subscribers for the last few days, until someone wrote me telling me something is wrong, and yes, none of the buy buttons work on my site anymore. These few days of no sales could have been avoided if you would have kept us up-to-date on such a serious issue.

Tom

This did go out in an email notice to all s2Member users both free and Pro users also.
http://www.s2member.com/kb/paypal-button-encryption-problems/
You can subscribe to updates from your Dashboard, and this notice is also visible in everyone’s Dashboard.

I’m very sorry for the delayed response on this. I’ve been swamped and just got a chance to take another look at this. I would LOVE to have some assistance with this, if that’s still possible. Please submit the details privately to me via this contact form. Thank you!

See: https://www.s2member.com/contact/?s2-ssl=yes&d=support

Hi there. I sincerely apologize for the delayed response.

I just reviewed your forum thread and your WP installation, along with your ccBill log files. It appears from your log files that everything is running properly for you now. However, if you ARE still having some trouble, please reply back and give me a specific transaction ID and I will track down what actually took place in your log files.

For future reference, please review ccbill-ipn.log and paypal-ipn.log because the -rtn.log files only show what happens live on the site, and not what’s taking place behind-the-scene. Your existing log files indicate that s2Member® is handling post-processing for you.

@cat@momentumoptionstrading.com

@bmiddaugh

Thanks for reporting this important issue.

This appears to be a problem on the PayPal® side of things. There is another bug report here; and PayPal seems to be working on it as this point. I will contact PayPal MTS about this also, but I suggest that each of you do the same, because often times it will take more than a single person having trouble to get something done.

Please report this here: http://www.paypal.com/mts/

When I hear back from PayPal® on this, I will update this thread.
Until then, I suggest turning off the encrypted button feature in s2Member®.

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

Thanks for reporting this important issue.

php.ini is set to use a max of 512M:
phpinfo () returns :

<div class="s2-code-tools"><a href="#" class="s2-code-select-all" onclick="s2_selectAll(jQuery(this).parent().next()); return false;" title="Select All"></a><a href="#" class="s2-code-view-source" onclick="s2_viewSource(jQuery(this).parent().next()); return false;" title="View Source"></a></div><code>memory_limit	512M	</code>

here is a sample of wp-config.php:

<div class="s2-code-tools"><a href="#" class="s2-code-select-all" onclick="s2_selectAll(jQuery(this).parent().next()); return false;" title="Select All"></a><a href="#" class="s2-code-view-source" onclick="s2_viewSource(jQuery(this).parent().next()); return false;" title="View Source"></a></div><code>define('WP_MAX_MEMORY_LIMIT', '256M' /* WebSharks™ Core auto-fix. */);
define('WP_MEMORY_LIMIT', '256M');</code>

First, I should point out WHY s2Member needs this much RAM, in this specific case. It’s actually not s2Member which needs the RAM, it’s the core WordPress® unzip routine that s2Member uses. In order to unzip a file it requires quite a bit of RAM to hold the data while it’s processing.

Here is the line that comes straight from s2Member’s pro upgrade routine which checks for memory available.

if(@set_time_limit(0) !== "nill" && @ini_set("memory_limit", apply_filters("admin_memory_limit", WP_MAX_MEMORY_LIMIT)) !== "nill" && @ini_get("memory_limit") === apply_filters("admin_memory_limit", WP_MAX_MEMORY_LIMIT))

In short, having this configured the right way (e.g. to provide enough memory in your configuration); is only the first part of resolving this. The second part requires that you verify that your server is actually following your configuration. If you are setting WP_MAX_MEMORY_LIMIT correctly, but still getting this error, my guess is that your server is not really allowing this, even though you’ve configured it as such.

Here’s how to test it on your server.

Create a new PHP file, just name it ram-test.php and upload it to your root web directory (in the same directory where your wp-config.php file resides). Inside this file, make an attempt to set the memory limit to what you’ve configured WP_MAX_MEMORY_LIMIT with and see what happens.

Here is how I would test it if I were investigating your server.

<?php
require dirname(__FILE__).'/wp-load.php';

if(@set_time_limit(0) !== 'nill'
	&& @ini_set('memory_limit', apply_filters('admin_memory_limit', WP_MAX_MEMORY_LIMIT)) !== 'nill'
	&& @ini_get('memory_limit') === apply_filters('admin_memory_limit', WP_MAX_MEMORY_LIMIT))
		echo 'Memory looks good! Server reports: '.@ini_get('memory_limit').' which DOES match up with what s2Member expects: '.apply_filters('admin_memory_limit', WP_MAX_MEMORY_LIMIT);
else echo 'Memory has issues. Server reports: '.@ini_get('memory_limit').' which does NOT match up with what s2Member expects: '.apply_filters('admin_memory_limit', WP_MAX_MEMORY_LIMIT);
?>

Run this file and please report back and let us know what message you got. If we get some feedback on this test, we can certainly try to improve things further, if possible.

If you need help with this, please submit a Dashboard login privately.
See: s2Member® » Private Contact Form

@ Andrea Cilento

I’m not sure where 15 days comes from. You posted a private contact form just yesterday, and upon us making an attempt to inspect that site, we found once again that it was impossible to investigate. The site you submitted yesterday was completely offline :-)

The site you posted when this thread was originally started (which was 10 days ago, and not 15 days); was online, but had no log files or anything for us to inspect. We wrote you back within 24 hours, but then 4 days later you wrote back asking for more assistance. We only received a new submission from you yesterday, and as I said, the site was offline.

In this time we have helped another customer in this same thread even, who is using ccBill as well; and seems to be running just fine now after getting some assistance w/ configuration.

Regarding your request for a refund. Please see: s2Member® » Terms » Refund Policy

We have a no refund policy on non-tangible digital items which are irrevocable. We do make special exceptions, but as clearly defined in our refund policy, we ask that you follow all suggestions and advice presented by our support team, and work to resolve the problem with our assistance.

I will leave this thread open for you, but if your next submission is not a site that is online, or a private contact form submission with log files that we can inspect for you, I’m afraid there will be nothing more for us to go on in this case. We find that in cases where there is trouble, it is often related to configuration of the software, or configuration on the ccBill side of things. These are problems that can only be detected through a careful review of your configuration, and by inspecting the log files generated by the s2Member® software.

If you would like to investigate these yourself, please see:
Dashboard -› s2Member® -› Log Files (Debug) -› Logging Configuration

Thanks for the heads up on this thread :-)

@ Cory — thank you for reporting this important issue.

User search on child blogs of a Multisite Network appears to have been broken after the latest optimizations were applied in the release of s2Member® v130802. We are having this fixed for the next maintenance release, and I’m attaching a patch file to this thread that can be used until it’s made available.

Please download: http://d1v41qemfjie0l.cloudfront.net/s2member/uploads/2013/08/users-list.inc_.php_.zip

Unzip and extract the users-list.inc.php file. Upload this file to your site via FTP and allow it override the existing copy of /wp-content/plugins/s2member/includes/classes/users-list.inc.php. Please report back with a confirmation of this being corrected for me :-) Thanks!

Thanks for the heads up on this thread :-)

This first post may have been slightly misleading. The issue here has nothing to do with urlencode so please forget I mentioned that. S2Member reads all the data that clickbank passes just fine. Things like membership level, IP, etc. The only major issue I have is the cbfid and cbur can’t be passed in the same clickbank link.

Right. The urlencoding that ClickBank does on their end, is on purpose. While it may look wrong to the naked eye, that’s actually correct. It’s just a bit odd to see the URL-encoded values all combined into a single variable on the ClickBank side of things (e.g. they combine several vars into vvar= on their side).

I’m investigating the other issue now. One moment please.