Topic on Project:Support desk

I recently upgraded to 1.30.0, and for some reason, I'm having this strange thumbnail issue. Upon uploading an image, the thumbnails work like they should, but when a new version of that image gets uploaded, the thumbnails don't regenerate, leaving the original image as the thumbnailed version. The thumbnails are correctly sized on the pages to match the new image, but if the ratio of the image dimensions are different, the image gets stretched.

Here's an example of what I mean: https://www.pidgi.net/wiki/File:Promotional_image_EN_-_Poke_Ball_Plus.jpg

Any idea on how to fix this?

Maybe there was a temporary failure on the server when uploading, that didn't purge the old thumbnails when uploading the new file. You may need to remove the thumb folder of that file and let MediaWiki recreate them again.

Looks like your wiki is not configured to generate thumnails dinamically. You'll need to manually recreate the thumbnails again by making a null edit on pages that use the image after deleting the thumbnails, or use Manual:Thumb.php from your browser to generate specific thumbnails.

Update to this - it ended up being an incompatibility with an old version of Semantic MediaWiki.

These sorts of symptoms can also be a job queue failure (Upon change in image dimension, all pages using the image have to be purged, so the width/height attributes in html are changed for the new aspect ratio of the image)

Have the same issue on Mediawiki 1.31.0 and with Semantic Mediawiki 2.5.6

Thumbnails are just not updated, even by using the call with thumb.php the old image remains.

Did you try to clear your browser's cache after uploading? It works for me.

If the call with thumb.php does also not return the correct image, it's not a browser cache problem.

You haven't checked if it's a job queue problem, though, so this is not helpful at all.

Also seeing this issue.

• MW 1.31.0
• PHP 7.0.31
• SMW 2.5.6

Upgrading to SMW 2.5.8 did not solve this problem for me. The unreleased 3.0.0-dev version appears to solve the problem.

Oh, and there are no jobs in the queue. Uploading a new version of the file does not appear to generate any jobs relevant to this, though, when using SMW 2.5.x (where the problem exists) or 3.0 (where the problem does not exist). The only jobs it generates are:

             job_id: 266
            job_cmd: recentChangesUpdate
      job_namespace: -1
          job_title: RecentChanges
      job_timestamp: 20180914232556
         job_params: a:2:{s:4:"type";s:11:"cacheUpdate";s:9:"requestId";s:27:"W5xDhLfkyYu4BqqyUK@9ZgAAAAY";}
         job_random: 1398893290
       job_attempts: 0
          job_token:
job_token_timestamp: NULL
           job_sha1: t0ui7t0cg0b9prp29q7plzaevrijg70

             job_id: 267
            job_cmd: htmlCacheUpdate
      job_namespace: 6
          job_title: Test_2.png
      job_timestamp: 20180914232644
         job_params: a:8:{s:5:"table";s:10:"imagelinks";s:9:"recursive";b:1;s:13:"rootJobIsSelf";b:1;s:16:"rootJobSignature";s:40:"038e9b9a072b7f6f5674aad13cdf91173c8ed6a9";s:16:"rootJobTimestamp";s:14:"20180914232644";s:11:"causeAction";s:11:"file-upload";s:10:"causeAgent";s:7:"unknown";s:9:"requestId";s:27:"W5xDtI2DZquTPPQ4ptCRIAAAAAc";}
         job_random: 820376045
       job_attempts: 0
          job_token:
job_token_timestamp: NULL
           job_sha1: qfv3vr0fn28whie2788uiy50x4a5mdy

On the failing server (SMW 2.5.x) I only saw the "recentChangesUpdate", not the "htmlCacheUpdate". On the working server (SMW 3.0) I saw both. In either case the jobs get cleared so quick I could have missed something, though.

The problem with a failing extension is that the htmlCacheUpdate is never inserted.

Jobs are inserted very late in the request pipeline, and an error in an extension can be totally unnoticed (because all the HTML has been sent to the browser). A debug log may have caught the problem.

I'm having this problem too. Did anyone ever get a solution to this? - User:Revansx

Have you tried disabling all extensions and reuploading the image?

No. I guess you're saying that the problem is likely some extension that is causing an error late in the request line and might not get noticed except for such a simple problem. And that turning all extensions off and one-by-one turning them on is the only way to identify the problematic extension. Is that right? gah! .. i really need a dev system, lol

Yes, that's what I'm suggesting.

I just had the same problem. But after reading this I thought I'd try using a different browser, and the new thumb appeared there like it should. That totally sounds like a cache problem with my usual browser. (I'm not going to test this yet because I'm have unfinished work in the Sandbox and don't want to flush the cache yet.)