Last modified: 2014-02-19 10:03:36 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 6044 - Enable Wikitext for MediaWiki:Thumbnail_error
Enable Wikitext for MediaWiki:Thumbnail_error
Status: REOPENED
Product: MediaWiki
Classification: Unclassified
Internationalization (Other open bugs)
unspecified
All All
: Normal normal with 4 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
http://en.wikipedia.org/wiki/MediaWik...
: i18n, patch, patch-need-review, testme
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-05-22 04:29 UTC by bdk
Modified: 2014-02-19 10:03 UTC (History)
6 users (show)

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


Attachments
1-line-patch (468 bytes, patch)
2007-03-01 20:52 UTC, Raimond Spekking
Details

Description bdk 2006-05-22 04:29:45 UTC
Please enable wikitext (or even html) for [[MediaWiki:Thumbnail error]] 
(that shows up as "Error creating thumbnail" by default, followed by a 
closer, often "cryptic" hint about the specific cause).

It would be very useful and reasonable IMO to be able to link this message
to a page like "Help:Purge", [[Wikipedia:Bypass your cache]] or close, because 
in most of the cases the only thing a user has to do is simply purging the cache. 

On some days such errors appear numerously on the Wikimedia projects, 
and usually nearly all the inexperienced users just remove affected images 
from articles, what is quiet annoying in general (baseless loss of images).

Thanks in advance :-)
Comment 1 Raimond Spekking 2007-03-01 20:52:34 UTC
Created attachment 3285 [details]
1-line-patch

A simple 1-line-patch, but I cannot test this special error case :-(
Comment 2 Chad H. 2007-12-03 21:52:05 UTC
Not sure if this still is relevant. Checking MediaTransformOutput (class MediaTransformError, to be exact), shows the use of wfMsgReal. Beyond that I don't know.
Comment 3 Siebrand Mazeland 2008-08-11 22:36:34 UTC
There are 15 hits in core for "thumbnail_error". There is 1 wfMsg usage left: /var/www/w/includes/Linker.php:                 $s .= htmlspecialchars( wfMsg( 'thumbnail_error', '' ) );

The rest appears to either be able to display wiki text, or HTML.
Comment 4 Bergi 2012-02-09 20:01:48 UTC
Currently not working on http://de.wikipedia.org/wiki/Datei:Wasserhose_1884.png. The message source shows up 2 times in a <div class="MediaTransformError" style="[custom rectangle]">.
Comment 5 Nemo 2013-07-27 20:46:16 UTC
(In reply to comment #4)
> Currently not working on
> http://de.wikipedia.org/wiki/Datei:Wasserhose_1884.png. The message source
> shows up 2 times in a <div class="MediaTransformError" style="[custom
> rectangle]">.

Ehm, we need another example, now PNGs up tp 140 MB or so are correctly thumbed thanks to VipsScaler.
Comment 6 Bawolff (Brian Wolff) 2013-09-29 01:00:24 UTC
These errors mostly aren't user visible (on Wikimedia wikis. On non-wikimedia wikis they are quite visible). The type of users who knows how to actually view the file itself, probably already knows how to get to the help page.
-----

Only possible objection I could maybe think of, is if we don't want the thumbnail servers spending time parsing things, but I can't imagine people are going to be putting too complicated of things in these messages.

I don't think comment 1's patch would work. You'd want to change line 396 of MediaTransformOutput.php from

$this->htmlMsg = wfMessage( $msg )->rawParams( $htmlArgs )->escaped();

to

$this->htmlMsg = wfMessage( $msg )->rawParams( $htmlArgs )->parsed();

probably (untested)

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


Navigation
Links