Bruce

Thank you very much for your purchase! :-)

How do I transfer the wordpress non multisite installation (http://comcentre.moretonbay.biz/) to the wordpress multisite installation (http://macleay.moretonbay.biz/)?
Do I have to delete the single installation and rebuild it?

This article from from WordPress.org may help you with this. You will need to delete the site that you have currently, but WordPress does have functionality to help you transition your current site to your WordPress Multisite installation.

http://codex.wordpress.org/Migrating_Multiple_Blogs_into_WordPress_3.0_Multisite

How do I upgrade s2member to Multisite Network License when I do the transfer?

With s2Member’s Blog Farm License + Unlimited Site License, you have access to documentation regarding setting up s2Member with your Multisite Installation in your My Account Page. Please follow the instructions in the Multisite Blog Farm Documentation file you now have available.

See: http://www.s2member.com/account/

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

Thank you for the information.

This seemed to have started after S2Member pro install but not sure. How do I reset all s2member settings to default?

To reset s2Member to default, turn OFF Deactivation Safeguards, then deactivate and then activate the s2Member plugin through your Dashboard.

See: Dashboard -› s2Member® -› General Options -› Deactivation Safeguards

Thank-you for your inquiry.

When we ban a user from our community – we change them to Banned level, set their account status to 3 in WP, and remove their Authnet payment ID from their fields – and move that to the info field for reference.

s2Member’s integrations with Authorize.Net, and all of s2Member’s supported payment gateways, are one-way integrations, meaning that changes that are made from the Payment Gateway are reported to s2Member, and s2Member uses this information. However, changes made manually to users on your site are not reflected to your Payment Gateway.

This means that if a user is paying for a subscription to your site and you remove their Paid Subscription ID from their profile, the user will still be billed unless you cancel the subscription through PayPal (or whatever PayPal Gateway you’re using).

Recently the problem we are having: Authnet continues to charge monthly fees even AFTER the banned user’s info has been removed from the appropriate fields. HOW do we stop Authnet from pulling those recurring payments for our banned users???

To stop an Authorize.net subscription from recurring, you will need to stop the subscription manually after deactivating the user’s account using the details here:

http://support.authorize.net/authkb/index?page=content&id=A656&actp=LIST

(For about a year we had been using Paypal – and never had this problem._

I am unsure how this could be the case. s2Member does not integrate this way with any of it’s supported payment gateways. Removing the user’s Paid Subscription ID will never stop recurring billing. Perhaps you simply never banned a user that signed up through recurring billing? You mentioned that you had multiple plans available on your site. Buy Now transactions would not require a cancellation of a Recurring Billing Profile, because a Recurring Billing Profile is not created for Buy Now transactions.

Please let us know if problems persist. :-)

The “You do not have sufficient permissions to access this page.” is a message thrown by WordPress whenever one of the following things happens:

1) You are attempting to access an admin page that does not exist, or is not created for your level

OR if

2) Your current user level does not have the capability manage_options

To find the issue here, please make sure that the following is all set up correctly:

Make sure that the user that you’re attempting to log in on is an admin on the specific site that you’re attempting to log in on. For instance, if you’re logging in at http://example.com/wp-login.php, your user should be an admin on your main site.

When you’re logging in, you’re being redirected to http://yourdomain.com/wp-admin/, and NOT http://yourdomain.com/wp-admin/network/. You should be getting this error as a regular admin user if you are trying to access your Network Administration panel.

If you still cannot access your WordPress Dashboard with a regular admin account after you test the above, you may have an issue with the capabilities associated with your Administrator role on your specific installation. If that’s the case, I would recommend installing a plugin such as Capability Manager, and ensure that your Admin role has the correct capabilities.

See: http://codex.wordpress.org/Roles_and_Capabilities

Please let us know if problems persist. :-)

Thank-you for reporting this important issue.

I’m sorry to hear that you’ve had a problem with upgrading. It sounds like your Deactivation Safeguards were turned off. Could you please check what you have set up under Dashboard -› s2Member® -› General Options -› Deactivation Safeguards?

If s2Member’s Deactivation Safeguards are disabled, any time s2Member is disabled on your WordPress site, s2Member will delete all settings that were set up. This is to help keep your database and user roles table clean if for any reason you decide to stop using s2Member.

One thing to note is that we are using the same paypal account for our testings so is it possible that this is happenng because of repeated purchases from the same paypal accoun

This, in conjunction with one other thing is what is causing this issue. To fix your issue, please set up another PayPal account for testing.

PayPal will not allow payment to go through from a PayPal account, to the same PayPal account. So because the payment is failing for this reason, s2Member demotes the user right after they are granted access. However, s2Member is only upgrading the member to level 1 for that limited amount of time because of your shortcode’s rra attribute value.

[s2Member-Pro-PayPal-For... rra="2" ...  /]

The rra value controls how many times PayPal is allowed to retry billing the user. By default this is set to 2, which should be fine. However, when this is set up, you will then be giving access to a specific level / set of capabilities to your member (depending on your Shortcode’s values) for as long as it takes PayPal to try to process the payment as many times as you specify here.

This is why you see “Demoted by s2Member: Thu Jan 31, 2013 2:03 am UTC” in your Administrative notes.

See: Dashboard -› s2Member® -› Download Options -› Shortcode Attributes & API Functions

Hello friends… I have followed all the instructions to configure the plugin, everything seems to work well for charging paypal subscription and returns perfectly to the site, but I could not get me back Auto EOT Time ($s2member_auto_eot_time) always returns empty.

This is the expected behavior. With PayPal, s2Member does not store and EOT date for live subscriptions. End of Term (EOT) dates are only set when the subscription is cancelled. This is because before this point, the subscription is not set to end at any point, and therefore there is no EOT date to set.

However, if you were using Buy Now transactions for membership, an EOT date would be set after each transaction. However, you should note that this type of transaction is non-recurring, so users would need to manually renew their accounts to continue having access to your protected content.

We have used WordPress SEO by Yoast for all of our public web pages. However, we are unsure if the private member content pages should have SEO. Should they be blocked from all search engines because they are password protected areas?

For protected areas of your site, s2Member will block access to your posts/pages from search engines such as Google, just as a regular logged-out member would be. These crawlers are instead redirected to your Membership Options Page. So SEO for these pages is not required or used.

Based on Philly’s post, the correct way to set this up would be to replace this line:

wp_nav_menu( array( 'depth' => 6, 'sort_column' => 'menu_order', 'container' => 'ul', 'menu_id' => 'main-nav', 'menu_class' => 'nav fl', 'theme_location' => 'primary-menu' ) );

With:

if ( is_user_logged_in() ) {
    wp_nav_menu( array( 'depth' => 6, 'sort_column' => 'menu_order', 'container' => 'ul', 'menu_id' => 'main-nav', 'menu_class' => 'nav fl', 'theme_location' => 'logged-in-menu' ) );
} else {
    wp_nav_menu( array( 'depth' => 6, 'sort_column' => 'menu_order', 'container' => 'ul', 'menu_id' => 'main-nav', 'menu_class' => 'nav fl', 'theme_location' => 'logged-out-menu ) );
}

Note that the above has not been tested, and maybe require tweaking to get it to work correctly.

That’s about as far as we can go with custom code, as per our Support Policy. If you need any further help, we recommend posting a job listing on http://jobs.wordpress.net/, or http://elance.com/.

Looking for some advice about the best way to exclude a specific URL from S2 protection. Here is the scenario: We’ve installed a chat program which interfaces with WP but is installed outside of the WP installs on the server. This works perfectly. People who visit our site, who are not logged in, cannot access the chat program. S2 is functioning perfectly. However, it is locking out admins from the admin log in. The URL which is set up to administrate the new chat software is:

When you say that your chat program “interfaces with WP”, what do you mean exactly? Is this something that is being pulled into a WordPress Post/Page? Are you only loading WordPress’s functionality here through PHP?

Hm…actually, I just tried to add /admin/ to our highest level of membership and when I enter the correct URL (logged into S2 as an admin) it says “page not found” and if I am logged out and try to enter the URL S2 redirects me to the login/registration page.

This is likely an issue with an invalid setup here. You should set up your URI restriction with /chatprogram/admin/. If you use /admin/, s2Member will block access to any URI on your server that contains /admin/ in the URL, which is not what you need here.

See: Dashboard -› s2Member® -› Restriction Options -› URI Access Restrictions

this is my current code that doesn’t work, i’m not sure it gets triggered at all. getting the signup email hook working gave me the impression that it is sitting at the right place in my s2-hacks.php file.

That code looks correct to me. I would suggest instead using update_option() to store the information.

See: WordPress -> update_option()

Unfortunately, as stated in our Support Policy, we cannot debug custom code. If you’re having issues, we recommend posting a job listing in a site such as http://elance.com/ or http://jobs.wordpress.net/.

i’d like to be able to put a condition for one of my Custom Registration/Profile Fields.
it’s a select dropdown.

This is not something s2Member currently supports natively. If this feature is something that you need, I’d recommend using custom JavaScript code to do this. s2Member assigns IDs to each of your Custom Profile/Registration Fields when it generates them so that something like this is possible. You can find the IDs for your Custom Profile/Registration Fields by examining the source code of the page in which your signup form is on with something like Firebug for Firefox.