BuddyPress.org

@chouf1 – yes, I know where the adminbar.css file is. Coda is my friend

The question was, why is adminbar.css being included in other themes (even none child ones) on a multisite network? What’s injecting it, and how do we turn it off.

e.g. My theme doesn’t explicitly link to adminbar.css, here’s the snippet from the header.php:

`

<link rel="stylesheet" type="text/css" media="all" href="” />
<link rel="pingback" href="” />
<?php
if ( is_singular() && get_option( ‘thread_comments’ ) )
wp_enqueue_script( ‘comment-reply’ );

wp_head();
`

No explicit inclusion of adminbar.css!

But, here’s what actually gets rendered in the browser:

`

`

The unwanted link to adminbar.css has been injected.

I assume it must be something in wp-head() doing it – is there a hook to turn it off?

Hi Roger,
the admin bar is constructed in bp-core/bp-core-adminbar.php
the css file for this is in bp-themesbp-default_inccssadminbar.css

notepad++ is my friend

p.s. we have the problem in 1.2.5.2 as well

@clojel

You shouldn’t really mod the core files, as they’ll be overwritten if you upgrade. Is there any filter you can hook on to instead as an interim solution?

Certainly though, this should be added to the trac as a potential bug to be looked at.

We have the same problem with child themes in secondary sites – we’ve turned off the admin bar, we don’t have any admin bar css being included in our child theme, but still it pulls in admin bar css code from bp-default and inserts the unwanted padding.

[As an aside: does anyone know where the code is that’s injecting the admin bar css include into the header of child themes? Is it a hook on wp-footer?]

@whitbyglennk
There is no WP ethos of free software for all. With all the licensing discussions going on, most people have completely misunderstood what it was all about. Free (as in the GPL software license) only means that any further development of GPL software has to be published under the same license (if the software is being released) and that, once you have the software, you can do whatever you please with it. Free does not mean, though, that you can get access to this software without paying. It’s perfectly ok to charge for GPL software.

Most developers, who charge for a plugin or premium themes, still give back to the community by answering questions in forums or uploading other plugins and themes to the WP repository. For some plugins 50+ hours have been spent on development. That’s a lot of money and time right there, but people still expect not to pay anything.

I guess we’ll be seeing more and more paid plugins and themes crop up over the next year. It’s not a bad thing, it’ll give users more choice (there usually is a free alternative around somewhere) and if someone buys a plugin/theme, then afterwards you can expect great support, which does not always happen with a free plugin.

Just me 2 cents

can you provide your server php info ? especially php memory_limit
who is your host ?
what’s your WP and BP version ?
mySql version ?
php version ?

@hnla – I think I’d class it as a bug, as it breaks child themes on existing sites
… or perhaps just a deprecated / implementation changed without clear warning mistake

Glenn… there is nothing new in charging for premium themes, it’s not a BuddyPress phenomenon… there are hundreds of people selling premium themes for WordPress (e.g. WooThemes, ThemeForest, …), and even more sites that are completely bespoke developments costing many thousands of pounds.

If you don’t like what people are providing you for free, you don’t have to use their work. If you don’t like the price of their paid for work, don’t buy them. You can take the bp-default theme for free and extend it as you want.

As I explained in one of your other threads about availability of themes, BuddyPress is extremely difficult to create distinctive generic themes for – it’s no wonder that some people charge a few pounds for their themes.

Yes, there is a BuddyPress primary site … where you’d run a BuddyPress specific theme, that lets you view members directories, group directories, member profiles, etc.

Error after 1.2.6 upgrade

Warning: move_uploaded_file() [function.move-uploaded-file]: Unable to move ‘/tmp/phpgytUT4’ to ‘/home/collabbo/science3point0.com/wp-content/uploads/group-documents/7/1287752340-blogcont.png’ in /home/collabbo/science3point0.com/wp-content/plugins/buddypress-group-documents/include/classes.php on line 234

Look in the documentation on this site about installing BuddyPress in a secondary blog.

That tells you how to do this

If everyone’s going to be friends with everyone else, I’d suggest just turning the Friends component off since it won’t be doing anything interesting. Dashboard > BuddyPress > Component Setup

As for groups, you have a few options. If you make all groups public, then everyone will have access to everything. And if you hide all of the “my groups” and “join this group” buttons in the theme, people will never know (or care!) whether they’re a part of groups. They’ll just be auto-joined if they choose to post on the forums. A different method is to modify something like this: https://buddypress.org/community/groups/auto-join-groups/

@djpaul –

Can we happily run the 1.2.5.2 default theme (and children thereof) on the 1.2.6 core? Thereby allowing all our existing child themes to continue to behave the same without any mods at all?

And, as a corollary to this… is there an install option for 1.2.6 that won’t overwrite the 1.2.5.2 theme (other than copying it somewhere pre-install, and then re-instating)?

I have been trying to help you!

Try Dashboard > BuddyPress > Forum Setup and then reinstall and set up a new bbPress installation. It sounds like something is wrong with your bb-config.php.

If nothing else works, and you don’t yet have any content in your installation anyway, you should consider wiping your database and starting from scratch. Clearly something has happened that is keeping BP from communicating with your bbPress database tables.