BuddyPress.org

I’m running:
bbpress
bbpress Q
Buddypress
Buddypress Human
Buddypress Like
Buddypress Share
Simple Facebook Connect
Custom Login
Quick Chat
WP-FileManager

Hi-thanks modernlooper for your reply
(I have now updated to latest BuddyPress & bbPress plugins-my site runs both plugins!).

Thankfully I have fixed the problem now but it was a bit tricky..
I now think the problem was an issue with x2 specific plugins-Wp Article Fetch & Tweet this.
On deactivating both of these from Network Admin (my site is running WP multisite) my blog (running WordPress & BuddyPress) is back to normal.
The Tweet this plugin is somewhat old & not updated so there could be some code issue with it. As for the WP Article fetch plugin I haven’t used it much so disabling it is no great issue!
(I will look for a new ‘Tweet this’ plugin as Twitter plugins are quite useful)

I still though need to get BuddyPress forums working properly on my site (I have posted several times for help with this on the support forum here but still BuddyPress forums are not running well on my site! If I wasn’t so stubborn to try & get BP forums working I would have deleted it ages ago & used an alternative eg Vanilla plugin or other-so if anyone can help me I would be grateful-but I don’t really expect any response as sadly I have had such limited response in the past from here to help me with this! I think BuddyPress is a misnomer; it could be better called somethingelse but I won’t type it now!..…).

@mercime

deactived both
upgraded wp to 3.4
activated both

still stuck on step 4, still see same error message
still can’t access /forums

Now, I’m running 3.4, but all of the problems are just the same.

Thanks for the reply shanebp.

1. I’m using Batcache, https://wordpress.org/extend/plugins/batcache/ and Memcached Object Cache https://wordpress.org/extend/plugins/memcached/ both of these use memcached for caching. We’ve used W3TC in the past on our WP-only sites, but it got be a little to unstable for our tastes… So far these seem to be working good, though we have to remember to bounce memcached in addition to PHP-FPM when we make a code change.
2. Right now we only have the following tables set to use MyISAM, the rest being InnoDB:
bp_groups
bp_groups_groupmeta
bp_groups_members
usermeta
users
We tried having them all to InnoDB, but due to its poor text searching performance compared to MyISAM, we switch back those 5.
3. TMPFS is worth its weight in gold.

Wow, 30K, very impressive! I’m hoping that there is a lot of performance that can be squeeze out of our DB server, which will be looked at soon by actual DBAs (I do not in anyway claim to be one…). If not, I’m looking forward to BP 1.6 for some of those performance enhancements found from bug #4045!

I downloaded that plugin a while back but was starting to assume it was used to extend groups, what I have done is use Group Hierarchy and limited subgroup creation to top level groups only. Not ideal but should work for what I need so far, I will do what you have suggested though as I think it will be better in the long run to build it from the ground up. Cheers bro

I tested the search_terms the last hours on a local server with 1.5.5 and 1.6 and on an web server with 1.5.5 and 1.6.. The bug won’t go away… But one thing I found out: The Plugin BuddyPress Hashtags make it work… but I is also using `search_terms=`… What is the trick?

Hello, there is a simply solution, few Extension as Buddypress shows messages errors with PHP 5.4, we could hide them.

Bonjour, la solution ci dessous en attendant que Budypress et d’autres extensions ( a vérifier au cas par cas) ne provoque pas d’erreur avec le php 5.4.

We must hide the messages errors / Nous devons cacher les erreurs PHP :

In /wp-includes/class-wp-error.php
/***************************Add after the first < php *************************************/
> after php to close it, don’t appear in this message, don’t lost it to close php
> after php n’apparaît pas dans ce message, ne pas l’oublier pour refermer la balise.
/***************************Ajouter après la première balise< php *************************************/
error_reporting(0);
@ini_set(‘display_errors’, 0);

Or simply directly to wp-config in the root.
Ou simplement dans le fichier wp-config à la racine.

PLus d’info dans / Most info in : http://www.wordimpressed.com/wordpress/php-turn-on-or-off-error-reporting/

With each update of WordPress, we must using this solution
A chaque mise à jour de WordPress, il faut refaire la manipulation si besoin.

Cordially / A bientôt.

CyclonUnited