Nuke's i18n files cause problem for later extension's i18n
Closed, InvalidPublic
Actions

Assigned To

None

Authored By

	MarkAHershberger
	May 8 2013, 1:52 AM

Description

MW wasn't picking up my i18n files until I commented out the following line in Nuke.php

$wgExtensionMessagesFiles['NukeAlias'] = $dir . 'Nuke.alias.php';

Looking at the file, I can't see right away why this is so.

Version: unspecified
Severity: normal
See Also:
https://bugzilla.wikimedia.org/show_bug.cgi?id=44294

• bzimport raised the priority of this task from to Needs Triage.Nov 22 2014, 1:19 AM

• bzimport set Reference to bz48235.

• bzimport added a subscriber: Unknown Object (MLST).

Are you sure this just didn't trigger cache invalidation?

(In reply to comment #1)

Are you sure this just didn't trigger cache invalidation?

Related to the other bug about possibly wrong timestamps in the files?

ugh... you're right. It triggered cache invalidation. I thought I was doing that with some of the maint scripts I was running.