Closed
Bug 703072
Opened 13 years ago
Closed 13 years ago
TOC wiki command broken
Categories
(Websites :: wiki.mozilla.org, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: gueroJeff, Unassigned)
Details
According to the wikimedia help, the __ TOC __ command should insert a TOC at the wherever the command is inserted within the document, and not at the top of the page. The __ TOC __ is not functioning this way. The __ NOTOC __ command works exactly as expected though.
|
||
Updated•13 years ago
|
Assignee: nobody → milos
|
|
||
Comment 1•13 years ago
|
||
Jeff,
That's not exactly quite what __TOC__ meta does. Mediawiki will not show TOC if there are less than 4 headers in the content, and you can use __TOC__ to force showing TOC even if there are not enough headers.
Anyhow, yes, __TOC__ can as well be used for positioning the TOC in the content.
Now, back to the topic:
I have tried this on local install of mediawiki using the same skin as on production, and it works well, ie it places TOC wherever I want. That said, it's something in the mediawiki settings that's disabling this, hence CCing relevant people.
|
|
||
Updated•13 years ago
|
Assignee: milos → nobody
|
||
Comment 2•13 years ago
|
||
Can we confirm if this issue occurs on the staging site (wiki.allizom.org)? There are some changes to skins/common that need to be rolled out to production, which may be impacting this.
I'm currently swamped at the moment, so it might be a while if this waits on me...
|
Reporter | |
Comment 3•13 years ago
|
||
The staging site won't let me in to test it. Should I be using something other than my LDAP credentials?
|
|
Reporter | |
Comment 4•13 years ago
|
||
(In reply to Jake Maul [:jakem] from comment #2)
> Can we confirm if this issue occurs on the staging site (wiki.allizom.org)?
> There are some changes to skins/common that need to be rolled out to
> production, which may be impacting this.
>
> I'm currently swamped at the moment, so it might be a while if this waits on
> me...
Have there been any updates to this bug? Just want to make sure it doesn't fall through the cracks :-)
|
|
||
Comment 5•13 years ago
|
||
Sorry about the delay on this... I just emailed you the login info to staging.
However, it's relevant to note that by now there's nothing major on wiki.allizom.org that hasn't been pushed to wiki.mozilla.org. The last month or so has seen all the major changes rolled out. Are you still having the problem on the production wiki?
It might also be worth testing on intranet.mozilla.org, just for comparison's sake. I can't imagine what wiki setting would affect this, but that might give us something to go on.
Thanks!
|
|
Reporter | |
Comment 6•13 years ago
|
||
(In reply to Jake Maul [:jakem] from comment #5)
> Sorry about the delay on this... I just emailed you the login info to
> staging.
>
> However, it's relevant to note that by now there's nothing major on
> wiki.allizom.org that hasn't been pushed to wiki.mozilla.org. The last month
> or so has seen all the major changes rolled out. Are you still having the
> problem on the production wiki?
>
> It might also be worth testing on intranet.mozilla.org, just for
> comparison's sake. I can't imagine what wiki setting would affect this, but
> that might give us something to go on.
>
> Thanks!
You know, I just went through both the production wiki and staging wiki and it looks like the bug has been fixed. Great work! Thanks for your help!
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•