Bruce

Hi Dean,

Your saying that Paypal should be able to see the error in my Payflow account’s history?

The issue seems to be brought up by the time your PayPal account was created, because PayPal has been updating it’s API, different users have different standards to follow, which can lead to issues when s2Member’s contacting PayPal and PayPal is set up to take different variables. PayPal should be able to fix the problem by upgrading the version of the API they’re using on your specific PayPal account.

I would suggest emailing them the error you’re getting, and the below link for information regarding the issue, if you cannot get it resolved using the tips Jason lined up within the post:

http://www.s2member.com/forums/topic/urgent-error-36-transaction-failed/#post-22378

Let me know how it goes :)

Hi Jorden,

To upgrade users within s2Member, you need to set up Billing Modification Forms from within your dashboard under s2MemberJ -> PayPal® Pro-Forms -> PayPal® Pro Billing Modification Forms. There you can set up forms to upgrade to different Membership Levels, and display different forms based on conditionals within your page. You can check out Dashboard -› s2Member® -› API / Scripting -› Simple/Shortcode Conditionals for information on how to set those up.

s2Member will then update the billing information for the user’s subscription to match the one they just upgraded to.

If I have a “gold” level member @ $200 and they want to upgrade to a Platinum membership which is $450, how does S2member handle this?

To do this, you would put something like this within your page:

[s2If current_user_is(s2member_level_3)]
	[s2Member-Pro-PayPal-Form modify="1" level="4" ccaps="" desc="$250 USD / One Time ( for lifetime access, non-recurring, no trial )" ps="paypal" lc="" cc="USD" dg="0" ns="1" custom="mysite.com" ta="0" tp="0" tt="D" ra="250" rp="1" rt="L" rr="BN" rrt="" rra="2" accept="paypal,visa,mastercard,amex,discover,maestro,solo" accept_via_paypal="paypal" coupon="" accept_coupons="0" default_country_code="" captcha="0" /]
[/s2If]

Let me know if you need anything else clarified :)

Hi Dean,

Sorry to hear you’re having trouble.

Are you using Recurring Billing with PayPal Payflow?

There has been a report similar to this one in the past, you can see what Jason said here.

If you could also send over your PayPal Logs from the transaction, x-ing out personal data (if you have logging enabled), that would be great. You should be able to find the logs from within /wp-content/plugins/s2member-logs/

Sorry you’re having these issues, PayPal has been updating it’s API and different users have different APIs based on the time they joined PayPal. As mentioned by Jason in the linked post, it may be in your best interest to contact PayPal and ask them about the error.

Thanks

Hi David,

s2Member does pass variables as an array in the URL of the page when it has to redirect users to the Membership Options Page. However, it does require some PHP within your Membership Options Page to make use of these variables.

You can find information on these variables within your Dashboard under s2Member->API / Scripting->Membership Options Page / Variables. Let me know if you need any help with setting something up. :)

Another Thought:

You may want to put a $_GET[] variable on the end of the URL the script I posted to be able to tell when a user is just directly accessing the Membership Options Page, and when they have been redirected through that script.

Thanks Andrew, glad to hear you’ve got it working. :)

Let us know if you need anything else.

Hi David,

Thanks for the information

I have uploaded the following code to your website within an s2hacks.php file in /wp-content/mu-plugins/

I tested this on your site and it seems to be working correctly. Let me know if you have any issues.

<?php
/**
* Hack authored by Bruce (Support Rep) on the s2Member Forums.
* If problems persist, add a topic reply to http://www.s2member.com/forums/topic/bp-redirect-not-working-for-create-blog/ or create a new topic
*/
add_action('wp_loaded', 's2hack_redirect_buddypress_404_create');
function s2hack_redirect_buddypress_404_create()
	{
		if($_SERVER&#91;"REQUEST_URI"&#93; === '/microsites/create/' && !bp_blog_signup_enabled())
			{
				header('Location: http://'.$_SERVER&#91;'SERVER_NAME'&#93;.'/options/');
				exit();
			}
	}
?>

If you have any further problems, please reply here. :)

Hi Jorge,

The only way to do this would be to set up a hook within a mu-plugin on site #2 so that you could send the user data to that site from site #1 and create_user() on that site. A developer familiar with WordPress could use the ‘user_register’ hook within WordPress to make this work.

If you’d like to keep an eye out on the s2Member Knowledge Base, we may post some information and sample code for this within a couple weeks.

Hi David

From my last post:

I’m going to look into this within the following day and see what might be happening here within s2Member’s code (I’m not familiar with this occurrence). If I cannot get you a resolution for this within the next 1-2 days I’ll contact Jason once again to get his opinion on it.

Investigation Complete.

From looking at the file /includes/classes/cache.inc.php, it appears that the variable $cache_needs_updating is set from within the file based on if() statements. This variable being undefined does not affect anything because it is only checking to see if the variable is TRUE.

I’m going to contact Jason about changing the code slightly within this file so that the above error does not show up within the debug, as it is not affecting anything.

Hi David,

Sorry for the delay

I took another look at the BuddyPress code for the /create/ page, and it appears that it is actually controlled by the BuddyPress theme you are running. In the default BuddyPress theme, when the user accesses the create blog page, they are given the message “Site registration is currently disabled”. I would take a look into the file within your theme called /blogs/create.php, and run a search for 404. If there is a trigger for the 404 page, you can post the code here, within a reply to this post and we’ll see if we can fix it.

How have other customers responded to this? Any leads appreciated.

A lot of people would conditionally hide links to the registration page using something like get_site_option('registration'); # if this == 'none' then they cannot make any more sites.. This can also be used for your site.

*I know I’ve mentioned this before, I’m getting this from debug:
NOTICE: wp-content/plugins/s2member/includes/classes/cache.inc.php:97 – Undefined variable: cache_needs_updating

I’m going to look into this within the following day and see what might be happening here within s2Member’s code (I’m not familiar with this occurrence). If I cannot get you a resolution for this within the next 1-2 days I’ll contact Jason once again to get his opinion on it.

Thanks for your patience.

Hi Andrew,

Looking at your page here, it appears that the BuddyPress login form is separated into two parts within the HTML. You simply need to display: none; to those IDs within the CSS file.

Like this:

p#login-text {
display: none;
}
#sidebar-login-form {
display: none;
}

Hi Andrew,

If you can’t take it off from the WordPress Dashboard, then it’s (most likely) a part of your theme.

You can probably edit it out through the sidebar.php file in your theme. Or, if you want to send me a link to your website, I can show you how to hide it with CSS.

You should be able to do this with get_users().

$users = get_users();
foreach ($users as $user) {
     echo '<li>' . $user->display_name . '</li>';
} 

You could also use $user->ID within the foreach() to get_user_meta().