[5.x]: Entries Field UX Issue
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 3.6k
- Forks
- 705
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 134
Description
What happened?
Description
This is more of a UX issue than a bug so my apologies if this is the wrong place to raise this.
There is a slight annoyance with the 'Entries' field, in that it does not maintain the 'ticked' state when searching or switching to a different source. This has lead to a few bug reports to us where users are saying their changes are not being saved.
I have attached a quick video showing the issue:
https://github.com/craftcms/cms/assets/142855/c4adf86b-142a-4336-bf69-f4eaf5b05b97
Hopefully the above video is clear enough, if not happy to provide more information!
Craft CMS version
5.0.5
PHP version
No response
Operating system and version
No response
Database type and version
No response
Image driver and version
No response
Installed plugins and versions
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No implementation files or tests are named. Reproduce the behavior shown in the attached video by using the Entries field, then trace the field's search and source-switching behavior. Done means selected entries remain visibly ticked after searching or changing source, and the selection is saved correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100