[SOLVED] Image resize does not work anymore. Caching issue?

Bugs Solved Bugs
1

I have…

  • [X] Checked the logs and have uploaded a log file and provided a link because I found something suspicious there. Please do not post the log file in the topic because very often something important is missing.

I’m submitting a…

  • [ ] Regression (a behavior that stopped working in a new release)
  • [X] Bug report
  • [ ] Performance issue
  • [ ] Documentation issue or request

Current behavior

Image resize does not work.
Here’s an example: https://cloud.squidex.io/api/assets/e71eaf24-961c-4ad9-ab56-d60cf19093c3?width=1400. The width parameter as no effect. The original image with its full width is shown.

However, if I change the width to 1401, it works again. Seems to be caching issue…

Expected behavior

https://cloud.squidex.io/api/assets/e71eaf24-961c-4ad9-ab56-d60cf19093c3?width=1400 should resize to 1400px.

Minimal reproduction of the problem

Open this link: https://cloud.squidex.io/api/assets/e71eaf24-961c-4ad9-ab56-d60cf19093c3?width=1400. It’s not 1400px wide.

Environment

  • [ ] Self hosted with docker
  • [ ] Self hosted with IIS
  • [ ] Self hosted with other version
  • [X] Cloud version

Version: current version

Browser:

  • [X] Chrome (desktop)
  • [X] Chrome (Android)
  • [X] Chrome (iOS)
  • [X] Firefox
  • [X] Safari (desktop)
  • [X] Safari (iOS)
  • [X] IE
  • [X] Edge
2

Thank you, there is no caching involved, which makes it strange.

3

I have no idea how this can happen but I will introduce a “force” parameter to always resize, even if there is a resized version available. This should not be used by default.

It is not deployed yet, but I have removed your resized version.

4

I think I have found the reason: It is actually this bug: [SOLVED] Image Resizer not work

You have probably resized the image before but the resizer was not working properly when only the width or the height was specified and then you always got the buggy version.

5

I don’t know the implementation details behind the asset optimizer, or if it’s related to this issue, but I can tell for sure it was working around 2 months ago :thinking:.

What do you mean exactly by “even if there is a resized version available”?

Thanks for the help :slight_smile:

6

The asset optimizer stores the resized version and if there is a such a file it just delivers that, instead of resizing it again. But if the file is buggy it will always deliver the buggy version. The force query parameter disables the check and always makes the resize.

7

Is there a way to purge all resized versions instead of adding the “force” param on every query?

8

No, sorry, there is nothing like that at the moment.

9