[@adyba Participant 14 years, 8 months ago]

Have you guys tested the fresh installation?

Im about to test this scenario:

1) WP 2.9.x

2) BP install (current state)

3) Upgrade WP to WP3.0b

4) Go to multisite network

5) Refresh BP

Does anybody some strong recomendation (like DONT DO IT ?

[@adyba Participant 14 years, 9 months ago]

I believe the problem is solved!

There must be a minor bug in the new version that I believe is hard to trace on production environment.

As many others I started with brand new WP (2.9.2) installation + new BP (1.2.2.1) on hosted environment. As many others I have encountered problem with permalinks. Tracing down the issue I have relized that the mint installation provides some strange permalink like “/members//messages/sentbox/” with double slashes in it. Newly (generated) user accounts were just fine “/members/user_name/messages/sentbox/”. I have realised that default “admin” user has an empty “nickname” in the WP mint installation (@ standard WP user profile).

BP uses the EMPTY NICKNAME to generate the PERMALINK and thus it is malfunctioned.

Solution is simple. Go for the Admin user account (inside the WP/WPMU) and check the nickname. Once having the proper nickname your BP site should work just fine.

[@adyba Participant 15 years, 4 months ago]

Paul,

The URL where I’m testing the BP is http:// mysupport.byethost13.com it is shared hosting where each subdomain that belongs to my account looks like root. All root files must be uploaded into \htdocs folder that pretends to be root.

Once installed, only the core Blog is fully available. Users (user1, user2) have created their blog(s). Posts are accessible by Site Wide Activity/Wires but no permalinks expect the main blog are accessible. Thus no user nor admin personal blogs (comments) aren’t accessible.

My hosting program allows the .htaccess. The links to the missing elements seems to be OK. It properly generates addresses like http://mysupport.byethost13.com/personal/2009/08/27/hello-world-2/ but it is empty.

The /wp-content/blogs.dir contains strange sub-folder structure

/wp-content/blogs.dir/1/files/avatars/2(4) where two and four is a Id of users that have

uploaded their avatar. Gods know what does it mean the 1 in the root.

For testing purposes I have created your account (Id 4) JDPaul/password. I just wanted to test the BP abbility to access/write the folder. Avatar was uploaded.

My conclusion:

1) BP is talsk to MySql

2) tld/blog works as expected

3) All site.tld/users links + site.tld/groups seems to be fine

4) At least part of the BP code can write the blogs.dir folder

5) For some reason site others blog permalinks site.tld/user1, site.tld/user2, site.tld/personal do not work.

Please feel free to log-in and play. I believe we both need a computer aided check list

1. Which version of WPMU are you running?

WordPress MU 2.8.4.

2. Did you install WPMU as a directory or subdomain install?

directory

3. If a directory install, is it in root or in a subdirectory?

root as much it can be on shared host

4. Did you upgraded from a previous version of WPMU? If so, from which version?

no

5. Was WPMU functioning properly before installing/upgrading BuddyPress?

there was no trafic

6. Which version of BuddyPress (BP) are you running?

BP 1.0.3

7. Did you upgraded from a previous version of BP? If so, from which version?

no

8. Do you have any plugins other than BuddyPress installed and activated?

no

9. Are you using the standard BuddyPress themes or customized themes?

standard – works fine

10. Have you modified the core files in any way?

no

11. Do you have any custom functions in bp-custom.php?

no

12. If running bbPress, which version?

not yet

13. Please provide a list of any errors in your server’s log files.

[@adyba Participant 15 years, 4 months ago]

I’m also struggling the same white-page-bogey. All redirection are fine but points to an empty blogs.dir directory. I’m just going to upgrade my faith. Other users blogs and comments are at least in the databases and once I solve all the .htaccess; blogs.dir ownership issues., it will show up one day.

BTW there is a WP redirection plug-in (https://wordpress.org/extend/plugins/redirection/) that promises to overcome the .htaccess. Would it be a common cure for rest of us? Would anybody help us generate a list/file of redirections that can be uploaded there?

I’m sorry to see the top contributors helping us (lamers) with the server configuration.

Would anybody code a simple system check (list) plug in that would help us (others) to communicate the issues to our host admins? I believe the community would more appreciate you guys to help us all with bigger issues.