[@djpaul Keymaster 17 years, 3 months ago]

Report this as a bug on https://trac.buddypress.org/

[@djpaul Keymaster 17 years, 3 months ago]

Right, I’m going to try to reply to this people, so give me some time.

[@djpaul Keymaster 17 years, 3 months ago]

On a side note, is there any chance of the bp.org theme appearing as an option?

Nope. Search the forums if you want a bit more story on why; this question is asked at least once a week!

[@djpaul Keymaster 17 years, 3 months ago]

You would edit profile fields like this via /wp-admin/admin.php?page=buddypress/bp-xprofile.php on your installation, but it looks like you can’t add a description for the default Name theme (which you can’t edit or remove).

Nice catch. Report it as an enhancement suggestion on https://trac.buddypress.org/; use your username and password from this site to log in.

[@djpaul Keymaster 17 years, 3 months ago]

And before you ask, no, it is not recommended to use the trunk version of BuddyPress on a public website.

[@djpaul Keymaster 17 years, 3 months ago]

Will I risk having to have the whole thing redone at every update?

Yes – because you’ll essentially be customising the default BuddyPress themes.

[@djpaul Keymaster 17 years, 3 months ago]

*When* does that error appear? After you’ve tried to activate BuddyPress sitewide?

[@djpaul Keymaster 17 years, 3 months ago]

Perhaps, but personally I dislike spam inviter tools (see what I did there?).

[@djpaul Keymaster 17 years, 3 months ago]

Does the link work with the regular bphome theme? This facebook 1.0 theme may need updating for the latest version of BuddyPress.

Something else you could try would be to copy functions.php from bphome and overwrite the file in facebook 1.0 theme.

[@djpaul Keymaster 17 years, 3 months ago]

I search twitter for people using various key words, then I send them messages

[@djpaul Keymaster 17 years, 3 months ago]

You have to download and install WordPress MU – https://mu.wordpress.org/

[@djpaul Keymaster 17 years, 3 months ago]

FB-Connect isn’t my favourite bit of software in the world as I spent some time checking out the code once, so there may be a hole there. </randomguess> Certainly my money is on a plugin.

Have a look at the record in wp-signups or wp-users; any clues or differences vs a user who registered properly? Any clues?

[@djpaul Keymaster 17 years, 3 months ago]

When you are installing Buddypress, the only plugin you want in your /plugins folder is buddypress itself. Nothing in /mu-plugins either. Your plugins which run on buddypress are causing this error.

I have a few plug-ins running, but without the admin back end working, I can’t deactivate them. Can I place them in a separate folder temporarily without causing even more havoc? i.e. welcome pack, monty spam, wp ban, limited log in attempts, askimet, etc.

[@djpaul Keymaster 17 years, 3 months ago]

Users and blogs should be ok. Remember you are only going to be replacing the files, you are not going to delete the database or anything like that. Anyway, this sort of thing is why I suggested you back up first, just in case

Yes /plugins

[@djpaul Keymaster 17 years, 3 months ago]

Email is probably going to get you a quicker answer. Only a couple of Automattic employees lurk here afaik.

[@djpaul Keymaster 17 years, 3 months ago]

After making a backup, delete your current BP directory. Download the latest version of BP and use that.

[@djpaul Keymaster 17 years, 3 months ago]

Put it into Plugins and activate it Site wide

[@djpaul Keymaster 17 years, 3 months ago]

Where exactly and when do you want your code to run?

[@djpaul Keymaster 17 years, 3 months ago]

WPMU doesn’t provde that functionality out the box. What about http://wpmudev.org/project/New-Blog-Defaults ?

[@djpaul Keymaster 17 years, 3 months ago]

When you say avatar – if you mean the user’s picture, changing the custom slugs ought to not break this (famous last words). Check you didn’t change that part of the HTML – did you edit any of the template files or the CSS?

Can you give us the web address of your site so we can maybe look at what is wrong?

[@djpaul Keymaster 17 years, 3 months ago]

Oh, and John’s specifically referring to the PHP memory limit value which normally lives in the server’s php.ini file (not system RAM or somesuch).

[@djpaul Keymaster 17 years, 3 months ago]

I think if you rename your /plugins and /mu-plugins (or whatever it’s called; the name escapes me) to something else, that’ll automatically deactivate them when WordPress tries to visit them. I think you have to visit your admin backend for this auto deactivation to happen.

OH! and when I went to check my error log to try and pin point the exact location of the error – all of my logs had been completely and totally WIPED. it showed zero errors. how weird is that?

Check you are looking at the correct file. Sometimes I chase errors then I realise I’m looking at an old log or the wrong file (doh!)

[@djpaul Keymaster 17 years, 3 months ago]

This is the intended behaviour.

[@djpaul Keymaster 17 years, 3 months ago]

Thanks for the heads-up el_terko! I’ve just upgraded to 1.0.2 and nothing obvious is immediately broken.

[@djpaul Keymaster 17 years, 3 months ago]

I suggest if you have problems with the new group stuff in the trunk, please report it as a bug on the Trac. This is exactly what beta code needs (testing) so thank you.