For Firefox there is WebDeveloper extension
https://addons.mozilla.org/ru/firefox/addon/web-developer/
which has menu to disable browser caching. In IE8 / IE9 there is menu to
disable caching when you run debugger via F12.
That's true for me, while developing but if I change the WikiEditor
Brion asked:
So where's your code being loaded from? Site or use JS pages? Some
literal JS files output from an extension? Something else?
From a physical JS file (e.g., myfile.js) handed to ResourceLoader by my
extension:
$wgResourceModules[vp.wiki.editor.edittools] = array(
'scripts' =
(Reposted from mediawiki-l due to zero responses.)
I've been adding custom tools to the WikiEditor toolbar (MW 1.17.0 version) and
am running into difficulty with browser caching.
When I do something simple, such as adding a button or changing text in a
dialog, the change doesn't take effect
Is it possible for the special:search logic to take us to [[category:foo]] if
[[foo]] doesnt exist and [[category:foo]] does?
This should be an easy wiki extension to write, using the hook
SpecialSearchGo($title, $term). Just check for the existence of the article
and the category, and modify
This is a question about an infrastructural detail of ResourceLoader and how it
interacts with Internet Explorer. (It's my first post to wikitech-l, so
apologies if it's the wrong forum.)
Our MediaWiki 1.17.0 site recently installed a bunch of extensions that use
ResourceLoader, such as
101 - 105 of 105 matches
Mail list logo