Last modified: 2012-03-01 00:32:39 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 T36796, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 34796 - Special:Version is not always up to date
Special:Version is not always up to date
Status: RESOLVED INVALID
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
1.19
All All
: High major (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-02-29 16:11 UTC by Marcin Cieślak
Modified: 2012-03-01 00:32 UTC (History)
2 users (show)

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


Attachments

Description Marcin Cieślak 2012-02-29 16:11:37 UTC
Recently I was waiting for r112570 to be deployed on https://pl.wikipedia.org/.
I was logged-in and all the time the previous version number (I believe it was
r112130) was displayed there, BUT I then realized by visiting
[[Special:CheckUserLog]] that the problem that r112570 solved (described in
r112562) was fixed - the missing link reappeared; which means the change must
have had been deployed. 

Having reliable [[Special:Version]] is very important for troubleshooting
especially with major upgrades when things are moving fast.

Can we do something so that cache for this page is purged on deploy?
Comment 1 Rob Halsell 2012-02-29 18:54:55 UTC
Marcin,

Logged in users do not get served cached pages in mediawiki.  So if you were logged in, you were getting generated content for all calls, no caching.

I would advise that the issue of the wrong items showing and appearing cached would possibly on your browser.

I have also been advised that special pages are not cached in the typical fashion of the normal pages.  I did not look into this, since the above logged in statement makes this not a mediawiki issue.
Comment 2 Bawolff (Brian Wolff) 2012-03-01 00:13:21 UTC
Are you sure you were looking at the right place? If just CheckUser was updated, core MediaWiki might stay at r112130, well CheckUser extension would have the updated version number.
Comment 3 Sam Reed (reedy) 2012-03-01 00:28:40 UTC
(In reply to comment #2)
> Are you sure you were looking at the right place? If just CheckUser was
> updated, core MediaWiki might stay at r112130, well CheckUser extension would
> have the updated version number.

Only if the full dir has been sync'd... If it's just 1 file, it won't
Comment 4 Marcin Cieślak 2012-03-01 00:32:39 UTC
That's confusing... Thanks.

Just seen it with 

00:03 <+logmsgbot> !log tstarling synchronized php-1.19/extensions/Collection/Collection.body.php  'r112745'

Now I get it. Not that I like it :)

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


Navigation
Links