BuddyPress

fixed with buddypress v1.2.5 release

nevermind – adding that will cause all 404 pages to default to the activity stream

I’ve got something to help you out.

Wait until BuddyPress is 3.0 compatible.

I actually thought it would be out of the gate considering the time frame of the Wordpress 3.0 development and the popularity of BuddyPress.

I just tried an upgrade and it was a failure to say the least. One of the issues is what your encountering.

This is in local testing finding a code solution but thanks for the response.

(…and technically 1.2.4.1 was suppose to be WP 3.0 ready while BP1.3 dependent on features of WP3.0 )

So it was supposed to be ready? Very interesting. We’ll there’s at least two of us who know the truth about that statement. It’s too bad. I just started with BuddyPress and with so much attention I expected to see something a little more polished. Am I expecting too much given it’s maturity? I’ll have to evaluate that question a little closer.

just taken from the dev meeting logs and 1.2.4 announcement (http://buddypress.org/2010/05/buddypress-1-2-4/)
“This highly anticipated version provides fixes to 74 reported tickets and adds improved support for WordPress 3.0 to help ensure a safe and worry free upgrade.”

Perplexing? lots of back slapping on that link announcement yet 1.2.4 does not work particularly well with 3.0 or particularly badly (to be fair) Why? not necessarily criticizing just rather bemused by BP development and testing.

[EDIT]
Updated patch commited by JJJ:

http://trac.buddypress.org/changeset/3066

@r-a-y thanks a lot for that. This is a good workaround for now.

When could an official fix be expected? Thanks!

@r-a-y Thanks r-a-y that does indeed fix things, albeit in a hackish manner

I understand what you’ve done with it, and it occurred to me that there may well be an issue with many who are using bp-default and choosing or at least attempting to choose activity stream as front page, they will not be running a child theme?

I had a play around with the bp-default functions file and specifically the function: ‘bp_dtheme_page_on_front_template’ controlling this aspect, keeping your workaround in mind I simply adjusted the add_filter from:

add_filter( ‘page_template’, ‘bp_dtheme_page_on_front_template’ );

To:

add_filter( ’404_template’, ‘bp_dtheme_page_on_front_template’ );

This appears to work correctly on one of my clean installs WP 3.0 BP 1.2.4.1 bp-default

Although this is adjusting core file, in the interim/short term until the correct solution is found would this not serve those that I mentioned above and when that correct solution found the hack would simply be overwritten in a point upgrade?

This isn’t a hugely tested solution, it works on the surface on one of my various installs, but there may well be issues I have missed, it’s suggested more as food for thought.

Lastly I can imagine that there are going to be many rushing into upgrading (that ‘upgrade now’ button is like the red ‘Do NOT Press’ button; too much of a temptation ) Although the upgrade is not problematical the few manual steps required might well cause some people issues and the fix discussed here be required so as such it might be worth a sticky post pulling the steps together along with any other fixes one might require, that people can be pointed to?

@hnla – While your method is well-intentioned, it breaks actual 404 pages. Try typing in example.com/hfklsadjfkasdhf and you’ll see the activity page, instead of the 404 page!

You could just copy my code directly into the bp-default theme’s functions.php so it will be overwritten when the next version of BP comes out.

FYI, the code can also go in wp-content/plugins/bp-custom.php as well and not necessarily in a child theme’s functions.php file.

Ah erm so it does; did say it wasn’t hugely tested. Ok then those that are running on bp-default theme will need to add your function to main functions file, please ignore my well intentioned but erroneous post above. (Last para stands thinking about though, the flood gates will open soon)

Thinking further it makes sense to add fix to main functions or bp-custom[bp-custom.php isn't a standard included file] so that it does get erased from existence on upgrade – one less thing to remember to adjust for people

thnx ray

@ray added code to functions in bp default

but getting eeor wen going to login pae, logout link ..

header modification already send some sort error