[@djpaul Keymaster 17 years, 1 month ago]

@Tore, no, BP 1.1 themes go into /wp-content/themes/ like any other wordpress themes.

/wp-content/bp-themes/ is from the previous version of BP and is deprecated.

[@djpaul Keymaster 17 years, 1 month ago]

First of all, a find in files would probably point you in the right direction. Secondly, *what* link(s)?

[@djpaul Keymaster 17 years, 1 month ago]

This is an issue with the plugin, not BuddyPress. Make sure that you are using the most recent version of the plugin and that it is compatible with BP v1.1.

If you are using the most recent version, then contact the plugin developer and let them know about the error message.

I’ve also moved the topic to the ‘Third Party Components & Plugins’ board.

[@djpaul Keymaster 17 years, 1 month ago]

Is this in a plugin or a theme?

[@djpaul Keymaster 17 years, 1 month ago]

Right, figured this one. It’s because you are all using the BP 1.0.3 ‘bphome’ theme with BP 1.1. This is a bug.

If you are intentionally doing the above, you’ll have to wait for a fix.

But if you just want to use the current default theme that comes with BP 1.1, check that you have the /wp-content/bp-themes/ directory deleted. And if you were upgrading, that you didn’t accidently copy/activate ‘bphome’ into /wp-content/themes/.

[@djpaul Keymaster 17 years, 1 month ago]

Sorry, I was going through 30+ threads at the same time. Thought yours was an upgrade.

[@djpaul Keymaster 17 years, 1 month ago]

You need to also delete the records beginning with ‘bp-‘ in your sitemeta database table.

[@djpaul Keymaster 17 years, 1 month ago]

It worked for me – and I suspect plenty of others – so there’s probably a bug lurking somewhere.

So just to check – delete /wp-content/bp-themes/. Put the new two theme directories into /wp-content/themes/. At this point, going to the BuddyPress admin backend (in /wp-admin/) will get you a red warning box.

Then go to http://example.com/wp-admin/wpmu-themes.php, activate ‘BuddyPress Default’ (not ‘BuddyPress Social Network Parent Theme’). Then you should be able to activate the ‘BuddyPress Default 1.1’ theme on http://example.com/wp-admin/themes.php.

[@djpaul Keymaster 17 years, 1 month ago]

Marking this as resolved. The next version of BuddyPress will also include a free kitten wearing an orange hat.

[@djpaul Keymaster 17 years, 1 month ago]

You are continuing to run a separate install of BBPress alongside BP 1.1?

[@djpaul Keymaster 17 years, 1 month ago]

madloki, he’s just released a major new version of BuddyPress 2/3 days ago. Any further release – unless there’s a genuine critical bug found, and this isn’t one – I expect will be quite a few weeks at the very least.

Obviously a trunk code fix will happen as soon as Andy or someone else contributes a fix.

[@djpaul Keymaster 17 years, 1 month ago]

Blogs.dir is created with the same user/group permissions as that which is running the web server. If it is not your server, you need to talk to your host and ask them do delete blogs.dir (or whatever you want to do).

[@djpaul Keymaster 17 years, 1 month ago]

Please continue this discussion on this thread.

[@djpaul Keymaster 17 years, 1 month ago]

I’m also going to mark this thread complete as the original poster’s user account has apparently been deleted at some point.

[@djpaul Keymaster 17 years, 1 month ago]

If /wp-content/bpthemes/ exist, BP will try to use pre-version 1.1 themes.

If that folder doesn’t exist, it will load from /wp-content/themes/ as like normal WordPress. This is explained perfectly well in the upgrade documentation and throughout this forum.

[@djpaul Keymaster 17 years, 1 month ago]

Of course there’s a BuddyPress “API”. How do you think we write plugins and themes that rely on BuddyPress? If you are specifically talking about stuff like how WordPress can use XML-RPC for remote blog posts, then, no, there’s nothing like that at the moment. You could use the AJAX functions for quite a lot of stuff, however.

I would imagine this is a very low priority feature suggestion and such a thing would more likely be driven by someone writing some kind of external app.

[@djpaul Keymaster 17 years, 1 month ago]

Do not post duplicate threads.

[@djpaul Keymaster 17 years, 1 month ago]

Just pushed up a new version of Welcome Pack for BP 1.1.

[@djpaul Keymaster 17 years, 1 month ago]

You are not following the upgrade instructions properly. There’s a document linked on the news post on the front of this site to an in-depth article, but:

1) Deactivate all of your plugins, but not BuddyPress (yet).

2) Remove any plugins out of your mu-plugins folder.

3) Change your theme back to the standard WordPress theme.

4) (Now) deactivate the BuddyPress plugin.

5) Delete BuddyPress off your server and the /wp-content/bp-themes/ directory.

6) Upload 1.1 and move the new themes into /wp-content/themes/.

7) Reactivate the BuddyPress plugin. Reactivate the BuddyPress theme.

Reactivate any other plugins you took out in step 1.

[@djpaul Keymaster 17 years, 1 month ago]

Ultimately this is a theme design decision and you can customise it yourself in a child-theme.

[@djpaul Keymaster 17 years, 1 month ago]

Have you *got* a http://domain.com/wp-content/plugins/buddypress/bp-forums/bbpress/ folder?

[@djpaul Keymaster 17 years, 1 month ago]

This is a WPMU question and you are best off looking on their forums. I think this is a setting in the Site admin panel, though.

[@djpaul Keymaster 17 years, 1 month ago]

Can you upload a screenshot and a ticket to https://trac.buddypress.org/? I don’t run a Windows PC so I can’t use IE.

[@djpaul Keymaster 17 years, 1 month ago]

There was a bug with WPMU reporting this message, but it still activated the plugin correctly.

If that’s not the case for you, we need more information: https://buddypress.org/forums/topic/when-asking-for-support

[@djpaul Keymaster 17 years, 1 month ago]

Without seeing your error logs, it is impossible to help.

Be sure you are following these upgrade instructions *exactly*.