Last modified: 2011-02-19 19:12:29 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 27352 - Wikimedia deployment needs /w/resources directory symlinked or overridden for debug mode
Wikimedia deployment needs /w/resources directory symlinked or overridden for...
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
: shell
Depends on:
Blocks: 27339
  Show dependency treegraph
Reported: 2011-02-12 01:51 UTC by Brion Vibber
Modified: 2011-02-19 19:12 UTC (History)
2 users (show)

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


Description Brion Vibber 2011-02-12 01:51:05 UTC
When using ResourceLoader's debug mode, .js files are fetched directly from their home location in the resources directory.

On Wikimedia deployments this would be in /w/resources; like the old extensions dir this'll need to be either symlinked in so the files can be exposed, or else overridden with a reference to

[Note that at the moment debug mode is additionally broken on due to bug 27321 / bug 27322. With the fix, it'll try actually loading the /w/resources files and will then fail due to them being missing.]
Comment 1 Derk-Jan Hartman 2011-02-19 18:55:35 UTC
This seems fixed now, can the ticket be closed ?
Comment 2 Krinkle 2011-02-19 19:12:29 UTC
I noticed this too while debugging on test2, told Roan about it on IRC and it was fixed earlier this week.

Hadn't noticed this bug, but yeah, it's fixed.
It was a new directory in 1.17 so it wasn't linked yet.

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