BuddyPress.org

Well, most twitter users don’t have a good blogging platform ,so microblog and use a very good blog platform.

So more choices for the site owner.. I don’t feel the need for FB user to use wordpress cos they have a many apps (crap) on facebook already than twitter !

Sorry for bumping this old post, but life is evoluting…

Such a plugin exist now:

https://wordpress.org/extend/plugins/buddypress-group-documents/

Speaking of your Achievements plugin, do you plan on offering an update that allows us to make new achievements without editing the source code?

Feel free to email me back if it helps.

There is also a solution for that.. It’s called Community blogs: https://wordpress.org/extend/plugins/bp-community-blogs/

From the plugin description:

By activating the Community Blogs plugin, Administrators can give immediate registered user status to any member of their BuddyPress enabled site on the blogs they choose. All the member has to do is visit the blog. The user is silently added as a registered user of that blog. Administrators can choose the role the new user has. Either Contributor or Author. Admins can give access to all users or users from specific BuddyPress groups.

As soon as a (registered) users visit the Blog (in your case Community Voice page) it automatically gets added as an author and is allowed to post! Great huh?

https://wordpress.org/extend/plugins/buddypress-links/screenshots/

Hi,

First of all: thanks for BuddyPress, great work

I’m building a new template for my BuddyPress site, but for some reason Ican’t get the custom template pages working. I copied an existing archive.php file to links.php,

put

<?php

/*

Template Name: Links

*/

?>

at the top of the code and put the file into the sn_parent directory.

When I add a new page in admin, I’m not able to select the template of the new file. Is this different then WordPress? Or am I doing something wrong.

I feel that maybe the life-stream should hacked or this FYI: https://wordpress.org/extend/plugins/complexlife

because it a simple and powerful plugin,and different from the other feed aggregator…

Hello guys.

I’ve just started developing a child theme for a theme I’m almost finishing developing and I got frustrated with this same behavior.

I will try to explain it better. As I’ve noted, WordPress doesn’t see the child theme as the actual theme, so bloginfo('template_directory') will return the parent theme.

BUT, if you faced this situation you already know that the sole unique parent theme’s file that is not inherited by child themes is style.css, which is the only file a child theme is needed to have. If we want to use parent theme’s style.css we must import it using @import url(../parent-theme-folder/style.css);

That’s why bloginfo('stylesheet_directory') returns the child theme path. As a record, template_url also refers to the parent theme.

I’m not sure of that, but I believe we can nest themes on a list, having THEME-1 as the root, THEME-2 as its child implementing some new extra stuff and THEME-3 having THEME-2 as its parent and adding a few more features. That’s not as impossible to happen as some may thing, I’ve already seen a few Thematic’s child themes, and if you wanna use any of them and do a few changes to their CSS, having 2 nested child themes is really possible, if WordPress supports it of course.

And with that we may end up with a now real problem: template_directory points to top parent theme, and stylesheet_directory points to the bottom child theme… Probably middle child themes will break when they try to access their files using stylesheet_directory and they are not found…

WordPress really needs to solve this, they should implement something like templatedir('theme-name'), where we can access any theme we want, even classic and basic…

For now what I’m gonna do is use PHP constants. My parent theme already has its:

define('THEME_PREFIX_PATH',bloginfo('template_directory'));

And for my child themes I’ll do the same using stylesheet_directory. Doing so, if someday WordPress gives a final solution for this mess, we’ll just have to use it on this constant and all our child themes will be fixed.

It’s sad but seems to be the most maintainable solution I’ve found.

@ pcwriter: Did you remove the kubrick theme from your theme folder (standard wordpress theme). I had the same problem a while back, solved it by placing the kubrick theme back in the themes folder.

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/

Just a note to say that I tried looking at Atahualpa to modify it for use with Buddypress, and the code is an absolute nightmare to work with. And it’s a table-based layout.

Yes, it has a lots of options. But if you want to mod it, ugh… There’s loads of other themes out there with options pages.

edit: to answer your original question, in taking the navigation on the right, just move the code in the theme into a nav spot where you want in the header, and style it to go horizontally.

It’s not really BP specific, or even MU-specific. It’s all a matter of styling.

https://codex.wordpress.org/Creating_Horizontal_Menus

I’ve added the WP abstraction code that will allow BuddyPress to run on all WordPress versions to the trunk. This code will more than likely be needed even after the merge, so I want to get it in there and up and running for 1.2.

I’ve had it going for a while locally, so it seems silly to sit on this until 1.3. After the merge I will tweak where needed, but I don’t anticipate much change since the multiblog features of 3.0 will simply be an on/off setting.

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

@David – fair point. fyi, group notifications: https://wordpress.org/extend/plugins/group-forum-subscription-for-buddypress/

About how member/profile data is stored in the database, Andy Peatling wrote:

I’ll be reworking the schema in 1.2, interested to hear your ideas.

I sent you a lengthy mail through the system, again describing the problem as I see it, but probably not enough solutions. I came across this in another thread:

I’m now using another 3rd party plugin for membership to the site (WP eMember). While it has its own table, it also creates a matching WP user for each of the members it creates.

I haven’t tested the various commercial membership plugins yet (Memberwing, Wishlist, …), but they must all have their own solutions for the problem. I’m curious what their database tables look like…