Closed
Bug 510694
Opened 15 years ago
Closed 15 years ago
SUMO / broken templates
Categories
(mozilla.org Graveyard :: Server Operations, task)
mozilla.org Graveyard
Server Operations
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: mossop, Assigned: chizu)
References
()
Details
See the error at the top of the url.
Comment 1•15 years ago
|
||
It looks fine to me. What's the problem?
Comment 2•15 years ago
|
||
OK, one of our hosts is acting up. Looking into it.
Comment 3•15 years ago
|
||
OK, something's borked. I've contacted MindTouch support, but I'd like IT to restart the wiki to clear this up for now, while MindTouch investigates possible causes.
Assignee: nobody → server-ops
Severity: normal → blocker
Component: Administration → Server Operations
Product: Mozilla Developer Center → mozilla.org
QA Contact: administration → mrz
Version: unspecified → other
Updated•15 years ago
|
Assignee: server-ops → justdave
Comment 4•15 years ago
|
||
Restarted deki on both boxes, and flushed the cache on the netscaler, doesn't seem to have helped any.
Comment 5•15 years ago
|
||
21:16:51 <sheppy> Just noticed that the namespace was set wrong for the mediawiki extension on one of the hosts; changed it to the correct value and restarted it. Hopefully that fixed it.
21:17:05 <sheppy> It was set to "use default" but I've found that doesn't always work in our setup.
Comment 6•15 years ago
|
||
21:17:47 < sheppy> I am seeing that on one of the hosts, I'm not getting a link in that "New in JavaScript 1.8.1" box though.
Comment 7•15 years ago
|
||
dropping sev and throwing this back in the pool... no idea what's going on here and not sure what we can do without help from someone at Mindtouch
Assignee: justdave → server-ops
Severity: blocker → normal
Comment 9•15 years ago
|
||
<MaxM> looking at the stack trace of the server i narrowed it down to a sproc
<MaxM> not sure why it's puking on you guys now but mindtouch 9.08 has most of the calls to that sproc obsoleted
<MaxM> the remaining calls to util_String_SplitToTable are with numeric ids as input instead of page titles which seemed to have caused the issue with extended chars
Was an upgrade to 9.08 already planned for the mdc?
Comment 10•15 years ago
|
||
Yes. When is 9.08 coming?
Comment 11•15 years ago
|
||
/me notes that the crash has nothing to do with the template malfunctions (that I know of). The crash stuff is over on bug 510746
Comment 12•15 years ago
|
||
It does, actually. The crash causes the wiki to act up, which causes the extensions to die, and some of them fail to start back up on their own.
Comment 13•15 years ago
|
||
Except that everything got kicked after the last crash, and it didn't fix the problem.
Comment 14•15 years ago
|
||
Yeah, because some debris is getting left behind. I think the mono bug we installed a new mono to try to resolve is still happening; basically there are situations where some cruft gets left behind when mono-based tasks fail, and eventually if it happens enough times, the mono processes won't start up correctly anymore. I strongly believe these problems are related.
Comment 15•15 years ago
|
||
Turns out the settings for the mediawiki extension had gotten badly hosed, apparently as a result of the crashes the other day (although I can't say that for certain, it seems unlikely to be a coincidence). I've at least mostly restored those settings, and most stuff should be working correctly again. I'll do a more thorough testing pass once my fever comes down.
Comment 16•15 years ago
|
||
Changing summary to better describe what this is about. After reading the last comment, however, I feel this is fixed. Re-open if I misunderstand.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Summary: Something seems broken about the templates → SUMO / broken templates
Comment 17•15 years ago
|
||
Yes, this is fixed.
Comment 18•15 years ago
|
||
Bug 510761 is not fixed, see for example
https://developer.mozilla.org/en/CSS_Reference/Mozilla_Extensions or
https://developer.mozilla.org/en/Firefox_3.6_for_developers
{{template.cssxref("foo")}} links to
https://developer.mozilla.org/en/CSS:foo instead of
https://developer.mozilla.org/en/CSS/foo
All recently added properties are completely broken, e.g.
{{template.cssxref("-moz-background-size ")}},
{{template.cssxref("-moz-transform")}}
Pseudo elements are completely broken. e.g.
{{template.cssxref("::first-letter")}}, {{template.cssxref("::selection")}}
Comment 19•15 years ago
|
||
The JSInherits template is still broken, e.g.
{{template.JSInherits("Object", "Methods", "__defineGetter__", "__defineSetter__", "hasOwnProperty", "isPrototypeOf", "__lookupGetter__", "__lookupSetter__", "__noSuchMethod__", "propertyIsEnumerable", "unwatch", "watch")}}
Links of methods that start "__" like __defineGetter__ are broken.
Reporter | ||
Comment 20•15 years ago
|
||
This is still broken, see f.e. https://developer.mozilla.org/en/Mercurial
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 21•15 years ago
|
||
Yeah, looks like there are other broken preferences still needing to be fixed. I assumed there would be, but will need folks to keep letting me know about problems like these. Once we get it all sorted out, I'm going to snapshot all the prefs so we can restore them correctly again if this ever happens again.
Comment 22•15 years ago
|
||
I need to kick this over to IT; the second server isn't picking up these changes, despite being restarted yesterday. One server sees all the new configuration changes I've done, the other does not.
Severity: normal → major
Comment 23•15 years ago
|
||
Mossop, re comment #20, I've fixed the config problem you mentioned - it now works fine on the server whose prefs are up to date. Need IT to figure out why the other server isn't picking up changes so we can get them picked up. Thanks!
Assignee | ||
Comment 24•15 years ago
|
||
Is this still a problem?
Assignee | ||
Comment 25•15 years ago
|
||
Please reopen if this is still an issue.
Status: REOPENED → RESOLVED
Closed: 15 years ago → 15 years ago
Resolution: --- → INCOMPLETE
Updated•10 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•