Mary Grisolia

Thanks Raam, the problem I see is that I want to automatically upgrade a subscriber without changing their billing plan. They will be upgraded only because they’ve been active for X months.

As I’m gonna need to handle unsubscriptions/cancellations manually (as per my previous post), then the automatic EOT behavior is set to NO.

What I want is that when a subscriber has been active for a given period, he’ll be promoted to a superior level. I’m offering a course so this will be the level of “graduated students”, who will have different capacilities than other active students. There’s no billing because they will have lifetime access to the content.

Can I do this automatically or do I have to upgrade all students manually?

Philly, you got it!

I didn’t have to network activate the plugin but only to activate it on the main blog. The options became immediatly available on the network dashboard (I even got an alert as soon as I activated the plugin on the main blog).

It’s all set now and the registration link is working (yey!).

I don’t mind having the plugin activated on the main blog (even if I won’t use it there), so I’ll just leave it like that.

About you’re question, this message appears right below the s2M network options panel:

These files MUST be patched, each time you upgrade the WordPress® core. If you set this option to Yes ( Patch Automatically ), s2Member will patch your installation now, and also in the future, should you upgrade to newer version. That way, you won’t need to patch manually each time WordPress® is upgraded.

Thanks again!!

P.S.: Cristián, thanks for having taken a look at this too. I posted another question in the forum a few days ago, hope that you get the time to see that one (still unsolved). It’s about payment/membership options.

For the address I get a “you don’t have enough rights to access this page” (or something like that, mine is in Spanish). This happens wether I use the main network blog domain name or the child blog one, and I got that message after logging in (it redirects me to the login page if I’m logged out).

I’m of course the network and site administrator. Actually, I’m the only user on this network. I have never installed any capability manager plugin – just in case you were wondering.

As for the lostpassword, I actually tried it (as is, with the network_ part it had, not having changed anything) for my child blog and it works fine (I don’t get redirected to the main network blog). I hadn’t ever touched this file before, do I really need to remove that bit? because, as I’m telling you, it works fine (contrary to the register function, which does redirect me to the main network site).

P.S.: Yes, MU is actually not easy to work with, but I cannot stand the idea of having to have multiple wordpress installations :(

Hey Cristián, thanks for your reply!

I checked my general-template.php file and the lostpassword function was ok (it contained network_site_url) as in the other topic. I tested it and it works (it doesn’t redirect me to the main network site).

The register function contained only site_url. I added the network bit to it (turned into network_site_url) but it’s still not working (it keeps redirecting me to the main network site register page). I compared both functions to see if I could make them match someplace else, but they’re quite different.

Here’s how my register function looks like:

function wp_register( $before = '<li>', $after = '</li>', $echo = true ) {

	if ( ! is_user_logged_in() ) {
		if ( get_option('users_can_register') )
			$link = $before . '<a href="' . network_site_url('wp-login.php?action=register', 'login') . '">' . __('Register') . '</a>' . $after;
		else
			$link = '';
	} else {
		$link = $before . '<a href="' . admin_url() . '">' . __('Site Admin') . '</a>' . $after;
	}

	if ( $echo )
		echo apply_filters('register', $link);
	else
		return apply_filters('register', $link);
}

And this is my child blog registration link:

http://www.tunuevocuerpo.com/wp-login.php?action=register

I also did a search on the WP forums but the few posts I could find were not exactly about the same thing. Only this one reported the same issue:

http://wordpress.org/support/topic/loginactionregister-says-registration-has-been-disabled

And this user actually posted on the old s2Members forum:

http://www.primothemes.com/forums/viewtopic.php?f=4&t=15431

In his case it was apparently a plugin-compatibility problem, but I didn’t quite get to understand if/how he solved his issue, so I’m gonna need an extra help with this :(

• This reply was modified 4 years, 4 months ago by  Mary Grisolia.

Hay Jason,

I couldn’t understand all you said because I haven’t used gravity or formidable forms, but I’m still wondering… for what I need, doesn’t my custom plugin just talk to WordPress and ask it who is logged-in? Because if that is the case then I don’t see the need for communication with S2Member (in my case). S2Member will determine if the custom page is accessible for that particular user, and if it is, it will give them access, and then my plugin will load the data in its custom database corresponding to the particular user (after having asked WordPress who is logged in).

Am I confusing things around?