risingisland I looked at this in the code of phpThumb. First of all, maybe try updating phpThumb if possible, on my dev server (Evo 3.1.5) the file assets/snippets/phpThumb/snippet.phpthumb.php has at line 105
$fNameSuf = str_replace("ad", "at", $fNameSuf);
which would exactly solve this issue, replacing ad
with at
. If this does not help, then in the same file at line 100 we have
$fNameSuf = '-' .
(isset($params['w']) ? $params['w'] : '') . 'x' . (isset($params['h']) ? $params['h'] : '') . '-' .
substr(md5(serialize($params) . $fmtime), 0, 3) .
'.' . $params['f'];
which generates exactly the 600x360-ad4
in the new file name. The ad4
part is created using
substr(md5(serialize($params) . $fmtime), 0, 3)
so it is MD5 hash of phpThumb parameters and, if filemtime='1'
then also the time of creation of the image is used (see line 93 of that file).
So a potential solution is the following:
- Add
filemtime='1'
to the phpThumb call, so it would look like
[[phpthumb? &input=`[+Main-Image+]` &options=`w=600,h=350,zc=C` &filemtime=`1`]]
This only forces phpThumb to check whether the image wasn't replaced by a newer version of itself (and so it is usually useful anyways). If you have already done this, then:
- Download the original image (the one you have inside the TV), open it in any image editor, export it and re-upload the exported version. You only want to force the image to be overwritten, so that the file creation time changes, and so also the MD5 hash changes.