Last modified: 2012-04-12 13:55:57 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 T30679, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 28679 - When $wgLanguageCode set to zh file cache do not work.
When $wgLanguageCode set to zh file cache do not work.
Status: RESOLVED WORKSFORME
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
1.16.x
All Linux
: Normal major (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-04-24 08:37 UTC by zoglun
Modified: 2012-04-12 13:55 UTC (History)
2 users (show)

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


Attachments

Description zoglun 2011-04-24 08:37:32 UTC
When I set $wgLanguageCode = "zh"; .

file cache just do not work. No cache file creat in /cache directory.

But when $wgLanguageCode set to 'zh-cn'; 'zh-hk'; 'zh-mo'; 'zh-my'; 'zh-sg'; 'zh-tw'

Thre are cache file creat in /cache directory and 

<!-- Cached/compressed 20110424071040 --> 

write in html code.
Comment 1 Mark A. Hershberger 2011-05-01 21:21:24 UTC
Just tested and saw the cache files.
Comment 2 zoglun 2011-05-02 02:10:28 UTC
OK SIR, I install a whole new mediawiki 1.16.4 in hawkhost web host. And again, when 

$wgLanguageCode = "zh";

 no filecache generate in /cache.

But when set to zh-hant; zh-hans; en.

there is it, it just work fine.


I also let my friend do this test, same ressult.


my site url:moegirl.org(default set to zh)

friend site url:acfunwiki.org(default set to zh-cn)
Comment 3 Bawolff (Brian Wolff) 2011-05-02 07:13:27 UTC
Note: I can reproduce on 1.16, However the issue appears to be fixed on trunk (1.18) as well as 1.17.

1.17 will be hopefully released really soon. Once that's released, try that version and see if it fixes it. If after updating to 1.17 the issue is still present please re-open this bug.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links