Last modified: 2013-05-08 19:12:43 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T50235, the corresponding Phabricator task for complete and up-to-date bug report information.

Bug 48235 - Nuke's i18n files cause problem for later extension's i18n


Summary:	Nuke's i18n files cause problem for later extension's i18n

Status:	RESOLVED INVALID

Product:	MediaWiki extensions
Classification:	Unclassified
Component:	Nuke (Other open bugs)
Version:	unspecified
Hardware:	All All

Importance:	Unprioritized normal (vote)
Target Milestone:	---
Assigned To:	Nobody - You can work on this!

URL:
Whiteboard:
Keywords:	i18n

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-05-08 01:52 UTC by Mark A. Hershberger
Modified:	2013-05-08 19:12 UTC (History)
CC List:	2 users (show)

See Also:	44294
Web browser:	---
Mobile Platform:	---
Assignee Huggle Beta Tester:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Mark A. Hershberger 2013-05-08 01:52:39 UTC

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.

Comment 1 Niklas Laxström 2013-05-08 05:55:35 UTC

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

Comment 2 Nemo 2013-05-08 06:29:48 UTC

(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?

Comment 3 Mark A. Hershberger 2013-05-08 19:12:43 UTC

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

Wikimedia Bugzilla is closed!

Search

Personal tools

Navigation

Links