BuddyPress.org

I believe our issues are different but both may be directly related to conflicts between buddypress and feedwordpress. Buddypress is a sitewide plugin and the buddypress bar loads for every blog page – so every blog error could potentially be related to buddypress. I don’t have my problem when buddypress in deactivated. So my issue (and yours) with feedwordpress may be a buddypress issue rather than a wpmu issue.

Given your pm reply, I assume you’re not experiencing the same error as I. I have not seen the issue you reported either.

https://buddypress.org/forums/topic/feedwordpress-and-php-warning

The problem with using the default child theme as a base for a new theme is that it is much more work. Rather than fit the thousands of WordPress themes into the default child theme, it seems easier to fit the needed BuddyPress features into the style of the many, many WordPress themes being produced for free or commercially.

Well… this doesn’t help… but really… as far as popular CMS tools go… the WordPress backend is about as easy and intuitive as it gets. I find most clients take to it pretty quickly and easily and end up loving it and using it a lot. Compare that to Joomla sites I’ve worked on where the clients end up abandoning the site because it take a computer science degree to wrap your head around it’s confusing interface and concepts. Again… I know that doesn’t really help you.

Have you looked at limiting user roles and screen options to streamline the WP backend? I always set clients up with something less than full admin privileges and turn off a bunch of screen options they won’t need or understand.

My bp component working fine in 1.0.2 but giving me warning in 1.1.1

I replaced

bp_core_add_nav_item(

__( ‘Example’, ‘example ),

$bp->example->slug

);

by

$args = array(

‘name’ => __( ‘Example’, ‘example’ ),

‘slug’ => $bp->example->slug,

‘item_css_id’ => false,

‘show_for_displayed_user’ => true,

‘site_admin_only’ => false,

‘position’ => 99,

‘screen_function’ => false,

‘default_subnav_slug’ => false

);

bp_core_new_nav_item($args);

but giving me warning

call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, ” was given in /opt/lampp/htdocs/wordpress-mu4/wp-includes/plugin.php on line 414

Thanks in advance

Same here I have been looking at doing a rewrite of the dashboard side for users, because not everyone is a seasoned wordpress user.

Very nice work. It’s the use of buddypress as a CMS that I’m interested in and this is a good example. Patiently waiting for your learnings, expecially integrating as a CMS with other aspects of WordPress. http://www.tastykitchen.com is my model, but I have no idea how to accomplish that.

@sdrib

this is what I am looking for, absolutely need somethin like this.

The WP-Dashboard is just too complicated for my users.

Please let me know about the outcome……

You’re welcome porceon.

Let me know how it goes, and don’t heistate to post your experiencies here.

As I told you I didn’t get to finish integrating, and I’ve to put in on hold, while I am working on someting else. So your experiments with this way of integration may turn helpful.

Cheers.

How about at least adding the admin bar dropdowns in the buddybar? It would be great to have some options, to simply check what would be included.

For example with the current buddybar it is such a pain just to edit a post I am watching (myblogs -> correct blog -> wp-admin, wait to load, then click edit posts, find correct posts, then edit, while in the regular admin bar it is just ‘edit this’

Of course, it could work the other way around: add BP dropdowns in the regular admin bar would work as well.

Obviously there are a few big issues with your install causing all of these problems.

8. Do you have any plugins other than BuddyPress installed and activated?

Yes several of them.

Deactivate all plugins other than BuddyPress. Use the default theme that comes with BuddyPress 1.1.1. Do you still get these white screen problems?

Do you get anything in your webserver error log? A white screen error can be caused by lots of things. Finally, which company provides your hosting?

I did it with P2 and an Artisteer-theme. It’s pretty much finished.

Just integrated as per codex instructions (copied all the folders and some files from BP-theme).

1. I called for another CSS in the header instead of in the actuall css file. Had problems with the latter.

2. Didn’t register userbar/optionsbar. Integrated them into navbar or individual pages (all user settings was placed on “profile”). This wasn’t intended at first but was a great way of handling the horizontal space problem. P2 and my theme are intended for a width of about 900px. Without the vertical userbar/optionsbar you can make it fit into that small space.

3. I made all the content fit by handling the CSS item “content” with a good width and overflow.

4. This however made me have problems with the sidebar widgets that are hardcoded (please make them into widgets instead). I had to rip them out because they disturbed the layout.

5. Had to do some additional skinning and handle a fixed amount of categories for the forums.

I just love how components.css did a lot of the work. Thanks a lot Andy!

This is awesome. Of course, I’m not a coder and don’t understand it yet, but it’s a beginning. I will try the same thing with Hybrid theme next month. Not sure about using the custom function, but if it’s easier and more flexibile, I guess I’ll learn.

Thanks for sharing this. I’m sure MANY are thinking about how to do this

@proceon

A lot about what you’re trying to achive is said here: https://buddypress.org/forums/topic/new-theme-framework-and-exisiting-wp-themes

Otherwise, I myself am trying to get a step by step procedure to integrate BuddyPress as a section of a “normal” website, that is not full BuddyPress based.

So far, form my experiments with theaming and integrating I can say:

1) Delete all the files from “bp-sn-parent” that are already in your WP Theme (header.php, footer.php, index.php, …). Leave just all sub-directories and “optionsbar.php”, “userbar.php”, “plugin-template.php”, “style.css.

2) Copy this at the bottom of “header.php” (WP Theme):

<?php if ( !bp_is_blog_page() && !bp_is_directory() && !bp_is_register_page() && !bp_is_activation_page() ) : ?>

<?php locate_template( array( ‘userbar.php’ ), true ) /* Load the user navigation */ ?>

<?php locate_template( array( ‘optionsbar.php’ ), true ) /* Load the currently displayed object navigation */ ?>

<?php endif; ?>

3) In the header (comments) of the “style.css” in “bp-sn-parent” theme write this:

Template : your-wp-theme-name

…so you make this theme a child of your WP Theme, right?

4) Activate the “bp-sn-parent” theme in the backend, under “Site Admin/Themes”, then activate it under “Apperance/Themes”.

This will be the theme ofor the whole site, but it’ll call all the WP theme templates when no BuddyPress functions are needed. It’s a reverse way of doing the integration. I think it’s better.

This procedure makes a lot of what you need, I think. Like, it gets your WP Theme working as it should and it “calls” the BuddyPress into play only when needed.

But, I need to warn you that I am still struggling with styling (or skinning) the BP theme.

So, I am still on it. But maybe it was worthing sharing already what I got so far, so that other may take it from there.

Hope it helps…

Check out this plugin…it will do mostly what you need, including creating a group specific blog. What more, it includes a theme for that blog and remains tied to the group, so you can pull in group information on that blog.

However, it only allows one blog per group. Check out the details here:

https://wordpress.org/extend/plugins/bp-groupblog/

Group specific forums are already inherently part of groups since BP1.1 came out.