1232921 - https://wiki.mozilla.org/Security/Roadmap is broken

Status: RESOLVED WORKSFORME

(Websites :: wiki.mozilla.org, defect)

Description

[Paul Theriault [:pauljt] (no longer reading bugmail)]

The security roadmap page is broken (https://wiki.mozilla.org/Security/Roadmap). I see the following error:

Unexpected non-MediaWiki exception encountered, of type "RuntimeException"

Comment 1

[Spike, UTC+1, spike on Matrix]

I get the same error message - ff 43.0.1
Searching for page in wiki does not find anything either - not sure how to help - sorry
Spike

Comment 2

[CaptainCalliope]

Finding a solution to this sort of problem is beyond my personal capability, but I may be able to help narrow down the problem space.

I did a search and found this report of a similar error: https://www.mediawiki.org/wiki/Topic:Rz3tnus9g3zgt1gh

We do have Semantic MediaWiki installed and use it extensively.

Do you have any sense how long this page has had this problem? I'm wondering if it might have happened after the last upgrade (which I believe was some months ago) or if someone added something to the page more recently that that could have caused this error by calling an extension like Semantic MediaWiki.

Comment 3

[Paul Theriault [:pauljt] (no longer reading bugmail)]

Not really - I posted when I noticed it. But archive.org had the correct page in June, and broken page on the 4th of sept 2015. 

https://web.archive.org/web/20150604042638/https://wiki.mozilla.org/Security/Roadmap

https://web.archive.org/web/20150904033829/https://wiki.mozilla.org/Security/Roadmap

Comment 4

[Paul Theriault [:pauljt] (no longer reading bugmail)]

Oh ok you can get to the edit page, and all it contains is

#REDIRECT [[SecurityEngineering/Roadmap]]

So maybe that is broken. Is that the correct way to do a redirect?

Comment 5

[Paul Theriault [:pauljt] (no longer reading bugmail)]

Oh but https://wiki.mozilla.org/SecurityEngineering/Roadmap is also broken :(

Comment 6

[Paul Theriault [:pauljt] (no longer reading bugmail)]

I tried blanking the page, but that didnt help. The content hasnt been changed since jan2014 so its not an urgent issue apparently but I wonder what else is affected.

Comment 7

[Loic]

It appears fixed now, I can't reproduce the issue.