Forum Replies Created
-
It’s a blank white screen because the theme is erroring out on you looking for Buddypress.
Always check your error logs on the server. You may have to temporarily rename the theme folder to be able to get into the backend.
Gonna share?
“you will have a merge script to port any existing installation to the new structure,”
Just a minor correction: in 3.0 you just upgrade. That’s it.
There were tow conversations going on about needing a script, one was in regard to making wp 3 have multiple blogs. This happens now in trunk via switching on an option. (way cool btw)
The other conversation about needing a script, was referring to people who had multiple single WP installs and wanted to merge them into one wp 3 install.
So – if you start now with BP on MU or on WP, when 3.0 comes out, you upgrade as usual.
And it’s WordPress 3.0.
Andy, I’ve been working with someone else havign this exact same issues, and here’s what we’ve narrowed down (if it helps).
For instance:
In bp-activity/bp-activity-templatetags.php, about line 491 or so: bp_activity_insert_time_since();
That function returns a value through a filter, which has a value created by the function bp_core_time_since();
That function is is ./bp-core.php, around line 1329 or so.
In this function, something quirky is going on, but not “always”.
Thus far, it only seems to be related to activity updates, although it could be more?
(Just created a group, it did it too, and shows 6 hours ago in the activity feed.)
So, I’m putting some echo’s and a die in the time_since function.
Here’s the output:
date passed: 1264065210
As passed into function. ($older_date)
date strtotime: 1264065210
The date passed is run through this:
<?php $older_date = strtotime( gmdate( 'Y-m-d H:i:s', $older_date ) ); ?>This does nothing to the date passed. The string is the same.
newer_date: 1264086810
This is generated if there is not a $newer_date passed into the function to compare the older_date to.
Code:
<?php $newer_date = ( !$newer_date ) ? ( strtotime( gmdate( 'Y-m-d H:i:s' ) ) + ( 60*60*0 ) ) : $newer_date;?>This produces, for the first time, a different time string, which is 21600 seconds ahead of the current server time.
since: 21600
The difference between the newer_date, and the older_date.
21600 seconds, or 6 hours, which is the difference between my server time and GMT.
current_time: 1264065210
This is just time() from the server. (Matches what was passed in)
– The date passed into the function is the current server time.
– The “newer_date” is generated as GMT.
So now, the question is this.
Theoretically, if the server time is ahead of GMT, the following will fail:
<?php if ( 0 > $since ) ?>This is checked right after the difference between the date passed (older_date) and the newer_date.
As the date passed in would be ahead of GMT (current server time), and newer_date will always be GMT if it is created within the function.
Soooo…… does this look trac worthy?
White screen is always an error of some kind, usually php. that’s why there is no one answer and everyone says read the error logs.
It;s designed this was to suppress the output of the specific error for security reasons (at least that’s what I remember from a while ago).
I think you need to add your GA code to it.
in 1.2 or if you;re using trunk, the theme will declare itself.
So in the future, there won’t be a need to move it.
“I don’t expect the number of template changes to be as significant after 1.2. “
This makes me feel better.
There has been a LOT of theme changes in the past, and once BP is into the greater WP world, I’m afraid too many in the future will turn people off. 
So if it’s mostly settled down at 1.2, that’s good news.
And there’s also the difference between giving the exact same specs to a handful of devs and getting widely varying quotes back.
