Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[4.5.0-beta.2]: Cannot edit freshly uploaded images with required custom fields #13566

Closed
wsydney76 opened this issue Aug 16, 2023 · 2 comments
Closed
Assignees

Comments

@wsydney76
Copy link

wsydney76 commented Aug 16, 2023

What happened?

I (Klara) have inherited the job to keep track of open issues for this (mostly dead) account, this issue probably refers to #11569 / #12125

Description

Setup:

  • Two sites, en/de
  • An asset volume with a required custom field altText, translatable by language.
  • A section with a required custom field featuredImage, set to Validate related assets

Steps to reproduce

  1. Upload an image.
  2. Edit image (via Assets menu), fill in an alt text and save.
  3. 'Couldn't save asset'

image

  1. However, switching to site 'Deutsch' and saving gives the same error (probably because there is no such thing as a provisional draft for assets and the edit from step 2 was never saved?)

Creating an entry, uploading an image directly to the assets field and editing/saving it via slideout, also gives the 'Couldn't save asset' error, but without a hint that the error comes from an other site, and leaves this:

image

I assume something similar (no helpful error message) would happen when editing a related entry with errors on other sites via slideout. (#12488 would also be helpful...)

Expected behavior

Be able to edit new images.

Actual behavior

Not yet...

Craft CMS version

Craft Solo 4.5.0-beta.2

PHP version

8.1.21

Operating system and version

Linux 5.15.90.1-microsoft-standard-WSL2

Database type and version

MariaDB 10.4.30

Image driver and version

Imagick 3.7.0 (ImageMagick 6.9.11-60)

Installed plugins and versions

None

@i-just
Copy link
Contributor

i-just commented Aug 17, 2023

Hi, thanks for reporting! I have raised a PR to adjust this.

@brandonkelly
Copy link
Member

This has been fixed in Craft 4.5.0 (stable), released today.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants