[@trent Participant 17 years, 6 months ago]

There is a plugin offered at wpmudev.org for this. Not sure if it is under wpmudev.org or premium.wpmu.org though. Works great. Just taps into the wp-signup.php and adds a box that has terms (that you put in the admin area) and a checkbox.

Trent

[@trent Participant 17 years, 6 months ago]

I know Prologue works fine on a vanilla install of WPMU 2.6.5 and with 2.7 beta. I haven’t bothered to try it with a buddypress install since the problems before, but if you don’t have site-wide tags plugin, it would make sense it is something it doesn’t like with buddypress. I would just disable them one at a time to find out which one screws it up. The only other thing that is constant might be the admin bar on it, but I can’t see that. Do you have the domain mapping plugin? That might be it as well….just fishing I guess

[@trent Participant 17 years, 6 months ago]

I had issues with this for multiple reasons. One was a WPMU issue, one was a sitewide tags from Donncha issue and one was a Buddypress issue. The WPMU issue was solved at one point around 2.6.3 release. The buddypress issue was tied to the plugin issue for sitewide tags and it was supposed to make it work, but I haven’t tried it. I know this is a nothing answer, but if it keeps asking you to login all the time, I would find out if disabling bp-blogs.php and/or sitewide tags fixes it to narrow down the issue.

Trent

[@trent Participant 17 years, 6 months ago]

Andy mentioned that it will come after the initial major release of Buddypress, but you can keep up by following the timeline.

https://trac.buddypress.org/wiki/roadmap

Trent

[@trent Participant 17 years, 6 months ago]

If you have permalinks up and running already, it shouldn’t be an issue with the .htaccess as buddypress uses existing permalinks. Do you have a cache plugin installed? Anything in your error logs? Have an example?

[@trent Participant 17 years, 6 months ago]

In terms of privacy of seeing profiles, this is coming in a later version by default, but for now, you can do what I proposed at the following:

https://buddypress.org/forums/topic.php?id=160

It just makes the entire buddypress-member theme from being no viewable by anyone but logged in members. The buddypress-home theme still is available for signups though.

Trent

[@trent Participant 17 years, 6 months ago]

I just deleted the subdomains that were created with the old system. Then I just put the following in my wp-config.php for WPMU:

define( 'NOBLOGREDIRECT', 'http://mydomain.com' );

That of course needs to be changed to your domain. What that does is take any random requests (in this case old reference requests) and sends them back to my main domain page. This also makes it so you don’t get the fancy signup page for random domains you are trying to register through the address and have to do it through your wp-signup.php page.

Since most registration works better for me through the main buddypress theme signup page, this change didn’t bother me at all. Plus it stopped all the requests giving errors or “signup pages” that came from the old URL’s.

Something to think about…

Trent

[@trent Participant 17 years, 7 months ago]

I have used Media Temple for WPMU sites in the past and the Grid is better than most shared hosts, but really WPMU itself can grow past resources quickly. That is why VPS or dedicated is recommended, though many still say they are fine on a shared host if their bandwidth and userbase is low. Other great VPS providers include Slicehost.com and Futurehosting.biz

Getting recommendations for hosts is covered extensively in the WPMU forums, so you might want to pop by for a search there.

Trent

[@trent Participant 17 years, 7 months ago]

Andy knows about it already, but I am playing with it small scale at http://onvertigo.com

[@trent Participant 17 years, 7 months ago]

Best thing would be to update to 535 as it is working fine for me.

[@trent Participant 17 years, 7 months ago]

Hmm….never really thought about that since I was thinking any plugin would apply to all the themes, but using the right template calls if the statements would work really well wouldn’t it. Thanks for the tip Ron. Usually the simplest solution is right in front of you

Trent

[@trent Participant 17 years, 7 months ago]

Thanks Ron. I will try that out and see what goes on. Did you put ending tags in footer.php then?

Trent

[@trent Participant 17 years, 7 months ago]

Did you put it on the index.php of every single page Ron? What syntax did you use? I was thinking about just putting the if_logged_in argument, but is $current_user better to use?

Trent

[@trent Participant 17 years, 7 months ago]

Problem is that changeset 444 will give errors as I reported in this ticket.

https://trac.buddypress.org/ticket/124

Trent

[@trent Participant 17 years, 7 months ago]

The 150 X 150 error is fixed in the latest Trunk version now! Thanks Andy!

trent

[@trent Participant 17 years, 7 months ago]

I find that users cannot change the avatar as it gives me the “image must be bigger than 150px X 150px” error even though the image is bigger….

Trent

[@trent Participant 17 years, 7 months ago]

Andy has tossed around a few ideas about having the solution you are looking at as an option. There is a thread in these forums that is pretty recent.

[@trent Participant 17 years, 7 months ago]

Great stuff Andy! Let me know if you need someone to test this!

Trent

[@trent Participant 17 years, 7 months ago]

I knew I wasn’t going crazy

[@trent Participant 17 years, 8 months ago]

Need to ask some experts. Playing around, if you use dsader’s privacy plugin, couldn’t you just edit line 120 of bp-core-homebase-functions.php from:

<input type="hidden" name="blog_public" value="0" />

to:

<input type="hidden" name="blog_public" value="-1" />

Wouldn’t that make the blog registered to members of the community only since the -1 is that option for the plugin?

Trent

[@trent Participant 17 years, 8 months ago]

Haven’t tried it yet. Do you mean just creating a new field for everyone through the site-admin ?

[@trent Participant 17 years, 8 months ago]

That is kind of a pain isn’t it. I was a little lucky since most of my blogs on one of my installs were using domain mapping, so I just changed their blog names to something else if they were using their main username and then created the homebase for them with their username. That is why it is easier to start from scratch and import blogs if you don’t have many rather than transforming a huge install over. I am not sure what the solution is, but it would be nice to have the option to put the homebase into an extension URL like username.bloghost.com/profile/ rather than having to have its own blog, but still have the dashboard created for the blog at that extension. All and all it really is a slippery slope either way though…

Trent

[@trent Participant 17 years, 8 months ago]

That plugin will work with BP, but it takes the site-admin manually editing the blog privacy since there is no place for the user to change privacy since it is locked out of the blog admin for home base blogs

Trent

[@trent Participant 17 years, 8 months ago]

This forum is a great idea now that things are moving forward so fast. Good deal.

Trent

[@trent Participant 17 years, 8 months ago]

Looks amazing Andy! I am really looking forward to what trying it out!