Page MenuHomePhabricator

i18n cache corruption for enwiki message (possibly others?) meant code displayed instead of labels
Closed, DuplicatePublic

Description

Earlier today, the toolbar in VisualEditor stopped displaying "Cite" on the new citation tool, and instead started displaying "<visualeditor-toolbar-cite-label>".

For me, it displayed correctly until I changed languages to qqx to check something else; when I went back, it was broken. For James F, it was displaying correctly until he logged out.


Version: wmf-deployment
Severity: normal
See Also:
https://bugzilla.wikimedia.org/show_bug.cgi?id=66543

Details

Reference
bz65230

Event Timeline

bzimport raised the priority of this task from to High.Nov 22 2014, 3:22 AM
bzimport added a project: Deployments.
bzimport set Reference to bz65230.
bzimport added a subscriber: Unknown Object (MLST).

As a note, it was fixed by me making a null edit to [[MediaWiki:visualeditor-toolbar-cite-label]]. Apparently the same breakage (in pl rather than en) was experienced on plwiki earlier as well.

Only in VisualEditor strings, or also other places been seen?

(In reply to Andre Klapper from comment #2)

Only in VisualEditor strings, or also other places been seen?

So far I've only seen it for this particular VE-related message, but the fun thing with deployment bugs is you never know…

I tried to reproduce the issue with:

eaction=edit&uselang=en
eaction=edit&uselang=qqx
eaction=edit

The Cite label in the toolbar was back to normal.

Could it be that whenever that new Cite function got added the l10n cache did not get regenerated? Without a way to reproduce it there is not much we can do unfortunately.

(In reply to Antoine "hashar" Musso from comment #4)

I tried to reproduce the issue with:

eaction=edit&uselang=en
eaction=edit&uselang=qqx
eaction=edit

The Cite label in the toolbar was back to normal.

Indeed; a null edit to the message page brought it back into the l10n cache.

Could it be that whenever that new Cite function got added the l10n cache
did not get regenerated? Without a way to reproduce it there is not much
we can do unfortunately.

No. It was added in 1.23wmf20. It is very unlikely that the l10n cache having suddenly broken on Monday night was caused by a deploy two months ago. :-)