Make WordPress Core

Opened 12 years ago

Closed 12 years ago

#12177 closed defect (bug) (fixed)

Fatal Error when choosing the user blog name

Reported by: deepcell Owned by:
Milestone: Priority: normal
Severity: minor Version: 2.9.1
Component: Multisite Keywords:
Focuses: Cc:

Description (last modified by wpmuguru)

I got a message, when choosing the user blog name in the option page at Admin menu.

Follow the error bellow:

Fatal Error
If your blog does not display, please contact the owner of this site.

If you are the owner of this site please check that MySQL is running properly and all tables are error free.

Could Not Find Blog!
Searched for cyberia.com.br/blog/ in ruimorei_wpmu::wp_blogs table. Is that right?

What do I do now?
Read the bug report page. Some of the guidelines there may help you figure out what went wrong.
If you're still stuck with this message, then check that your database contains the following tables:

  • wp_blogs
  • wp_users
  • wp_usermeta
  • wp_site
  • wp_sitemeta
  • wp_sitecategories

If you suspect a problem please report it to the support forums but you must include the information asked for in the WPMU bug reporting guidelines!

I had checked all my database and aparently every thing is good.
It's strange to me, 'cause I had only change some options in my admin area and the entire blog crashed Up like a <snip> explosion!

Attachments (1)

error1.jpg (78.8 KB) - added by deepcell 12 years ago.
print of error

Download all attachments as: .zip

Change History (7)

12 years ago

print of error

#1 @ryan
12 years ago

  • Component changed from General to Multisite

#2 @wpmuguru
12 years ago

  • Description modified (diff)

Please refrain from using foul language.

Did you do this on the main blog/site?

#3 @wpmuguru
12 years ago

(In [13039]) prevent editing site domain/path on multisite main site, see #12177

#4 @wpmuguru
12 years ago

  • Priority changed from highest omg bbq to normal
  • Severity changed from critical to minor

#5 @wpmuguru
12 years ago

Haven't had a reported re-occurrence with this.

#6 @wpmuguru
12 years ago

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.