BuddyPress.org

@Gam3con, open your style css file and change a {color: #717171;} to a{color:#FFFFFF;}

you done.

I find this completely odd because BuddyPress does not auto create a username on the registration page from the database. Maybe you have mal-ware or something? Also it could be the browser auto filling.

Did you create the network using these steps?
https://codex.wordpress.org/Create_A_Network

Because you’re using subdomains, you’ll need to set that up correctly as well:
https://codex.wordpress.org/Create_A_Network#Step_2:_Setting_Wildcard_Subdomains

Btw, this is a WordPress problem; did you try posting your question over there?

Support Forums

Hi thewhyteempire, please do not post duplicate threads:
https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/buddypress-doesnt-work-when-i-enable-the-network/

Closing this one.

You’d probably want to hijack the $bp global when a group page is displayed.

If you’re using BP 1.2.x, look particularly at `$bp->is_item_mod` in /buddypress/bp-groups.php

@digitalhytop – BuddyPress is a WordPress plugin; front page handling is a WordPress thing.

Modemlooper’s link is a good place to start.

When you create a new page for your frontpage, you’ll probably want to create a page template for it:

Page templates: The untapped potential of WordPress

I was wondering myself how to do this. But the instructions above do not apply to BuddyPress, since the “Front Page Displays” settings are all missing from the main BuddyPress site under Settings.

So you basically want someone to develop a site for you? If you do not no how to develop a custom BuddyPress component then hire a developer.

Thanks to Katrina Willis (http://katrinawillis.com), my partner on the UGN site, for figuring out the issue. Here is how she describes the fix:

“On ugnchicago.com, I finally figured out why my name was displaying in the form field.

In the SQL database, I was the default user (the user with the id=0), so that made my first name display as a default string when you installed the BuddyPress forms (which populates a default into the field). I went in and manually removed that from the database, so we’re clean!”

I hope this helps you all. And check out Katrina’s site, while you are at it!

tagged: @PeterHatch, @modemlooper, @JaredGoyette

Eventpress works great to me in WP 3.2.1 multisite and BP 1.2.9. I have used the plugin Multisite User Management to mange all the users roles and to change them to the Event creator role in the main site.

By the way, the only bug that I have found is that the link created in the admin bar in: My account -> Events and My acoount -> Events -> My events don’t work propertly, if I click them, they go to the site_url

Anyway, great plugin, congrats!

You can also create your own BuddyPress component that way things you post into it will work similar to Facebook’s activity stream.

@Webbasica I accomplished that by using the MultiSite feature… each “fanpage” is a blog. When I started my community I studied Facebook Fan pages and concluded that they should not be able to send private messages to their fans, nor tag members on pictures nor make mentions (@username). Therefore I opted for using “blogs” as fanpages, any business or brand or institution can create a blog and post things, entries, pictures, etc. They can have a king of profile, an about pre-set page and their activity wall is a page with almost no content and all comments! This works also grate if you’re using oEmbed plugin which allows you to paste youtube videos urls and it will be the same than embedding them… so I just think they’re perfect. Let me know if I can help you further… regards

That sounds like a bug. Could you open a ticket on trac.buddypress.org please?

Well I managed to import 30k members and 297k forum posts into the new bbpress plugin. Now we just need the plugin to work with buddypress and I’m set.

This should provide a good test prior to our updating the larger sites with 500k+ members and millions of posts…

here it is…https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/search-php-template-vs-custom-bp-loops/ (no responses)

and i’m wondering if this is to do with it … https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/why-does-a-page-named-search-redirect-to-members-search/

@larrysmith1000, @Arwym, @FitzUCF, @janismo, @hnla
I don’t know if anyone is still looking at this, but I think it is a topic that is worth pursuing. What seems to be getting lost though is what it takes to do the job.

A facility like Justin Tadlock’s members plugin is a big help. It provides a mechanism to define and edit roles and apply them to users. That covers a lot of territory. However, unless the content management part of the software looks for and enforces those roles, it is meaningless. Justin provides a facility to do that if what you are talking about posts/pages and potentially custom post types. That is fine for WP content or even things like BuddyPress Docs where Boone implemented it as a custom content type (although I haven’t look at the details of his implementation relative to permissions). However, BP adds additional content types. And it is not just FORUMS. Groups are a content type. Private messaging is a content type. etc.

That is where the current_user_can() checks make sense. Users should have permission to perform actions. That doesn’t necessarily mean new roles, but it does mean distinct capabilities. Those capabilities can then be assigned to any role that makes sense. But the capability list needs to be published like it is for WP https://codex.wordpress.org/Roles_and_Capabilities

The mechanism for assigning capabilities to roles and roles to users and doing the actual check is all WP. It’s already there. Justin provides UI to access it. What I am seeing missing in BP is published string literals that have meaning in terms of capability sets and I assume the current_user_can() checks that actually make it happen. (I looked for it on Google and this is where I was directed!)

@DJPaul you talked here in terms of BP1.3, which is now 1.5 I believe. Did any of this actually make it into the code? If not, it sure would make sense to me to find it’s way on to a revised RoadMap.

My 2 cents!

As for BuddyPress, delete spammers and spams with links leading to viagra, etc. Re SEO plugins and sitemaps, these are supposed to help with Google ranking not the other way around. Site URL?

https://codex.buddypress.org/home/

Currently setting up and updating docs for BP 1.5 – feel free to list down specific information you need here and/or even submit articles as well.

I was posting on a StudioPress forum about their efforts to upgrade their Genesis Connect plugin for compatibility with v1.5 and asked about the recommended install process (uninstall/re-install). The answer in part was:

“There are BP 1.2.9 functions calls in GC 1.0.7 that are not in the BP 1.5 beta-2. If you leave GC 1.0.7 active and upgrade BP, you end up with call to undefined function errors both in the front end and in the admin area of your site.”

BP 1.5 seems like a major move and, from what I’ve seen as I begin to look at it, a very beneficial move. However, it also seems, from the discussion in this forum, to be a move with big impact in terms of plugins. I’m new here, but on that basis I have a question:

Would it have been possible or make sense to ease the transition in some cases by providing some adapter functions that would translate old replaced functions with re-directions to their new counterparts? The old functions could then be identified as deprecated and removed at a later date, but in the immediate horizon some plugin modules might continue to work rather than needing to be modified or abandoned? Simply dropping stuff without fair warning seems drastic.

It might not be possible in all cases, but it might help with the transition. I know a lot of people want to move forward to the new v1.5 and this type of code strategy might help.

Just a thought.

BTW – I’m beginning to play with beta 5029 and it looks fantastic! Great job … you guys did a lot of good work!

@sirspacey I’m already working on a plugin for this. You can read the discussion here: https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/how-to-add-fields-to-group-creation-with-group-extension-api-please-read/