It should work. Did you set BP_ROOT_BLOG in your wp-config.php to the correct site ID?
yes, that is done, but I still see the same in setup screen, I tried deleteing the plugin and reinstalling and still the same, slugs in the root blog not sub-domain.
so I have to install it and then do redirects as in the page? although it said it’s not needed in fresh install.
We’ll need to check. I’m at work at the moment, but I’ll create a trac ticket so we are sure that we test this out
A note on this. may or may not be relevant.
Have two test multisite installations both with subdirectories and both with bp installed on a subdirectory via wp-config -define ( ‘BP_ROOT_BLOG’, 14 );
One (say A) I left BP on 1.2.9 and then on 1.2.10.
The other (say 
I was continually updating via ftp to server with the trunk version right up to 5176 (which btw is labelled 5175 on trunk page). here the bp subdirectory is (define ( ‘BP_ROOT_BLOG’, 2 );
B is fine up to now with 5176
To-day, once 1.5 was made official I tried updating A in the normal fashion via the WordPress.
disabled plugins etc
Went to Wizard but the references to the bp pages are all for blog id 1 not to blog id 14 and if i go to the pages via browser I get Error 404 – Not Found
Hope this is of some use. Thanks for all the work you guys have done. Is there any remedy for Site A (not urgent).
reinstalled 1.2.10 on site A. all well.
An update. I ran through a few tests this morning, with
`define( ‘BP_ROOT_BLOG’, 2 );`
I tested on two kinds of MS installations: one with subdomains and one with subdirectories. In each case, I installed BP 1.2.10, then upgraded to 1.5. In each case, everything worked fine. The pages in the wizard dropdown were from blog 2, *not* blog 1. This is as expected; see https://buddypress.trac.wordpress.org/browser/tags/1.5/bp-core/admin/bp-core-admin.php#L535
For now, I have closed https://buddypress.trac.wordpress.org/ticket/3602. If anyone can give steps to reproduce (perhaps I’ve misunderstood something about the process), please do so on that ticket.
@boonebgorges have you tried fresh 1.5 install instead of upgrading?
I have been frustrated the last 2 hours trying to do it, and the same still happen, I even updated to wordpress 3.3 on one test site to see, but still without any hope.
I’m not upgrading, I’m installing 1.5 from scratch on subdomain multisite, can you try that and see if the bug reproduced for you?
@boonebgorges have you tried fresh 1.5 install instead of upgrading?
I have been frustrated the last 2 hours trying to do it, and the same still happen, I even updated to wordpress 3.3 on one test site to see, but still without any hope.
I’m not upgrading, I’m installing 1.5 from scratch on subdomain multisite, can you try that and see if the bug reproduced for you?
I just tested and it mostly works. I did realize that you are correct that the reported URLs are incorrect, ie that it says
`Automatically create a page at: http://domain.com/members/`
instead of
`Automatically create a page at: http://site2.domain.com/members/`
However, when the pages are actually created, they are created properly on the secondary site. The BP installation works correctly on http://site2.domain.com when finished.
I just tested and it mostly works. I did realize that you are correct that the reported URLs are incorrect, ie that it says
`Automatically create a page at: http://domain.com/members/`
instead of
`Automatically create a page at: http://site2.domain.com/members/`
However, when the pages are actually created, they are created properly on the secondary site. The BP installation works correctly on http://site2.domain.com when finished.
wow! I have been postponing my site for a week now cause of a false alarm! sweet 
It worked now, perhaps you can change the ticket subject to correcting the links that appear, it can give someone a hard time like it did to me.
wow! I have been postponing my site for a week now cause of a false alarm! sweet
It worked now, perhaps you can change the ticket subject to correcting the links that appear, it can give someone a hard time like it did to me.
redid this now. and success. Convoluted explanation. Script not executed memory shortage !
Added define(‘WP_MEMORY_LIMIT’, ’64M’); to wp-config. No relief !
but am redirected to page not found but with a reference to myEasyBackup plugin.
Deactivated this plugin.
Logged out. Logged in.
reinstall.
Am asked by BP about permalinks and then to create each page-click and am redirected to the CORRECT subdirectory (ie blog 14).
All as it should be from then on.
Thanks and sorry for wasting time.
redid this now. and success. Convoluted explanation. Script not executed memory shortage !
Added define(‘WP_MEMORY_LIMIT’, ’64M’); to wp-config. No relief !
but am redirected to page not found but with a reference to myEasyBackup plugin.
Deactivated this plugin.
Logged out. Logged in.
reinstall.
Am asked by BP about permalinks and then to create each page-click and am redirected to the CORRECT subdirectory (ie blog 14).
All as it should be from then on.
Thanks and sorry for wasting time.
No time wasted – thanks for your help and patience debugging https://buddypress.trac.wordpress.org/ticket/3639
No time wasted – thanks for your help and patience debugging https://buddypress.trac.wordpress.org/ticket/3639
