Last modified: 2013-07-08 13:00: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 T51078, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 49078 - Extensions folder in non-standard path
Extensions folder in non-standard path
Status: RESOLVED INVALID
Product: MediaWiki extensions
Classification: Unclassified
UniversalLanguageSelector (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2013-06-03 10:03 UTC by Santhosh Thottingal
Modified: 2013-07-08 13:00 UTC (History)
14 users (show)

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

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

Description Santhosh Thottingal 2013-06-03 10:03:26 UTC 
Universal Language Selector extension tries to read its i18n json files from the extensios folder in same domain for IE8 to overcome a bug( see Bug 45958 and Bug 41489)

For the extensions folder,  {wgScriptPath}/extensions is failing in http://en.wikipedia.beta.wmflabs.org/

For example:
http://en.wikipedia.beta.wmflabs.org/w/extensions/UniversalLanguageSelector/i18n/en.json is 403
while http://www.mediawiki.org/w/extensions/UniversalLanguageSelector/i18n/en.json is OK

My assumption is beta instance should have same configuration of production. I guess extensions are in some other location in beta instance compared to mediawiki.org
Comment 1 Krinkle 2013-06-03 20:57:17 UTC 
Using "{wgScriptPath}/extensions" is not supported. Use $wgExtensionAssetsPath instead.

Does that work?

Note that $wgExtensionAssetsPath can (though not always) be on another domain. So you can't rely on CORS.

As I recall I recommended ULS to no longer load raw JSON files in production.
Comment 2 Antoine "hashar" Musso (WMF) 2013-07-08 12:35:06 UTC 
Moving bug from beta to ULS
Comment 3 Santhosh Thottingal 2013-07-08 13:00:43 UTC 
This bug is no longer valid since ULS does not read raw json files.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links