BuddyPress.org

Those don’t appear to have an action or a filter attached. If you make an enhancement ticket on https://buddypress.trac.wordpress.org/, we can add some to the next version of BuddyPress for you.

We fixed this in trunk the other day. Take a look at the change here: https://buddypress.trac.wordpress.org/changeset/4351/

@eventfulsd

When logged-in, simply visit the Members Directory or the member’s Profile and click “Add Friend”.

EDIT: remember to also make sure “Friends” is enabled under “Buddypress” > “Component Setup” in your WordPress backend.

Yes…. with the ‘world famous’ wordpress 5 minute installer and not cpanel – although I’ve never used cpanel or any host’s wordpress installer….

If you have the necessary information to hand, it should be a simple and reliable process…

If the wordpress files are ok and all present then it should be possible just to delete the wp-config.php file (or rename it to something like wp-config.php.bak in case you neet to refer to it again), and go to your web address.

Ideally you should delete all the wordpress files, get the latest versions from wordpress.org and then re-upload them via ftp ( using a ‘client’ program such as filezilla ) to make sure that they are all uploaded correctly. Delete the WordPress database user and table through cPanel control panel.

Sometimes there are problems when not all the files have been uploaded, or have been corrupted, but I haven’t had any problems using filezilla….

@jstebbing better late than never
`add_filter( ‘bp_get_group_description’, ‘do_shortcode’ );`

I don’t understand what you mean by ‘bunches’….

If you look at the wp-config-sample.php it should have a text block at the beginning like the following (quoted from wp 3.1.2)
`
<?php
/**
* The base configurations of the WordPress.
*
* This file has the following configurations: MySQL settings, Table Prefix,
* Secret Keys, WordPress Language, and ABSPATH. You can find more information
* by visiting { @link https://codex.wordpress.org/Editing_wp-config.php Editing
* wp-config.php} Codex page. You can get the MySQL settings from your web host.
*
* This file is used by the wp-config.php creation script during the
* installation. You don’t have to use the web site, you can just copy this file
* to “wp-config.php” and fill in the values.
*
* @package WordPress
*/
`
those /* and */signs mark the beginning and end of text blocks that should be ignored in a .php type file…. ( this also true for single lines beginning // )

Make sure that is the case with your config file.

To edit php files you should use a text editor such as notepad++ rather than a wordprocessor such as MS Word.

If it doesn’t already exist you can just add

define('WP_MEMORY_LIMIT', '64M');

to the wp-config.php in the wordpress root directory.

It needs to go somewhere above

/* That's all, stop editing! Happy blogging. */

There are situations where this won’t have any effect, so you could try asking your host to increase your wordpress memory limit, or do a search on that subject as there are other ways to do it yourself…

If that doesn’t work, and for some shared server hosts it won’t, then have a look at the suggestions here and here.

Or find a host that offers more memory – which could be difficult as all the other shared hosting services, that I’ve found, don’t quote the memory available in their advertising….

https://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP

It’s on the BP 1.4 roadmap https://buddypress.trac.wordpress.org/ticket/2348 – BP Roles and Capabilities

As hnla said, search the site or wordpress.org forums. This has been discussed a million times, and there is no point in starting a new discussion.

https://buddypress.org/community/groups/installing-buddypress/forum/topic/windows-iis6-problems-404-error/ which leads to https://buddypress.trac.wordpress.org/ticket/2299

Anything in your web server’s error log?

Nothing to say yet, but the next major release of BuddyPress, 1.3, is something we’ve been working on for a long time and is getting closer. You can review the current roadmap of issues to address at https://buddypress.trac.wordpress.org/report/11

Mmmm weird.. BuddyPress and WordPress SEO just work fine both enabled. The trick I posted is to offer full compatibility for WP SEO URL rewriting. If you get completely blank BuddyPress pages something is really messed up. I did not know Hybrid worked with BuddyPress but I think the error is to be found there. Try enabling BuddyPress and WP SEO and switch to the default buddypress theme. If it still gives you empty pages then reinstall both WP SEO and BP.

No, BuddyPress absolutely requires custom permalinks. What about putting “%post_id%” into the custom field? I’m not sure what the default behaviour is when permalinks are not set, so you may need to play around — take a read of https://codex.wordpress.org/Using_Permalinks#Choosing_your_permalink_structure

Or, what’s the URL to your site? Have you installed WordPress in a subdirectory called “members”?

Could you report as a bug on https://buddypress.trac.wordpress.org/? We may have already fixed it in our development version of BuddyPress, but you reporting the issue would prompt us to check. You can use your username and password from this site. Thanks!

There are two posts, the sitewide tags plugin copies the post onto that designated blog, so it’s working properly, although not the way you want it.

Something like this might work, but I’m not sure where best to put it. Try testing it in your theme’s functions.php for now (easiest):

`
global $wpdb;
if ( (int)$wpdb->blogid == (int)$bp->site_options )
remove_action( ‘save_post’, ‘bp_blogs_record_post’, 10, 2 );
`

== I have installed and reinstalled WP3.1.2 + BP 1.2.8 from scratch ==

When you say you did it from scratch, do you mean you uploaded WP files manually and not used webhost script like fantastico and the like? If you used the webhost script, I suggest you drop tables from DB, delete .htaccess file and re-install WordPress manually via FTP/cpanel. I’ve seen dozens of BP install problems arising from the fact that WP was installed using those webhost scripts.