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.x]: Conditional fields on Asset field layout are not appearing/hiding automatically #12365

Closed
Stalex89 opened this issue Nov 23, 2022 · 3 comments

Comments

@Stalex89
Copy link

What happened?

Description

The default behaviour (at least on Entries) is when you change the condition for conditional field, it will toggle visibility for conditional fields. However that doesn't happen automatically if conditional fields are set in Asset layout. You have to manually resave asset to trigger visibility of conditional fields in control panel

Steps to reproduce

  1. Create Asset volume with conditional fields in asset layout
  2. Add a new asset to the volume
  3. Try to toggle condition field

Expected behavior

Conditional fields should show/hide automatically when condition field is changed

Actual behavior

Nothing happens when condition field is changed, you have to manually resave asset to trigger visibility of conditional fields

Craft CMS version

Craft CMS 4.3.3

PHP version

8.0.25

Operating system and version

Darwin 21.6.0

Database type and version

MySQL 8.0.31

Image driver and version

GD 8.0.25

Installed plugins and versions

@i-just
Copy link
Contributor

i-just commented Nov 23, 2022

Hi, thanks for reaching out. That's a duplicate of #12348 and it's currently working as expected. Elements that don't support autosaving drafts (like assets, globals, users) will only show/hide conditional fields after saving your changes.

@i-just i-just closed this as completed Nov 23, 2022
@i-just i-just self-assigned this Nov 23, 2022
@Stalex89
Copy link
Author

Stalex89 commented Nov 23, 2022

@i-just Aah ok, thank you for your fast response, sorry for the duplicate post

@i-just
Copy link
Contributor

i-just commented Nov 23, 2022

Not a problem :)

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

2 participants