BuddyPress.org

Hmm. So, you’re saying, if I have a non-English version of WordPress (maybe MS subdomain specific), and I try to activate the BuddyPress plugin, it’ll fail and give me the “are you cheatin'” message?

The problem goes away if you removed your localisation? You changed nothing else?

BuddyPress doesn’t use bb_users at all, only wp_users.

You have a standalone installation of bbPress which is where your users database is (because you mentioned bb_users, I expect)? Can we just clarify that you’ve installed WordPress, and activated BuddyPress?

Have you integrated your standalone bbPress install at all? If so, how? Via the “Use an existing bbPress installation” button in the BuddyPress Forums Setup page?

The default view for the member directory is “active members”. This will only show users who have logged in since you activated BuddyPress, and are therefore considered active (last_activity meta is present). If you change the ordering to something else, the members will show.

Technically this comes down to if a user’s “last_activity” record is present in wp_usermeta. I suppose you could pre-prime the last_activity record by something like this: http://buddypress.pastebin.com/USrLFAFH It’s not tested, but I think you could put it in your functions.php. Remember to remove it after one execution, however(!)

It’s worth pointing out that BP 1.2.6 will require WordPress 3.0+.

The latest, generally that’s a given and the only one that would be available to download from the main download link on wordpress.org. That is now 3.01 which combines the old WP MU multi blog capability. BP works fine with latest version of WP.

BP 1.2.6 is set for release any moment now but install 1.2.5.2 in the meantime and update it when available.

Had you ever previously installed BuddyPress or attempted a BuddyPress forum installation on this site / database before now?

Are all the forums broken, or do, for example, newly-created groups’ forums work ok?

Is your WordPress set up as a multisite? (this used to be called WPMU. If you don’t understand this question, the answer’s no)

Are the bbPress tables in your database? For example, wp_bb_forums, wp_bb_meta, wp_bb_posts and so on?

Hi,

You can check this plugin which I recently develop to provide ACL BuddyPress Extended Profiles:

https://wordpress.org/extend/plugins/buddypress-xprofiles-acl/

Hope you find it useful.

Regards,
NetTantra

somewhat related:
http://farinspace.com/multiple-wordpress-wysiwyg-visual-editors/

Wish I could help with the actual visual editor you are working with, but alas no experience doing that, just happened upon the article above yesterday while working on another project. Hope it lends some ideas

@mikey3D

Yes, sorry – I only checked a multi-word post title.

You are correct, categories and tag page titles are behaving differently in default BuddyPress vs. default WordPress install

The function that builds the title in BuddyPress is bp_page_title(). In WordPress it’s wp_title()

The WP function is doing a lot more work with the category and tag slug, taking the name slug it’s been passed (with the hyphens inserted) and looking up the correct (non-hyphenated) title to insert.

OK, two things I suggest:

1. Report this, and suggest that the bp_page_title() function should behave the same as wp_title() for categories, tags, etc. This would be the sensible way for the function to behave IMO. @hnla – is adding this to the trac, the correct way to raise this a possible fix?

2. For a quick fix, code your own title function, and replace the call to bp_page_title() in your header.php with a call to your own function

The function may look a little daunting, but should be reasonably straightforward with a bit of judicious copying and pasting from the existing BP and WP functions.

Cheers, Roger

.You could also try my plugin (he says with shameless self-promoting grin).

See this post for the latest beta version: https://buddypress.org/community/groups/add-all-nav-links-to-bp-adminbar/forum/topic/updated-the-beta/
Here are the user configuration options available in the admin panel under “Settings” > “BP-WP-Navbar”
– Hide or display the main theme navigation
– Hide or display the site name in your new adminbar
– Hide or display the Login and Signup links in the adminbar
– Hide or display the “Visit Random” menu
– Select whether to display top-level WordPress pages horizontally or in a dropdown menu
– Define the label for the dropdown in WordPress 2.x
– If you’re running WP3.x, the plugin will fetch whatever custom menu labels you assign and display them in the admin bar along with all child pages in dropdowns
– Define the label for the Buddypress directory dropdown (default = “Community”)
– Define the font, font-weight and font-style for all menu items
– Define ALL colors: navbar background, main and sub menu item backgrounds, border, text and hover colors too
– Set the overall width of the navbar and of sub-menus
– Set the height of all menu items
– Adjust margins where required
– Reposition your fancy new custom navbar anywhere you like, relative to your theme so it scrolls with your pages

If you add categories to your custom menus in WP3.x, the plugin will pick them up and display them in whichever menus they are assigned to. Give it a whirl.

This is a simple thing to achieve with just a little custom theming. It’s also highly theme specific (if, where, when, how big, etc, you want adverts), and not something I’d expect in a default setup.

If you want a simple plugin solution, there are lots of off the shelf basic plugins in WordPress that should work without problem in BuddyPress (ad-rotator plugins). Use a theme with dynamic sidebars, install the plugins and add the widgets.

If advertising is really crucial to the business, then you are better to work with a full powered ad management system, e.g. OpenX or Google Adserver. Again, these are straightforward to include in a BuddyPress site: create dynamic sidebars in your theme for each of the advertising zones you require, then insert widgets with the ad zone codes from your management system. These ad management systems provide all the options you requested, and a whole lot more.

You can also consider using a different CMS – DotNetNuke has vendors/banners integrated with its source. I’m playing around with several open source CMS. I like WordPress for its end user interfaces and for its social networking applications. But I think I may still prefer DNN for business sites… still evaluating.

I was having 5 or 6 sploggers sign up daily no matter what I did until about 2 weeks ago when I revamped my tactics. Since then, I have had 0 spam signups… not one. Fingers crossed Here’s what I’ve done:

– Removed references to WP/BP in footer text
– Changed the register slug to something unrecognizable that has no bearing whatsoever to the concept of signing up (so even those grossly underpaid 3rd-world human spammers can’t figure it out)
– Installed WPMU Super Captcha to let the nice humans through: https://wordpress.org/extend/plugins/super-capcha/
– Installed WP-Ban to block the not-so-nice ones: https://wordpress.org/extend/plugins/wp-ban/
– Installed Buddypress Humanity as a double-check: https://buddypress.org/community/groups/buddypress-humanity/
– Blocked lists of bad bots in .htaccess as suggested in this post: https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/buddypress-spam/?topic_page=2&num=15#post-60177
– Added “deny from all” in .htaccess for wp-config.php
– If someone does manage to access the register page through a direct url (without visiting any other page first), they are bumped to a GOAWAY page with the following in .htaccess. .

# BEGIN ANTISPAMBLOG REGISTRATION
RewriteEngine On
RewriteCond %{REQUEST_METHOD} POST
RewriteCond %{REQUEST_URI} .wp-signup.php*
RewriteCond %{HTTP_REFERER} !.examplesite.com. [OR]
RewriteCond %{HTTP_USER_AGENT} ^$
RewriteRule (.*) http://examplesite.com/goaway.html [R=301,L]

So far, so good. As I mentioned, not a single splogger has managed to get through in about 2 weeks. If they do, there are 2 ingredients in the above recipe that can be adjusted:
– the captcha image is fully customizable to render bot algorithms redundant (hopefully)
– the register slug can be changed as often as you change socks

On a final note, there are also some interesting tweaks to be found here: http://www.smashingmagazine.com/2010/07/01/10-useful-wordpress-security-tweaks/

I’m having the same issue, did anyone find a solution ?

I had the same issue running XAMPP on Windows 7 Prof and fixed it by adding the sub directory where my wordpress was located to the RewriteBase in the .htaccess file

In my example I installed wordpress in a subdirectory called wp1
To update .htaccess

1. Open .htaccess file
2. modify RewriteBase / to RewriteBase /wp1

You need to enable WP Multisite. This link should help: http://wptheming.com/2010/03/wordpress-3-0-enable-network/

Have you changed your permalinks to something else?
https://codex.wordpress.org/Settings_Permalinks_SubPanel

Set it to anything but the default.

First, you have to change all references to the strings you want to localize so your POT file knows where to reference them.
Then, you need to create a POT file.

Here’s a quick guide I found on Google using poEdit:
http://weblogtoolscollection.com/archives/2007/08/27/localizing-a-wordpress-plugin-using-poedit/

There are others of course!

If you have any Qs, reply back.

@rogercoathup
Especially when multisite is installed, I always recommend that people test their WordPress thoroughly; do custom permalinks work, can you comment, can you register new sites, and so on. Usually it’s a permalink or mod_rewrite

si-captcha doesn’t work on my sites. I’m using https://wordpress.org/extend/plugins/wp-recaptcha/ and it seems to stop some of them. Still not a spam free solution.