[@djpaul Keymaster 16 years, 10 months ago]

Do not try to uninstall BP by deactivating it in the admin.

This is caused by a known WPMU bug.

[@djpaul Keymaster 16 years, 10 months ago]

Replying to six month old threads that have been marked as ‘resolved’ (Green traffic light) will mean most people will skip the thread.

But, https://wordpress.org/extend/plugins/custom-profile-filters-for-buddypress/

[@djpaul Keymaster 16 years, 10 months ago]

@David – downloads plugin at https://wordpress.org/extend/plugins/buddypress-group-documents/. I haven’t tried it yet, but it looks good.

[@djpaul Keymaster 16 years, 10 months ago]

This is on the roadmap https://buddypress.org/about/roadmap/

[@djpaul Keymaster 16 years, 10 months ago]

For starters, disable all plugins (other than BuddyPress) whilst you get the main issue resolved.

Since you say the signup link didn’t work either, I think this is a ‘pretty URLs’ issue. Ask your webhost if mod_rewrite is enabled (or equivalent)

[@djpaul Keymaster 16 years, 10 months ago]

Obviously 1.2 in under development and not everything is guaranteed to work properly. If you haven’t enabled blog privacy (which turns off the sitewide activity posts for that blog), please report it as an issue on http://trac.buddypress.org using the same username/password which you do here.

[@djpaul Keymaster 16 years, 10 months ago]

A post has been deleted from this thread as it was little more than spam/advertising.

[@djpaul Keymaster 16 years, 10 months ago]

Probably just not compatible with the current version of BuddyPress. Try contacting the author and see if they plan to update.

[@djpaul Keymaster 16 years, 10 months ago]

I’ve marked this thread as resolved

[@djpaul Keymaster 16 years, 10 months ago]

Probably your plugin is getting loaded before BuddyPress is.

I’m not even sure this code works as it should, but try adding this (renaming the function of course):

/* Check that BuddyPress is loaded before Achievements */

function dpa_load_buddypress() {

if ( function_exists( 'bp_core_setup_globals' ) )

return true;



/* Get the list of active sitewide plugins */

$active_sitewide_plugins = maybe_unserialize( get_site_option( 'active_sitewide_plugins' ) );



if ( !isset( $active_sidewide_plugins['buddypress/bp-loader.php'] ) )

return false;



if ( isset( $active_sidewide_plugins['buddypress/bp-loader.php'] ) && !function_exists( 'bp_core_setup_globals' ) ) {

require_once( WP_PLUGIN_DIR . '/buddypress/bp-loader.php' );

return true;

}



return false;

}

add_action( 'plugins_loaded', 'dpa_load_buddypress', 11 );

[@djpaul Keymaster 16 years, 10 months ago]

(Then of course you can rename your plugins folder back afterwards, and reenable the ones you want to keep)

[@djpaul Keymaster 16 years, 10 months ago]

Quick fix

Rename your /plugins/ folder to anything else i.e. /plugins-disabled/.

Visit yoursite.com/wp-admin/plugins.php. This will disable all plugins but should get you out of trouble.

[@djpaul Keymaster 16 years, 10 months ago]

Look at bp-core-settings.php in the bp_core_screen_general_settings() function. It is the line that begins

add_action( ‘bp_template_title….

which sets the title. It calls the bp_core_screen_general_settings_title() function which returns the title. Two options – create a custom language file and translate the title there, or figure out where/how to remove_action that line.

[@djpaul Keymaster 16 years, 10 months ago]

*IF* the error is the memory one, have a look at https://buddypress.org/forums/topic/500-errors-1and1-webhost#post-29415

[@djpaul Keymaster 16 years, 10 months ago]

Just tried to look but I’m getting a totally blank page. Guess you’re trying stuff.

When you say “any plugin”, which plugins specifically are you referring to? It is possible they out are of date and incompatible with the current release of BuddyPress. The trick to find out is to disable all plugins other than BuddyPress itself, and use the default (unedited) BuddyPress theme, and test your site. If you are still getting this sort of problem, then it’s either a BuddyPress bug or something specific to your setup.

If the problem is only recreated when a plugin is re-activated, then you need to contact the author of that plugin and ask when it will be updated to work with the current version of BuddyPress.

Also, thank you for trying Achievements

[@djpaul Keymaster 16 years, 10 months ago]

That refers to moving the current backwards compatibilty code OUT of the main BuddyPress plugin and moving it to a new, optional plugin (“BuddyPress Legacy”, or something). It won’t be any new code than what there is in the current release.

[@djpaul Keymaster 16 years, 10 months ago]

I want to say “1.2 doesn’t contain any database changes”, but then John’s going to pop in and say something has (probably the activity tables if any). If you are asking will the current trunk version database schema change when 1.2, I doubt it. I think Andy said he’s code-freezing BuddyPress 1.2 at the end of December to allow about a few week’s worth of testing.

Being close to the release of 1.2 (close to a beta, anyway), I’d suggest using 1.1.3 for now. Everything should upgrade easy to 1.2 when that is released.

[@djpaul Keymaster 16 years, 10 months ago]

Settings template is hardcoded at the moment (yes, we know). That file is a remnant from an earlier version of BuddyPress that was meant to make it easier to create one-screen plugins.

[@djpaul Keymaster 16 years, 10 months ago]

*cough* Yours for a billion squillion dollars.

This is one of the best threads I have read this week. I have no time left this evening to share my thoughts fully, but in a nutshell, I think for a quick blog post option in the BuddyPress (frontend? UI?) — *not* just the home blog theme, like P2 — makes sense. I think it would be worth exploring the idea in this discussion.

As such, I spent the evening throwing together a plugin that adds a ‘New Blog Post’ link underneath a user’s “Blogs” menu. You can get the alpha 0.1 release from http://djpaul.dangerous-minds.net/postcard.zip (it’s called “Postcard’).

As its an alpha and I’ve only spent about 3 hours on it so far, the form doesn’t do anything yet, but I’d like some feedback on what people think. I’ll probably end up releasing it as a plugin anyway.

[@djpaul Keymaster 16 years, 10 months ago]

The early versions of the P2 theme had messy JS backend making it tricky to move (IMO).

Erich above wrote “An average user probably only wants to write some text and post an image or a video” – this is a different task than what the WP

posting backend was built to do. That’s why P2 was so popular because it encouraged microblogging using the WordPress platform.

[@djpaul Keymaster 16 years, 10 months ago]

It’s not as simple as that. One thing you will need to tackle is getting bbPress and BuddyPress sharing the same cookies for user authentication. You need to select the ‘use existing install’ option on the BuddyPress admin to configure BuddyPress; if you have previously selected the new install option, I don’t know what the impact will be if you then tell it to use an existing install.

What you need to do is find a tutorial or guide for how to install BuddyPress forums (previous to version 1.1, you had to do it manually and it was very complicated). You could start by reading backwards on https://buddypress.org/forums/topic/forum-install-some-helping-hints-2

[@djpaul Keymaster 16 years, 10 months ago]

I’m marking this as not an issue as there’s never a guarantee that the trunk code is going to be stable. As Andy says, report bugs in development versions on https://trac.buddypress.org/

[@djpaul Keymaster 16 years, 11 months ago]

Please make a new thread for the new issue; this one is about something else and is eight months old

[@djpaul Keymaster 16 years, 11 months ago]

You don’t need two threads for the same issue. Since you have https://buddypress.org/forums/topic/can´t-upload-avatar, I’m closing this one.

[@djpaul Keymaster 16 years, 11 months ago]

You need to upgrade; this bug was fixed in a recent version.