Jason (Lead Developer)

By default, s2Member menu items will ONLY display if the current administrative user has the create_users Capability. So you might take a look to be sure the Role you’re dealing with, does NOT have this Capability. If it does, please remove that Capability from the custom Role that you’re setting up.

Otherwise, if more control is needed, you can always filter the s2Member menu out with a custom hack. s2Member exposes a Filter to make this possible.

Create the directory and file:
/wp-content/mu-plugins/s2-hacks.php
( these are MUST USE plugins, see: http://codex.wordpress.org/Must_Use_Plugins )

<?php
add_filter("ws_plugin__s2member_during_add_admin_options_create_menu_items", "__return_false");
?>

Of course, you might want to apply some conditional logic before adding the filter, but this may help.

Thanks for the heads up on this request for support.

The issue is with the BuddyPress layer.

Sorry, if the issue is with BuddyPress, you will need to seek assistance from BuddyPress. I attempted to view the link you posted earlier (http://bit.ly/JPVaeB/), but it appears to be broken now? If you have some further details that you’d like us to review, please feel free to follow-up.

Otherwise, you might try the BuddyPress forums, if the problem is specifically with BuddyPress.
http://buddypress.org/support/

$xml .= '<billTo>';
$xml .= '<firstName>'.esc_html(substr($post_vars["x_first_name"], 0, 50)).'</firstName>';
$xml .= '<lastName>'.esc_html(substr($post_vars["x_last_name"], 0, 50)).'</lastName>';
$xml .= '<address>'.esc_html(substr($post_vars["x_address"], 0, 60)).'</address>';
$xml .= '<city>'.esc_html(substr($post_vars["x_city"], 0, 40)).'</city>';
$xml .= '<state>'.esc_html(substr($post_vars["x_state"], 0, 2)).'</state>';
$xml .= '<zip>'.esc_html(substr($post_vars["x_zip"], 0, 20)).'</zip>';
$xml .= '<country>'.esc_html(substr($post_vars["x_country"], 0, 60)).'</country>';
$xml .= '</billTo>';

Thanks for the follow-up.

“It appears that PayPal IPN transactions are timing out from WordPress due to the one of the port being not open. Please provide us with the server requirements to further look into it. We have open only standard ports.”

I still think there is a server configuration issue here. s2Member is only attempting to access a publicly available URL over port 80 (i.e. the standard HTTP port). Like I said before, I believe there is a mis-configuration at the hosting level, causing the firewall to deny requests made by the server itself. If port 80 is being blocked, it should NOT be. Particularly if it’s the server itself making this request.

Thanks for the heads up on this request for support.

B. The user downloads 5 files in 7 days, and when the next 7 day period starts, he downloads 5 different files but no longer has access to re-download the first 5. The 5 files are based on concurrent use. If I had 50 files, it would take him 10 weeks to download them all but he would not be able to re-download them.

Following the example that you laid out…

s2Member allows X number of files to be downloaded, every X number of days, as configured by the site owner. A customer may download up to 7 different files in each 7 day period. The date calculation begins when the first downloaded occurs, and automatically resets back to 0 after 7 days has passed.

For example…

If a customer downloads 5 files today, they are not allowed to download any new files until 7 days later, when the next period begins for this customer. When the next period begins, 5 new files can be downloaded.

There is no distinction in these calculations regarding files downloaded in previous periods. A customer will NOT always have access to files they’ve downloaded in the previous periods. Once a new period begins, all previous downloads are wiped away. In other words, a customer could not download 5 new files, and then go back and download 25 files again, which they might have downloaded in the past.

@Alissa Glenn

This might be completely unrelated… however, I noticed when logging into your site via FTP, that I HAD to use http://ftp.fatcow.com, instead of your primary domain name. Your primary domain kept timing out on me. I suspect this is somehow related to the issue on the site itself. Anyway, just thought I would mention that.

@Alissa Glenn

Investigation completed.

I found that your server is misconfigured in some way. HTTP requests from the server to itself are timing out, which is indicative of a server configuration issue, perhaps with DNS resolvers.

I’ve created a test file for you here.
http://www.noplanmealplan.com/?http_test=1

This should print success on the screen, but it is continuously timing out with the following error.

WP_Error::__set_state(array(
   'errors' => 
  array (
    'http_request_failed' => 
    array (
      0 => 'connect() timed out!',
    ),
  ),

I have this test logging it’s results into this file, for you and your hosting company to review:
/wp-content/mu-plugins/http-debug.log

The file responsible for handling these tests, was uploaded here:
/wp-content/mu-plugins/http-debug.php

Please delete that http-debug.php file once your hosting company has assisted with this issue.
I would suggest showing these errors to them, and asking for assistance.

It seems that your current server configuration is preventing WordPress from communicating with itself. HTTP POSTs are failing when the server itself is attempting to POST data to it’s IPN handler. This is required for s2Member’s Authorize.Net integration, which POSTs data from a Pro Form, to it’s own IPN handler. From your log files, it seems that your server stopped functioning properly around Sept 2011. That’s when the logs went blank, and nothing more was recorded. I suspect because all HTTP communications began to time out on the server.

Thanks for the heads up on this request for support.

s2Member Pro will allow 14 months, but only if you have rr="BN", meaning it’s a Buy Now button.

Otherwise, s2Member Pro is subjected to the limits set forth by PayPal’s Recurring Billing system, which states that recurring billing periods CANNOT exceed 1 year. I know this differs slightly from PayPal Standard Buttons, and I have no idea why, but that’s the way it’s written none the less. Thus, s2Member Pro Forms are not capable of charging customers in intervals that exceed 1 year, 12 months, or 365 days.

https://www.x.com/developers/paypal/documentation-tools/api/createrecurringpaymentsprofile-api-operation-nvp

Yes, that is correct. s2Member does not store billing information locally, for security purposes. Any updates to billing info must be accompanied by a new submission from the customer, including a new full billing address to match the new payment method they will be using going forward.

Billing Update Forms from s2Member Pro are designed to handle this, by connecting to the payment gateway, and updating the details on file with your gateway, for a specific customer.

Thanks for the heads up on this thread.

I just took a quick look at your import file, which looks fine. You have 100 lines in this import, with 5 lines containing duplicate email addresses. I imported this file into an installation of WordPress v3.3.2, running with BuddyPress as the only other plugin, running with the default BuddyPress theme.

The following errors were encountered during importation:

Line #17. Conflicting. The Email address ( xxxx@xxxxaswsor.com ), already exists.
Line #18. Conflicting. The Email address ( xxxxxx@xxxxu.edu ), already exists.
Line #19. Conflicting. The Email address ( xxxxxx@xxxxxoursuccess.com ), already exists.
Line #20. Conflicting. The Email address ( xxxxxx@xxxxxpanies.com ), already exists.
Line #21. Conflicting. The Email address ( xxxxx@xxxem.edu ), already exists.

Thanks for the heads up on this thread.

I’m sorry if there has been any confusion about this. There’s currently NO feature in s2Member that would absolutely stop a User/Member from updating their own Profile (i.e. Username/Password/Email Address). However, you do have control over which Custom Registration/Profile Fields can be edited, and which CANNOT be.

If you create your own Custom Registration/Profile Fields, these can be configured to disallow Profile edits, under: Dashboard -› s2Member® -› General Options -› Registration/Profile Fields. Open each field’s configuration window for details regarding this configuration option.

Under s2member > General Options > Member Profile Modifications I have the “Redirect Members away from the Default Profile Panel? ” setting set as “Yes”.

The feature that you’re referring to, is designed to prevent the /wp-admin/profile/ panel from being used, in cases where you’d rather Users/Members stay on the front-end of your site instead (i.e. NOT allowing /wp-admin/profile/ access, to the WordPress default profile editing panel). However, this is NOT to say that s2Member is going to disallow any sort of profile update whatsoever. It’s only preventing profile updates from occurring through the /wp-admin/profile/ panel.

If you’d like to take this a step further, and lock down s2Member’s stand-alone Profile editing panel as well, you could add this action hook to your site, which accomplishes just that.

Please create this directory and file:
/wp-content/mu-plugins/s2-hacks.php
( these are MUST USE plugins, see: http://codex.wordpress.org/Must_Use_Plugins )

<?php
add_action('init', 'prevent_s2_profile_updates', 1);
function prevent_s2_profile_updates()
	{
		unset($_GET&#91;'s2member_profile'&#93;, $_POST&#91;'ws_plugin__s2member_profile_save'&#93;);
	}
?>

Thanks for the heads up on this thread.

The s2Member Framework (i.e. the free version of s2Member), is 100% GPL, as-is WordPress itself. Therefore, as long as you follow all of rules of GPL, you can bundle a copy of the s2Member Framework into another GPL-compatible software application. Just remember, your entire application must also be licensed as GPL if it includes s2Member.