BuddyPress.org

@chouf1 –

It’s a baffling decision by the core team – I don’t know why they thought it was reasonable to break the design of every child theme that’s been based on the bp-default parent.

bp-default was not a standalone theme, it was a parent to hundreds of child themes. There was a responsibility to keep it delivering what those child themes had been built to expect.

As @chouf1 says, if this couldn’t be done – the upgrade should have been clearly labelled with a strong unequivocal warning.

It wouldn’t be too late, if they fixed this immediately, and upgraded bp-default so it maintains it’s existing behaviour. If they want to add new features, put them where they belong – in a new theme – don’t change the behaviour of the existing one.

@johnjamesjacoby

If @paulhastings0 can confirm it works, I’ll put it in.

@intimez – Just checked Private Messages for Friends Only and the plugin still works fine on BP 1.2.6.

BP 1.2.6 made some changes to the way buttons are rendered.

If you modified the member header in your child theme, you’ll need to look at the changes made to /members/single/member-header.php and apply them.

I Just installed a fresh copy of wp 3.0.1 and bp 1.2.6 and received a 500 error using

System Linux
PHP Version 5.2.12
Server API CGI

When I switch my php version to 4.4.8 buddypress installs fine then I switch back to 5.2.12 I start to get the 500 errors again.
I am running this install on a shared hosting platform which I do not have access to the apache error logs to really figure this out. I was wondering if anyone else is having this same issue.

Could you write in a recent tread ? This one was opened 8 mounth ago.
MrMaz posted today to announce v. 05 !!!

@mrmaz , Could you please revise the Create a Link page. Categories are smushed together and like Microsoft Notepad when text isn’t wrapped to the page. It makes it difficult for users to add links in an orderly way.

Instead, could each category be on a new line? Thank you.

Thinking the issue lies with:

/messages/messages-loop.php

bp_message_thread_last_post_date()

function lives in:
/buddypress/bp-messages/bp-messages-templatetags.php: line 288

would guess at the filter

bp_format_time(get_date_from_gmt(

is possibly to blame but will have to see if the ticket sheds light on it

cool cheers.

this is/was the relevant ticket I guess?

https://trac.buddypress.org/ticket/2203

To be honest I think the template pack broke for one of the 1.2.5 releases. I have a lot on my schedule at the moment; I will try to get time this weekend to at least figure out what’s broken, even if I can’t release an update.

@gearupandplay To limit the text try this:

for your functions.php :

function Wanna_Limit_Text($Text,$Min,$Max,$MinAddChar) {
if (strlen($Text) < $Min) {
$Limit = $Min-strlen($Text);
$Text .= $MinAddChar;
}
elseif (strlen($Text) >= $Max) {
$words = explode(” “, $Text);
$check=1;
while (strlen($Text) >= $Max) {
$c=count($words)-$check;
$Text=substr($Text,0,(strlen($words[$c])+1)*(-1));
$check++;
}
}

return $Text;
}

this for you template :

post_author )),10,90""); ?>

Where 90 is the number of characters and you just adjust that.

Good luck

Too early to bump

I’ll ask for the sake of it this is a pure install no plugins activated?

I can’t really see what the issue might be but then would normally be looking at logs or running ‘top’ to see processes working

Can’t think what to suggest other than ensure an absolutely clean install just running BP nothing else.

I wouldn’t leave your php.ini public like that for too long

@rogercoathup

That nasty hack shouldn’t be an issue and it is not so much nasty as plain illegal to place style tags as children of ‘body’

This is the ticket I raised ages ago, well I and another but wasn’t aware it was a duplicate, the style rules never were required as the adminbar was removed and didn’t require any styles to help it along, the ticket was moved here there and everywhere, but I forced the issue by moving it back from 1.3 to 1.2.6 and requested that it be dealt with as it was a simple fix so in 1.2.6 those style tags don’t exist. previously I was having to use

remove_action(‘wp_footer’, ‘bp_core_override_adminbar_css’);

If I was hiding the adminbar for logged out view.

hats off to @Chouf1 – a. for solving it, and b. for ‘tagging’ the thread as solved – we should all get into that discipline (although a button to do it automatically would be nicer)

ok… two solutions:

1. the nasty hacky – adding define (‘BP_DISABLE_ADMIN_BAR’, TRUE) in our theme’s functions.php

Why nasty hacky: well it inserts inline CSS into our footer to hide the adminbar and remove the padding; that’s nastiest enough in itself, but it also uses !important to override anything we actually want to do – even nastier.

2. the cleaner – adding remove_action( ‘init’, ‘bp_core_add_admin_bar_css’); in our theme’s functions.php

That does the job!

Unfortunately, we have to add that in the functions.php of any additional theme we want to use. Let’s get all this presentation stuff in the default theme where it belongs (not in the core)… I’ve said this a lot recently.

It should be in the theme not in core files but it needs to load at ‘init’ ? or does it? is it that it must load before theme loads

@hnla – posting simultaneously !

follow up – it’s actually being added in the function:

bp_core_add_admin_bar_css()

in bp-core-cssjs.php

I can’t help but think this should be in the default theme, not in the core files.

/buddypress/bp-core/bp-core-cssjs.php