Anyone aware of why the Refresh link is disabled in REL1_35?
<li id="ca-purge" class="is-disabled"><a href="/sfb1368/wiki/index.php?title=Test&action=purge">Refresh</a></li>
&action=purge seems to work fine.
Issue related to SMW which was fixed with the 3.2.1 release.
Anyone aware of why the Refresh link is disabled in REL1_35?
<li id="ca-purge" class="is-disabled"><a href="/sfb1368/wiki/index.php?title=Test&action=purge">Refresh</a></li>
&action=purge seems to work fine.
SMW uses a similar implementation of it's own. It also fails for MW 1.35 and later. Probably a "goodie" provided during some refactoring.
Refresh, that is SMW not the Purge extension. Purge displays, Purge and your code shows Refresh.
Indeed, this is correct. I am now totally confused if Purge works for MW 1.35 or not. No clue. However I do know that SMW 3.2.1 brought the fix for SMW.
It does work, the question is should we separate Purge by changing it's #id from ca-purge to ca-purge-ext. As I said SMW steps on Purge by overwriting it. SMW takes over the link name, changes from Purge to Refresh. SMW attaches new JS, overwriting Purge's JS.
I do not really see a point in installing Purge together with SMW. Never done that. However making these extension not "clash" in a way will probably still be a good idea.
I would agree, but some may not know they conflict or take them as one and the same if they are new to SMW. I'll create an issue to discuss this further on GitHub. Thanks!
I agree. I have 1.35.2 and there is no tab with purge on it using minervaneue (desktop view).
&action=purge works anyway because this functionality is already in this release - ie this worked using no purge extension installed. Logged in users get a confirmation page and then the page is cleared from the cache.
HOWEVER, what I wanted this for was so that the page would be immediately recached (the refresh functionality) such that immediately after an edit the first anonymous user to request the page wouldn't have to wait for the scripts to run.
Is there a fix?
Edit: Can confirm it works on 1.35.5, I clearly shouldn't test when tired lol, was my own mistake that it wasn't working.