Community Support Forums

I have a slight issue of when a member tries to logout from there automatic blog that they receive after signing up , they cannot logout..... they can only log out from the main blog site..

http://screenr.com/22Xs

Are you using the network's admin account in that test? Have you tried a normal user's account for that?

I am using a normal member...... when it makes me double loggin regarding the other issue, then it allows me to log out from the site created by member

but uses the default wp login without my custom logo and default wp logged out screen without my custom logo

thanks..

no double login with IE this time in this vid... but made me in Firefox... just a second ago...

http://screenr.com/kxXs

This only seems to be for existing user... with new users..., i can logout from the newly created blog but it also defaults to the wordpress loggout screen instead of the custom screen... I also have settings in s2 to force user to custom edit profile screen but it dafaults to wp edit profile screen when on the blog the user created dashboard but it does default to the login welcome screen when in the main blog membership dash ? is this designed this way?

http://screenr.com/YxXs

Hi Scott. Please see my reply here regarding COOKIEPATH.
viewtopic.php?f=4&t=15385#p45159
Let me know if you are still having trouble with this please.

I also have settings in s2 to force user to custom edit profile screen but it dafaults to wp edit profile screen when on the blog the user created dashboard but it does default to the login welcome screen when in the main blog membership dash ? is this designed this way?

Yes, this behavior is by design. Each instance of WordPress is it's own. That is, each Child Blog in your Network is associated with it's own instance of other plugins, and that includes a separate instance of s2Member as well. So the reason you're NOT seeing the same behavior one from Child Blog to another ( or from the Main Site to a Child Blog ), is that s2Member needs to be activated and configured for each Blog in the Network separately. While it is possible to activate s2Member ( or any plugin for that matter ), "Network Wide", each instance of s2Member needs to be configured, on a per-Blog basis.