WordPress.org

Make WordPress Core

Opened 10 years ago

Closed 10 years ago

#12850 closed defect (bug) (invalid)

WP3 beta fails after enabling network

Reported by: OiPenguin Owned by:
Milestone: Priority: normal
Severity: normal Version: 3.0
Component: Multisite Keywords: reporter-feedback
Focuses: Cc:

Description

After enabling the network feature (MU) according to the instructions (http://codex.wordpress.org/User:Andrea/Create_A_Network) pages in the admin fails to load completely. I've attached a screenshot from Firefox. Opera produces the same error. I've tested on Ubuntu 10.04 beta running Apache.

Attachments (1)

wp3beta_fail.png (74.4 KB) - added by OiPenguin 10 years ago.
The image depicts the page as printed from bottom up. A button to confirm changes and probably some more settings are missing.

Download all attachments as: .zip

Change History (10)

@OiPenguin
10 years ago

The image depicts the page as printed from bottom up. A button to confirm changes and probably some more settings are missing.

#1 follow-up: @sivel
10 years ago

  • Cc matt@… added
  • Component changed from General to Multisite
  • Keywords reporter-feedback added; network removed

A few questions/tasks for you:

  • Did you put the required code for wp-config.php above the "That's all, stop editing! Happy blogging." line?
  • Can you enable WP_DEBUG by placing define('WP_DEBUG', true); in wp-config.php above that same line?

I see the rest of the page without problem. If you do not see any errors printed please try checking your apache error logs.

#2 @wpmuguru
10 years ago

Try dropping the network tables and re-enabling the network from scratch. That screenshot looks like it picked up an existing network install that was set up a while back in the alpha.

#3 in reply to: ↑ 1 @OiPenguin
10 years ago

  • Cc lars@… added

Replying to sivel:

  • Did you put the required code for wp-config.php above the "That's all, stop editing! Happy blogging." line?

I missed this part of the instruction. After placing the required code above the "That's all, stop editing! Happy blogging." line the page loads completely.

However, I don't succeed in creating new sites despite double (or triple) checking that my settings are correct according to http://codex.wordpress.org/User:Andrea/Create_A_Network. I do however suspect that the error is related to a local issue. Hence, this report should probably be classified as resolved?

Apologize for the slow reply, I'd forgotten to register my e-mail address.

Yours,

Lars

#4 @nacin
10 years ago

However, I don't succeed in creating new sites despite double (or triple) checking that my settings are correct

What do you mean by that? How are they not successful?

#5 @OiPenguin
10 years ago

I'm afraid I'm unable to elaborate any further. If you could tell me how to trouble shoot or what logs to investigate I'll do my best to contribute.

My issue: When attempting to create site /localdomain/wp3/test2 with email tes2@… the page loads forever. When I go the Users the user test2 is created, as is the site /test2 however when trying to access backend (../test2/wp-admin) the page is non-existent and nothing is created in /var/www/wp3/wp-content/blogs.dir

Yours,

Lars

#6 follow-up: @wpmuguru
10 years ago

This is most likely something with your server config. The uploaded media folder isn't created when you create a site. That's done when the first media item is uploaded.

#7 in reply to: ↑ 6 @wpmuguru
10 years ago

Replying to wpmuguru:

This is most likely something with your server config. The uploaded media folder isn't created when you create a site. That's done when the first media item is uploaded.

Do you have rewrites enabled on you vhost entry?

#8 @OiPenguin
10 years ago

I believe I have enabled rewrites, but the problem persist. However, I'd rather attribute the error to misconfiguration on my part rather than a bug in Wordpress. I suggest changing the status to resolve as invalid.

#9 @nacin
10 years ago

  • Milestone 3.0 deleted
  • Resolution set to invalid
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.