BuddyPress.org

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

@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.

@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?

When could an official fix be expected? Thanks!

You could try GlotPress:
http://trac.glotpress.com

http://blog.glotpress.com – GlotPress blog

It’s not a plugin, but it allows you to translate scripts using a front-end interface.

There’s not much documentation or anything like that since it’s still quite an early script, but if you feel the need to edit language files using a front-end script, GlotPress is an option.

—

[EDIT]
Just found the following WordPress plugin:
https://wordpress.org/extend/plugins/easy-translator/

It’s a little old, but you could give that a shot as well.

Works like a charm for me!

WP 3.0 and Buddypress 1.3 in two steps:

1) Make sure upload_path option is set to wp-content/blogs.dir/1/files
2) in old .htaccess change

RewriteRule ^(.*/)?files/(.*) wp-content/blogs.php?file=$2 [L] TO

RewriteRule ^files/(.+) wp-includes/ms-files.php?file=$1 [L]

Works!

Read and implement everything listed in Pete Mall’s post:
http://is.gd/cT9kB

and FYI, it’s WordPress 3.0 now

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

@andrea_r – Or you can simply read Pete’s post
http://developersmind.com/2010/06/17/upgrading-wordpress-mu-2-9-2-to-wordpress-3-0/

@allenmcgraw – check out this post:
http://is.gd/cTrBB

Locking this thread.

I’m not sure if this is a good solution, but it works for me until a fix is released. I installed the “Page Links To” plugin (http://txfx.net/code/wordpress/page-links-to/), created a new page called “Activity Temp”, and have it redirect to the Activity Stream. I set the temporary page as a child of another page so it doesn’t show up in the main navigation bar.

[EDIT]
Updated patch commited by JJJ:
https://trac.buddypress.org/changeset/3066

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.

Not unless you want to backtrack to WP(MU) 2.9.2… make sure you can revert to your DB backup and filesystem.

I say just wait for a fix unless you’re on a production site.

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.

Keep tabs on this ticket:
https://trac.buddypress.org/ticket/2403

same: https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/wordpress-3-0-buddypress-1-2-4-1-and-activity-stream-as-front-page-possible-fix/

no solution at the moment

I’d recommend not using Twire.

Try Tweetstream instead:
https://wordpress.org/extend/plugins/tweetstream/

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.

@r-a-y thanks for this and I have seen this code before and tried it several times but I cant get it to work…I know its me….Im just not putting it in the right place on the functions.php page. Ive put it at the very start of the page. For example:

function sh_walled_garden()
{
global $bp;

if( bp_is_register_page() || bp_is_activation_page() )
return;

if( ! bp_is_blog_page() && ! is_user_logged_in() )
bp_core_redirect( $bp->root_domain .’/’. BP_REGISTER_SLUG );
}
add_action( ‘get_header’, ‘sh_walled_garden’ );
/* Stop the theme from killing WordPress if BuddyPress is not enabled. */
if ( !class_exists( ‘BP_Core_User’ ) )
return false;

/* Register the widget columns */
register_sidebars( 1,
array(
‘name’ => ‘Sidebar’,
‘before_widget’ => ‘

‘,
‘before_title’ => ‘

‘,
‘after_title’ => ‘

‘

blah blah……….

Is that correct? Because when I do this I get an error reading.

I just need to know “exactly” where to put it on the page. For example put it between “x” and “y”.

Thanks for getting back to me promptly though…appreciate it.