You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using an asset field on an entry to generate some page CSS for background images. I've started to use SVG background images and would like to use the asset focal point feature to control the background-position in the entry template.
Steps to reproduce
Upload an SVG as an asset
Click the preview button
Click the enable focal point button
Drag and save the focal point
Save the asset
Expected behavior
The asset is saved and a thumbnail of the asset is generated that either ignores the focal point or does as the source TODOmentions.
Actual behavior
An error is thrown and a message is written to the log.
[web.ERROR] [craft\errors\ImageTransformException] Failed to generate transform with id of #
Craft CMS version
4.13.0
PHP version
8.3.8
Operating system and version
Linux 4.14.345-262.561.amzn2.x86_64
Database type and version
MySQL 8.0.35
Image driver and version
Imagick 3.7.0 (ImageMagick 6.9.13-11)
Installed plugins and versions
Amazon S3 2.2.1
CKEditor 3.10.0
The text was updated successfully, but these errors were encountered:
What happened?
Description
I am using an asset field on an entry to generate some page CSS for background images. I've started to use SVG background images and would like to use the asset focal point feature to control the
background-position
in the entry template.Steps to reproduce
Expected behavior
The asset is saved and a thumbnail of the asset is generated that either ignores the focal point or does as the source
TODO
mentions.Actual behavior
An error is thrown and a message is written to the log.
Craft CMS version
4.13.0
PHP version
8.3.8
Operating system and version
Linux 4.14.345-262.561.amzn2.x86_64
Database type and version
MySQL 8.0.35
Image driver and version
Imagick 3.7.0 (ImageMagick 6.9.13-11)
Installed plugins and versions
The text was updated successfully, but these errors were encountered: