[5.x]: Enhancement: Title links in cards in an Entry field should open the Edit flyout (like Matrix/ckeditor fields)
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
5.7.10 When you add a Title or Entry field chip to a card displayed in an Entry field, clicking the Title or Entry Field chip (related Entry) does not open the Edit flyout, instead it dumps you back to the root Entries menu.
Steps to reproduce
- Add 'Title' and/or 'Entry field' to a card.
- Add an Entry to an Entry field and set it to display as a card.
- Click the Title hyperlink in the card.
- Note the Edit flyout navigation is lost.
Expected behavior
Hyperlinks in cards to Entries in an Entry field should open the Edit flyout.
Actual behavior
Hyperlinks in cards to Entries in an Entry field open the root Entries edit menu.
It would be even better if chip Entry field links in a card opened the linked Entry and then a second flyout for the entry in the chip itself.
In reference to enhancements in: https://github.com/craftcms/cms/discussions/16185
Craft CMS version
5.7.10
PHP version
8.2
Operating system and version
No response
Database type and version
No response
Image driver and version
No response
Installed plugins and versions
-ckeditor
-preparseField
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
Reproduce this in Craft CMS 5.7.10 by creating an Entry field card with a Title or Entry field chip, then compare its navigation with Matrix and CKEditor fields. Done means clicking the card link preserves the Edit flyout instead of returning to the root Entries menu; the linked discussion may clarify the additional nested-flyout behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100