722560 - Trouble editing the MozillaWiki

Status: RESOLVED DUPLICATE of bug 738257

(mozilla.org Graveyard :: Webdev, task)

Description

[Mark LaVine [:mlavine]]

I'm unable to edit the MozillaWiki - the rich editor won't load and won't let me open any other kind of editor to add to content to a wiki.

Thanks for the help

Comment 1

[Corey Shields [:cshields]]

Can you still edit with the default editor?  I'm not aware that we have a rich editor installed..

Comment 2

[Jake Maul [:jakem]]

This is a bug in our wiki skin. The rich text editor doesn't work, and once you're in it you can't get back out of it. Here's a workaround that will get you back to a usable state.

When you're on an edit page and it's broken, append this to your URL and hit enter:

&useskin=vector

This will load up the stock 'Vector' skin, which works properly... it takes a few seconds for the rich text editor to load, but once it does you can use it or switch back. Once you're switched back, the normal skin/editor should work again.


Assigning to webdev as a mediawiki skin issue. For anyone reading this, we *need* to rewrite our wiki skin... we keep running into problems like this due to poor MediaWiki backwards compatibility... skins must be re-based on the default skin for every major version upgrade.

Comment 3

[Mark LaVine [:mlavine]]

"When you're on an edit page and it's broken, append this to your URL and hit enter:

&useskin=vector

This will load up the stock 'Vector' skin, which works properly... it takes a few seconds for the rich text editor to load, but once it does you can use it or switch back. Once you're switched back, the normal skin/editor should work again."

This allowed me to edit the wiki just fine but after saving the page, the text shows up as a wonky mix of code/links/words. I know I'm entering the info in correctly.

Comment 4

[Jake Maul [:jakem]]

The text that appears wrong... did you enter that with the normal editor or the rich-text editor?

I don't think the rich text editor actually works properly with our skin... I wouldn't try to use it (or use this "%useskin=vector" trick) beyond getting *back* to the normal editor.