Last modified: 2005-10-28 00:12:22 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 T5806, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 3806 - Limitation of thumbnail generation for huge images should not cause broken links
Limitation of thumbnail generation for huge images should not cause broken links
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
File management (Other open bugs)
1.6.x
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
http://cs.wikipedia.org/w/index.php?t...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-10-27 09:30 UTC by Mormegil
Modified: 2005-10-28 00:12 UTC (History)
0 users

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


Attachments

Description Mormegil 2005-10-27 09:30:27 UTC
MediaWiki refuses to generate a thumbnail for huge images (to enforce an upper
limit for memory requirements). The current behavior in such case is that
[[Image:Foo.png|thumb|Foo!]] will appear as a red broken link to Special:Upload,
which is quite unintuitive.

Even more strange, there is a difference between
[[Image:Foo.png|thumb|200px|Foo!]] and
[[Image:Foo.png|right|200px|Foo!]]. While the thumbnail is not generated in both
case, the latter displays correctly, using just a scaled img linking to the
original full-sized image and letting the browser to do all work.
I believe both should behave in the same way (and display the image).
Comment 1 Brion Vibber 2005-10-28 00:12:22 UTC
Fixed on CVS HEAD and live; thumb will now fall back gracefully to client-side scaling 
as the other cases do. For super-giant images this may be bad for your web browser, 
but at least it's off our servers. ;)

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


Navigation
Links