4 points
Community rank #8895
rjmxracer1
NewbieJust Getting Started
MemberLikes (0)
I was using Multi-DB plugin 2.9 for WordPress MU 2.9.2
Recently upgraded to WordPress 3.0.1 and Multi-DB 3.0.2.
The main blog displays blank page with no errors.
I have enabled WP_DEBUG in wp_config.php but still no errors or warnings appear. The PHP log does not display any errors either (though it normally would). All I get is a blank screen + blank error log.
I have also temporarily removed all of the other MU plug-ins that could be interfering.
I am able to access ALL of the 3000 other blogs and the wp-admin perfectly fine.
The root blog (i.e. blog_id 1) was previously located in the database wpmu_c4 (because MD5(1) = c4...) with table prefix wp_1_
Now that I am on WordPress 3, it seems that Multi-DB expects my main blog tables to be located in wpmu_global (i.e. the global database) with table prefix wp_ so I have moved those tables to comply.
I get the feeling that the code must be hitting a dumb exit(); instruction somewhere.
6758 pointsCommunity rank #8Supreme DeityWPMU DEV StaffLifetime member
Developer
(joined June 2008)
Likes (0)
Sounds strange that you are not getting an error and that the rest of the blogs are running ok.
But just to be sure can you check:
1. Is the database connection correct in the main wp-config.php file? Set this to your global database though you can set it to any as long as it is valid.
2. Do you have any other plugin that is just activated on the main blog that could be causing a problem, can you disable all the plugins on the main blog and re-enable one at a time?
3. Can you check your global tables list, and make sure they are all actually in the global database.
4 pointsCommunity rank #8895NewbieJust Getting Started
Member
(joined September 2010)
Likes (0)
1. I have confirmed that the permissions for the configured user are the exact same on the global database as on other working blog databases.
On the original, problematic install, when I change the db login/password settings to something random, I get a fancy, informative database error. Changing it back gives the blank screen.
2. All other plugins are disabled.
3. Before, when the tables were named wp_1_x in the wpmu_c4 database, I was getting some helpful errors regarding missing tables. Now that I have moved tables to the correct location I am getting zero errors.
Here is the list:
wp_blog_versions
wp_blogs
wp_commentmeta
wp_comments
wp_domain_mapping
wp_domain_mapping_logins
wp_gb_templates
wp_links
wp_options
wp_postmeta
wp_posts
wp_registration_log
wp_signups
wp_site
wp_sitecategories
wp_sitemeta
wp_term_relationships
wp_term_taxonomy
wp_terms
wp_usermeta
wp_users
6593 pointsCommunity rank #9Supreme DeityMember of the MonthLifetime member
Keeper of the Dark Chocolate
(joined July 2007)
Likes (0)
marcobrasil65, please start a new thread. Hijacking someone else's thread, especially with an unrelated problem, is really frowned upon on most support forums.
Please make sure you've read the install docs included with the download as well as the sticky:
Responses (5)
Developer (joined June 2008) Likes (0)
Sounds strange that you are not getting an error and that the rest of the blogs are running ok.
But just to be sure can you check:
1. Is the database connection correct in the main wp-config.php file? Set this to your global database though you can set it to any as long as it is valid.
2. Do you have any other plugin that is just activated on the main blog that could be causing a problem, can you disable all the plugins on the main blog and re-enable one at a time?
3. Can you check your global tables list, and make sure they are all actually in the global database.
Member (joined September 2010) Likes (0)
1. I have confirmed that the permissions for the configured user are the exact same on the global database as on other working blog databases.
On the original, problematic install, when I change the db login/password settings to something random, I get a fancy, informative database error. Changing it back gives the blank screen.
2. All other plugins are disabled.
3. Before, when the tables were named wp_1_x in the wpmu_c4 database, I was getting some helpful errors regarding missing tables. Now that I have moved tables to the correct location I am getting zero errors.
Here is the list:
wp_blog_versions
wp_blogs
wp_commentmeta
wp_comments
wp_domain_mapping
wp_domain_mapping_logins
wp_gb_templates
wp_links
wp_options
wp_postmeta
wp_posts
wp_registration_log
wp_signups
wp_site
wp_sitecategories
wp_sitemeta
wp_term_relationships
wp_term_taxonomy
wp_terms
wp_usermeta
wp_users
I am really stumped on this one.
Member (joined September 2010) Likes (0)
Okay, found the problem -- it was an issue with the content of wpmu_global.wp_options.
Thanks for your help!
Member (joined June 2010) Likes (0)
help i m not expert i want multidb in my network
Keeper of the Dark Chocolate (joined July 2007) Likes (0)
marcobrasil65, please start a new thread. Hijacking someone else's thread, especially with an unrelated problem, is really frowned upon on most support forums.
Please make sure you've read the install docs included with the download as well as the sticky:
http://premium.wpmudev.org/forums/topic/couple-questions-and-please-let-me-know-is-this-how-you-install-multidb
If you have a specific question, please be sure to include it.
Become a member