Actually, that page is pretty outdated.
I'm not even sure if it's mentioned when an install fails anymore.
How to force a re-install is still good relevant advice.
After the merge, they will have the same trac, and the same bug
reporting system.
Aha, I just checked - that link is shown when you get the "No WPMU found
on this host" message when an upgrade fails.
So basically, that message appears when it finds an install, but can't
find some aspect of the main blog in the database.
That help any? :D
Andrea
Carreg wrote:
Right, I've started having a pick through the MU documentation as
promised and one of the first pages which struck me was this one:
http://codex.wordpress.org/Debugging_WPMU. It seems to start off OK (I
did a little tidying), but after the first set of bullet points it moves
on to talking about how to submit bug reports. While this might be
helpful to some extent I'm not convinced this page is the right place
for it.
I didn't compare the instructions on this page to those on the pretty
comprehensive 'Reporting Bugs' page so I don't know how much crossover
there is between the two documents. However it strikes me it might make
sense to add a new section to the 'Reporting Bugs' page which covers MU
and move all that stuff over there. That'll free up the debugging page
to be more about debugging.
I think it's important that page is clutter-free if the page is, as it
says, mentioned when MU throws up install errors.
What do people think?
C
_______________________________________________
wp-docs mailing list
[email protected]
http://lists.automattic.com/mailman/listinfo/wp-docs
_______________________________________________
wp-docs mailing list
[email protected]
http://lists.automattic.com/mailman/listinfo/wp-docs
