Page MenuHomePhabricator

Raw '#coordinates:' shown on articles due to Elastic/CirrusSearch disabling
Closed, ResolvedPublic


Suddenly all the #coordinates are shown in the wiki pages instead of being hidden as usual.
for example take a look at:

Most likely the #iferror that we use on #coordinates doesn't work anymore.

This problem is spread in the whole site!

Version: unspecified
Severity: major
See Also:



Event Timeline

bzimport raised the priority of this task from to Unbreak Now!.Nov 22 2014, 3:53 AM
bzimport set Reference to bz72559.
bzimport added a subscriber: Unknown Object (MLST).

PS when I say suddenly means that 2/3 hours ago everything was fine.

Oh I see. CirrusSearch has some problems for the last hour (discussed in #wikimedia-operations on Freenode IRC), as also mentioned in

So this likely will be fixed again once the Search issues are sorted out.

Yeah, they had to turn off the use of CirrusSearch, which turned off GeoData. Which means this appears all over articles.

It's back on, just need to fix the articles affected.

It should just be a matter of purging any articles that were affected. Elasticsearch is back so GeoData is back and Cirrus is back in the places it was before.

celebration.women wrote:

This problem seems to have reappeared?
I just loaded the page for "Chemical Heritage Foundation" on English Wikipedia
and saw the following displayed as text:

Did you try purging the page? It shows fine for me.

celebration.women wrote:

Okay, editing and resaving to purge the page seems to have cleared it. Thanks.

I've reopened because I've the problem has come back again.
Just noticed in Wikivoyage (e.g. and also in Wikipedia (e.g.

Please take a look at it.

Gone again? I can't see it on the Wikivoyage article you linked (after purging).

Yes, same problem as four days ago - it broke and now it works again.
Operations is/was investigating.

Now we have modified in it:voy our main template to avoid layout issues. However, when GeoData is disable the special mobile page Nearby doesn't work and there's no backup plan for that.

Raimond: good idea to separate the two components as suggested in bug 72814.

Change 170358 had a related patch set uploaded by MaxSem:
Don't disable GeoData completely if CirrusSearch is having problems

Change 170358 merged by jenkins-bot:
Don't disable GeoData completely if CirrusSearch is having problems

GeoData should now remain enabled no matter what's going on with CS.

  • Bug 72814 has been marked as a duplicate of this bug. ***