Last modified: 2006-09-19 06:14:02 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 7336 - Uploaded image not updated
Uploaded image not updated
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2006-09-15 09:37 UTC by Petr Matas
Modified: 2006-09-19 06:14 UTC (History)
0 users

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


Description Petr Matas 2006-09-15 09:37:24 UTC
Yesterday I uploaded a new (5KB) version of the image (see link below). The previous 
version size was 9KB. The image summary page shows the new size (5KB) of the image, but 
the displayed image itself is the old (9KB) version. This looks to me that there is some 
bug in the saving process, as the database is in an inconsistent state.

Affected image:

Petr Matas
Comment 1 Rotem Liss 2006-09-15 14:28:42 UTC
Force-reload the image page (Shift+Ctrl+R in Mozilla, Ctrl+F5 in Internet Explorer).
Comment 2 Brion Vibber 2006-09-15 14:29:25 UTC
The squids should be purged properly on upload.
Comment 3 Brion Vibber 2006-09-15 19:23:27 UTC
There was a network problem which broke the multicast updates;
this has been resolved, so page and image updates _should_ update
correctly now.

You may still have to refresh in your browser, though.
Comment 4 Petr Matas 2006-09-19 06:14:02 UTC
And please tell me, did it require any intervention? Would waiting a few days
for the update to propagate through the system be enough?

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