BuddyPress.org

Detective, please come and rescue me…

I am trying to achieve the 3 layer approach suggested by outolumo, which looks ideal to me.

I just got a serious inheritance problem…!

Because I need to integrate BuddyPress in a section of a site and not having it run as a whole site, I am testing this set up:

1) The original “WP Theme” as a parent (with just the code in post #2 from Andy, in “header.php”)

2) The “bp-sn-parent” folder stripped out of reduntant files that are already in “WP theme”, keeping just BP folders and “optionsbar.php”, “plugin-template.php”, “userbar.php”, and “style.css”.

Made this theme a child of WP Theme, declaring “Template: wp-theme” in the stylesheet, right?

3) The “bb-default” theme for styling (skinning) and customization.

I’ve declared “Template: bp-sn-parent” so that “bb-default” is a child of “bp-sn-parent”, which is a child of “wp-theme”.

So:

1)”wp-theme” is the parent.

2) “bp-sn-parent” is the child of “wp-theme” (style.css declares: Template: wp-theme).

3) “bb-default” is the child of “bp-sn-parent” (style.css declares: Template: bp-sn-parent).

First problem:

The “bb-default” theme is not showing up in the backend under “Site Admin/Themes”, so I cannot make it available in “Apperance/Themes” to activate it.

If I put a blank “index.php” file in “bp-sn-parent”, than it does show up in the backend, so I can activate it. (Is that normal?)

So, before activating the “bb-default” theme (which should refer to “bp-sn-parent” which should refer to “wp-theme”), I’ve edited the “style.css” in the “bb-default” theme to import the styles from “wp-theme” (because it styles the whole site) with this rule:

@import url( ../wp-theme/style.css );

The result is a that the homepage (normal site) is blank, and the BuddyPress section is there, but messed up and not skinned with “bb-default” styles, and only some styles from “wp-theme” are applied (the footer image is there, but not the header image).

Now, if I go and I activate the “bp-sn-parent” theme, the homepage of the site shows up normally, and the BuddyPress section has some “bb-default” styles and got the header images from the “wp-theme” but not the footer image. And it’s preatty screwed up too.

So, as you see I am trying to achieve this 3 layers set up, but as I said, something with inheritance is totally messed up.

Does anybody have any insights on this. I am sure it could be useful for the whole community.

Thanks.

Sorry, I deleted the post. I pasteed it into the wrong topic.

These screen captures have been out for a bit.

To set the record straight this is completely doable for BP. Our custom theme is similar to this.

My team has seen what Anahita can do. It’s a good setup and code base.

The code is clear, theming is not that difficult.

Having said that we declined a partnership and instead put our contributions toward the Buddypress and automattic stack because of the community which exists today.

A community with plugins, themes, and developers that are never hard to reach.

Of course it would be nice if Matt would maybe lend some help to Andy (dedicated BP) because with any competing product comes comparisons and bigger wishlists.

Even though BP just came out with 1.1.1 it still feels like things are just starting to warm up. Anahita has a ways to go to get here.

(from my iPhone, sorry if this doesn’t make sense.)

Check out this: https://buddypress.org/forums/topic/extending-wordpress-themes-post-experiences#post-24546

This is what I do. You can add this in your theme, in mu-plugins or in bp-custom:

function rk_signup_redirect() {

if (strpos($_SERVER['REQUEST_URI'], 'wp-signup.php') !== false ) {

$url = 'http://ryuuko.cl/register';

wp_redirect($url);

exit;

}

}

add_action('init', 'rk_signup_redirect');

You should change the url to fit your needs, or use a redirect in .htaccess.

The default theme borrows /blog/ so if you’ve installed your WPMU into a subdir called ‘blog’ I guess the redirects are getting confused.

Lisa – I’m going to upgrade my AvenueK9 theme to be compatible with BP 1.1.1 … it works fine right now, but there are a few style issues I’m going to iron out. The documentation is also a bit scanty, so I’ll be more descriptive in the next release to address some of the common questions I’ve been getting for this

yep, there is. you can set your logo as a background image by adding the following to your #header h1#logo a element…

<br />

text-indent: -9999px;<br />

background-image: url(http://blogs.nyu.edu/blogs/jr197/japan/Newsweek_logo.gif);<br />

width: 335px;<br />

height: 78px;<br />

in this case, the text-indent will move your h1 title link -9999px out of view. the second line calls your image logo as a background property; in this case, i just used a newsweek logo. the last two lines define the dimensions of your logo. hope this helps

Quote:

“if any of you want to have an image logo rather than the h1 text, go ahead and change “display: block;” to “display: none;” in the “#header h1#logo a” element. then, drop in your image tag and play around with “padding-top:” values for “#header” “

This certainly works. However, the image is not linkable (I put the image in the #header section section). I can’t seem to put the image in the #header h2@logo a section and also get rid of the text that appeared on top of the image.

Any way I can make the image linkable without going in and modifying the underlying header.php? I’m assuming that I would be creating a whole new parent theme if I need to modify header.php.

Still learning…

I think both the above are on the money. I’d suggest making a link to (does that even make sense in the context of a book?!) https://buddypress.org/extend/themes/

I have the same problem. It seems to be a problem with the default theme:

1) Buddypress deactivated, using buddypress theme – issue

2) Buddypress activated, usibg P2 theme – no issue.

that is a great plugin! Thanks.

I was wondering if there is a way that only the admin could connect blogs to group blogs. In my bp-network users are allowed to open their own group but they are not allowed to start a new blog. But I would like to connect blogs to some groups (as an admin, not group admin). Any idea on this one?

I will update the plugin for 1.1.1

The plugin was made for a early beta of buddypress and is not programmed properly.

I’s a quick and dirty try.

I just started to rebuild my template for the new theme architecture.

Next step will be to rewrite the Seo for Buddypress Plugin and extend it properly.

It just occured to me, that detective’s way is the way the theme framework should be done. Here’s the deal:

1.0:

BP-Blog theme & BP-member theme. The blog theme was essentially any WP-blog theme (with minor tweaks), and the member theme contained the BP functionality. Both of them contained also their separate skins.

Theming was possible by taking excisting WP-themes and BP-themes and skinning them for consistent look. This approach had obvious disadvangages, but the advantage of being able to start from just about any WP-theme.

1.1.

WP-SN-Parent theme is essentially a WP-theme with BP-functionality. Theming is done by childing this theme. This solves issues about non-standard theme structure, but has the downside of having problems with integrating to other themes.

Enter Detective’s solution: in stead of two layers of BP default theme, we should have three:

1) BP-Structure theme (structure)

2) BP-Functional theme (pb-member theme etc. functionality)

3) Skin (CSS+js etc)

Each of these is the child theme of the upper.

Now, since BP-Functional is essentially an unskinned non-complete theme (no headers or footers etc.), it can and must be childed to any theme, not only to BP-Structure. Hence it would restore the 1.0 ability to start from any WP theme, and integrate BP into that. Still it would use the Child theme functionality and live nicely within the WP theme ecosystem.

For bp-theme authors this would mean improved flexibility: they could start by skinning (and maybe extending) the BP-Functional, or just the BP default skin. On the other hand, they could child the BP functional to some existing theme of theme framework – like Sandbox of Hybrid – and skin that.

And the best part is that it would be backwards compatible with the 1.1 framework: the bp-sn-parent is just split into generic structure part an the bp-specific function part, and skinned to the actual default part. And any theme extending (childing) the bp-default could still be extending (childing) it.

This kind of in-between theme is an interesting development in the design of WP-themes, kind of plugin in the theme architecture… Don’t know if it has been done before…

Could this make it into 1.2?

So far 1.1 free theme is only one which you can download directly from this site, other than original buddypress theme.

There’re paid themes, but I believe they aren’t updated to 1.1

Well done on the book. It sounds really cool. There aren’t enough Buddypress themes out there. I am working on a custom parent theme, would like to share it once its done but its nowhere near ready for release.

Why don’t you set up a website and put that address in the book and then link to or keep copies of the theme on your site. That way if sites go offline you won’t end up with dead links in your published work.

When using the auto upgrade, the following error is given. The error states that the plugin could not be activated, but it is activated. Not sure yet if plugin is working properly. I did notice that I lost the small groupblog icon on the group menu. Both the error and loss of icon occurred with the bp-groupblog 1.2 and 1.2.2 versions.

wpmu-2.8.4a, bp-1.1.1 php-5.2.5

Plugin could not be activated because it triggered a fatal error.

Fatal error: Cannot redeclare bp_groupblog_setup_globals() (previously declared in /home/ttacconn/public_html/wp-content/plugins/bp-groupblog/bp-groupblog.php:40) in /home/ttacconn/public_html/wp-content/plugins/bp-groupblog/bp-groupblog.php on line 48

How exactly do you implement this in a new theme:

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

That’s the only thing that I’m guessing could be wrong.

Hi!

I’m also having these problems. Localy (XAMP) it all works okay but uploaded to my webhost none of the pages (members, groups, profile, etc) works.

I’ve tried using the deafult theme and my own theme – no change.

I’ve tried without any plugins – no change.

It’s 1.1.1 and latest WPMU. I’ll see about trunk later on.

I’ve yet to put up another local installation or online. That will be the next step.

Like the first poster I’m using hostgator. How about you rfauster?