Skip to content

Conversation

@jasonvarga
Copy link
Member

@jasonvarga jasonvarga commented Jan 23, 2026

To reduce confusion around the Image button being enabled but not visible in the UI, we started requiring that an asset container be selected whenever the Image button is enabled (#12238).

However, because the Image button is enabled by default, this meant that creating a Bard field forced you to select an asset container before you could save the field.

This PR adjusts the default behavior of the buttons and container config fields based on how many asset containers you have configured.

No containers:

  • Button bar excludes the image button
  • Container field is blank. But, no validation would kick in because the image button isnt selected.

One container:

More than one container:

  • Button bar has the image button selected
  • Container field defaults to blank. This causes the same validation that currently happens, forcing you to pick a container.

Replaces #13607 - We'd prefer to keep the image button enabled by default where possible.
Replaces #13609 - Giving the asset container fieldtype a default value means it can never be null.

This follows the approach we already take for the container config field inside the assets fieldtype.

@jasonvarga jasonvarga merged commit 23327b5 into master Jan 23, 2026
13 checks passed
@jasonvarga jasonvarga deleted the bard-image-button-2 branch January 23, 2026 20:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants