Last modified: 2011-09-20 23:10:17 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 T30448, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 28448 - imageinfo object malformed if image has already been uploaded
imageinfo object malformed if image has already been uploaded
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
UploadWizard (Other open bugs)
unspecified
All All
: Normal major (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-04-07 01:07 UTC by Ryan Kaldari
Modified: 2011-09-20 23:10 UTC (History)
2 users (show)

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


Attachments

Description Ryan Kaldari 2011-04-07 01:07:48 UTC
If an image has already been fully uploaded, and you try to stash it again, it will get created with a malformed imageinfo object attached to it. Specifically, all the properties in the imageinfo object will be embedded within an array instead of being directly in the object. This causes things like
var prop = _this.imageinfo[ propName ];
to fail, and thus the thumbnails won't link to anything.
Comment 1 Neil Kandalgaonkar 2011-04-07 01:10:23 UTC
Almost certainly related to bug 28230 but will need to fix that first to be sure.
Comment 2 Ryan Kaldari 2011-04-07 01:13:32 UTC
This affects the imageinfo object for the image itself as well as for all of
the thumbnails.
Comment 3 Ryan Kaldari 2011-04-07 01:14:42 UTC
I think you meant bug 28320.
Comment 4 Bugmeister Bot 2011-08-19 19:12:38 UTC
Unassigning default assignments. http://article.gmane.org/gmane.science.linguistics.wikipedia.technical/54734
Comment 5 Neil Kandalgaonkar 2011-09-20 23:10:17 UTC
Can't reproduce this any more -- looks like it is fixed, or replaced with entirely new bugs at least.

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


Navigation
Links