-
Notifications
You must be signed in to change notification settings - Fork 641
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
HUD modal only showing single source and not pre-selecting on first trigger #3227
Comments
Are the sections that aren’t visible enabled for the current site? |
No, they are only enabled in their individual sites. For example, we have 5 sites:
And 5 sections:
Those sections are only enabled in their respective sites. And then, we have a Case Studies (entries) field with the following settings:
|
Hm, ok. In that case it seems like it is mostly behaving as expected.
I don’t think that just because only a single source ends up being visible, that the field should actually remove the sidebar (like it would on a field that is only configured for a single source) – because Craft doesn’t know that the author is expecting a single source. For all it knows, the field’s name & instruction text are written assuming that multiple sources would be visible, and it won’t be clear which source is selected if the sidebar isn’t shown. So the only awkward thing here is that the one source doesn’t get selected automatically. |
👍 that makes sense. If the single source could be pre-selected, I think it would help reduce the confusion that we've seen some clients have. |
Description
We have an Entries field that is related to multiple sections (across multiple sites), and also managed on a per site basis. When I click to add an entry the first time, I see the following:
The left sidebar seems unnecessary, and the section isn't pre-selected. If I click the section in the left sidebar, leave that entry, and then come back to it later in the session, clicking add entry now pre-selects the section:
Steps to reproduce
Additional info
The text was updated successfully, but these errors were encountered: