Jason (Lead Developer)

Thanks for your inquiry. ~ We appreciate your patience :-)

I believe what you’re looking for is the s2Member® Pro Login Widget. The s2Member® Pro Login Widget (which comes with s2Member Pro) has a setting that handles this automatically for you. You make the login widget available, and s2Member handles the rest (ultimately defined by the redirect_to variable).

Please let us know if you have any other questions/concerns :-)

Thanks for reporting this important issue.

Warning: Illegal string offset ‘level’ in C:\xampp\htdocs\ancestryireland\wp-content\plugins\s2member-pro\includes\classes\exports-in.inc.php on line 110

What version of s2Member® Pro are you running please?
Or, if you’d like to send us a Dashboard login and FTP access, we’ll run diagnostics for you.
See: s2Member® » Private Contact Form

[ERROR] PHP Echo Tag:
PHP v5.4.7 supports the echo tag () at all times. So you’re good here.

Please disregard this. It’s actually a false-positive that needs to be corrected I see. On PHP 5.4.7, you should see this as a PASS, and not as an ERROR. We’ll have this corrected asap.

Thanks for your inquiry. ~ We appreciate your patience :-)

A member logs in, ends up on their My Account Page (AKA Login Welcome Page). However if they try to click an otherwise restricted link they get redirected back to the ‘Membership Options Page” page.

Once you are redirected, please look at the URL, and copy/paste all of the query string variables that you see in the URL, here in the forum for review. Those are called MOP Vars, and they will tell the story about why the redirection occurred. You can learn about these here.

See: Dashboard -› s2Member® -› API / Scripting -› Membership Options Page Variables (MOP Vars)

It appears that because the Auto-EOT System was not enabled from the start on your installation (i.e. you just recently enabled it, it would appear), that you now have a backlog of EOTs that need to occur.

s2Member will certainly process these, but each time the CRON job is fired (it should be run every 15 minutes), s2Member will process at most, 3 EOTs at a time.

So if you setup the CRON job and let it run periodically, these accounts that you mentioned will be demoted by s2Member eventually; as s2Member goes through the backlog of EOTs that need to occur.

I just ran it again manually, and it picked up User ID 841 and demoted them. User ID #4 is still awaiting EOT.

It is also possible to extend the per-process setting, by filtering this default value of 3.

Please create this directory and file:
/wp-content/mu-plugins/s2-hacks.php
(NOTE: these are MUST USE plugins, see: http://codex.wordpress.org/Must_Use_Plugins)
(See also: http://www.s2member.com/kb/hacking-s2member/)

@Joe Raciti

Please see this article about SMTP server configuration for GMail.
http://email.about.com/od/accessinggmail/f/Gmail_SMTP_Settings.htm

Yes, that will be fine too.

Thanks for the follow-up :-)

I’m adding this to our list. Thank you.

Thanks for the follow-up :-)

Great! It’s been forwarded to some friends of mine for review. If they are interested, they will response to your project request. NOTE: I would also post this at Elance.com, if possible; many developers that I know prefer to work from there :-)

Details received. Thank you!

The Dashboard login that we have is working properly, but the FTP access is not working on our end. Please check those credentials for us, and submit a functional FTP login via this private contact form: s2Member® » Private Contact Form, or let us know if there something more we need to gain access. Thanks!

Jason- Thanks… Sending info over via the contact form. We’ve signed up for everything with the name “PayFlow” on it, and now have an arsenal of logins and passwords and vendor IDs, etc., but nothing seems to be working, as now I keep getting “Error #1. User authentication failed.”

This could indicate that you have the wrong type of PayPal account, or that the details entered in this section of your Dashboard do not match what the PayPal API is expecting from calls originating from your server.

See also: Dashboard -› s2Member® -› PayPal® Options -› Payflow Account Details

Once we have FTP access, we can also review your s2Member log files.

Thanks for your inquiry. ~ We appreciate your patience :-)

The problem is, if someone over time adds all the courses to their account, that is going to be a lot of subscriptions being processed, when it would be easier to have it update into one manageable monthly payment.

Exactly. s2Member® supports only one active subscription at a time. In other words, each customer can be associated with one Paid Subscr. ID in the Dashboard. Adding additional one-time purchases on top of that is no sweat for s2Member®, but adding additional monthly recurring fees (where you have more than one Recurring Billing Profile associated with each customer), is not something that s2Member® supports at this time.

So for instance, let’s say a customer registers initially for Membership Level #1 at $19/month.
Now they want access to course A and course B, and that costs an additional $5/month (for each course).

So you introduce a Billing Modification Form that simply adds the extra Custom Capabilities to their Membership with you, and you charge the adjusted rate of $29/month for this entire package. s2Member® Pro Billing Modification Forms will terminate the existing Recurring Billing Profile, and it will create a new one to takes it’s place (i.e. a new Recurring Billing Profile that matches the new package they have).

Of course, it’s not always just that simple, because often times, there are conditions and dynamics involved with calculating prices during checkout. Some site owners deal with this by implementing their s2Member Pro Forms with PHP code (i.e. in a custom WordPress template file).

For instance, something like this; where you calculate prices/terms dynamically in custom ways — in your own code; and then pass that information along to your s2Member® Pro Form Shortcode.

See also: Dashboard -› s2Member® -› PayPal® Pro Forms -› Billing Modification Forms

<?php
$base_monthly_rate = 19.00;
$amount_per_course = 5.00;
$new_course_ccaps = array('course_a', 'course_b');

$user = wp_get_current_user();
$existing_level = c_ws_plugin__s2member_user_access::user_access_level($user);
$existing_ccaps = c_ws_plugin__s2member_user_access::user_access_ccaps($user);
$caps_in_new_package = array_merge($existing_ccaps, $new_course_ccaps);

$level = $existing_level;
$ccaps = implode(',', $caps_in_new_package);
$ra = $base_monthly_rate + ($amount_per_course * count($caps_in_new_package));

echo do_shortcode('&#91;s2Member-PayPal-Pro-Form ... level="'.$level.'" ra="'.$ra.'" ccaps="'.$ccaps.'" ... /&#93;');
?>

In this example, the only problem is this…

The customer is going to pay you $29 now (during they’re upgrade), because those are the terms of the new Custom Capability package they are purchasing. However, in many cases the customer will have already paid you $19 for the current month they are in, so the very first charge in this new Recurring Profile, should be less that amount. This is accomplished with the ta="" tp="" tt="" Shortcode Attributes.

See: Dashboard -› s2Member® -› PayPal® Pro Forms -› Shortcode Attributes (Explained)

This considers what I just mentioned, and uses ta="" tp="" tt="".

<?php
$base_monthly_rate = 19.00;
$amount_per_course = 5.00;
$new_course_ccaps = array('course_a', 'course_b');

$user = wp_get_current_user();
$existing_level = c_ws_plugin__s2member_user_access::user_access_level($user);
$existing_ccaps = c_ws_plugin__s2member_user_access::user_access_ccaps($user);
$caps_in_new_package = array_merge($existing_ccaps, $new_course_ccaps);

$level = $existing_level;
$ccaps = implode(',', $caps_in_new_package);
$ra = $base_monthly_rate + ($amount_per_course * count($caps_in_new_package));

$ta = $ra - $base_monthly_rate; // Discounted price for the first month in this new plan.
$tp = 1; $tt = 'M'; // 1 month at this discounted rate.

echo do_shortcode('&#91;s2Member-PayPal-Pro-Form ... level="'.$level.'" ra="'.$ra.'" ccaps="'.$ccaps.'" ta="'.$ta.'" tp="'.$tp.'" tt="'.$tt.'"... /&#93;');
?>

Thanks for reporting this important issue.

Can you please post the PayPal Button Shortcode that you integrated with s2Member? In other words, for these Members who are expiring on the WP side of things, what exactly did they purchase from you? We’ll need to see how your Shortcode was configured please.

Also, it would be a good idea to enable s2Member’s logging routines, so you can see if PayPal is sending s2Member® IPNs behind-the-scene, which are resulting in these expirations (i.e. failed payments, cancellations, etc). What do your log files tell you? Feel free to post those privately for us to review with you.

See: Dashboard -› s2Member® -› PayPal® Options -› Account Details -› Logging
See: s2Member® » Private Contact Form

Thanks for your patience.

I setup a test account on your installation with Username EOT_Test, at Membership Level #1, and with an EOT Time that was in the past. I then ran the URL provided by s2Member to the Auto-EOT CRON job.
/?s2member_auto_eot_system_via_cron=1

Inspecting the User’s account afterward at this URL:
/wp-admin/user-edit.php?user_id=2711

Indicates the Member was succesfully demoted down to a Free Subscriber, and s2Member notes that.
Demoted by s2Member: Fri Jan 25, 2013 8:22 am UTC

To add some more details that might be helpful while investigating this issue, manually entering the following into a web browser didn’t cause demotions for people with expired EOTs either:

http://mywebsite/?s2member_auto_eot_system_via_cron=1

Indeed, it isn’t clear that it did anything. The web browser ended up displaying an otherwise blank page.

Please let us know if problems persist :-)