This is not an image that can be manipulated - 4.0.0-beta3

[cookie10codes]

Hi Andrew 👋🏼

Describe the bug

Each image we try to upload into our field results in a This is not an image that can be manipulated. My image is big enough, so that's not the issue. I can't seem to find any error in the logs. What I do see is this log, which maybe causing this problem?

2022-06-01 13:55:32 [web.INFO] [nystudio107\imageoptimize\services\OptimizedImages::shouldCreateVariants] Array
(
)
 {"memory":11876624} 

As this issue #334 describes, the ./craft image-optimize/optimize/create solves the issue but we can't expect the author asking to manually run the command each time they upload an image.

To reproduce

Steps to reproduce the behaviour:

1. Go to a page
2. Upload an image
3. Double click the image (or check the image optmise field in Assets)
4. Showing the message This is not an image that can be manipulated

Screenshots

Versions

• Plugin version: 4.0.0-beta3
• Craft version: Craft Pro 4.0.3

Thanks for looking into this 👍🏼

[michtio]

@khalwat any news on this front? As it's excruciatingly annoying, every time an image uploads to run a console command to make it working.

Makes it unworkable at the moment for our content editors. Thank you for having a look!

[curtismorte]

We're experiencing the same issue.

However, our context is slightly different. We always get the message "This is not an image that can be manipulated" for all optimized images fields associated with a volume when we first upload an asset. However, as our queue is running and completing tasks, those messages then get removed and we see the optimized images themselves.

Note that all of our optimized image fields use auto for their image format specification.

We don't use the native poor man's queue with Craft, and instead use a service unit (systemd) to always have processes running that watches the queue (we have 4 of them per server).

[khalwat]

I believe this is due to the auto setting, which will be addressed shortly. There must have been an underlying change in how image transforms are handled in Craft 4

[curtismorte]

@khalwat yeah I noticed a big difference in the code bases for transforms between Craft v3 and Craft v4 when tracking down the issue for #329 .

[khalwat]

Addressed in: 3598ec1

You can try it now by setting your semver in your composer.json to look like this:

    "nystudio107/craft-image-optimize": "dev-develop-v4 as 4.0.0-beta.4”,

Then do a composer clear-cache && composer update