Problem/Motivation
Some configs have tabs, some don't and only accessible via list controller dropdowns. Some of the tabs may be exposed through contextual links but they are not. This may also serve as entry points for those who do not have edit access to the original data otherwise.
Proposed resolution
- Make translate tab names include type names so it is appropriate for contextual links even when merged with other types of links (eg. menu + block); also useful for when the tab shows up among other things, eg. account settings, content type settings, etc.
- Make the translate tab show up as a contextual link as well.
Remaining tasks
Add tests proving contextual links worked.
User interface changes
Each config entity will have a translate tab, no inconsistencies. Translate operations show up as contextual links finally:
API changes
None.
Comment | File | Size | Author |
---|---|---|---|
#4 | local-task.patch | 6.29 KB | Gábor Hojtsy |
#2 | local-task.patch | 4.28 KB | Gábor Hojtsy |
#1 | local-task.patch | 3.12 KB | Gábor Hojtsy |
Welcome to d8mi.localhost | d8mi.localhost 2013-09-10 16-36-25.jpg | 75.54 KB | Gábor Hojtsy | |
Welcome to d8mi.localhost | d8mi.localhost 2013-09-10 16-35-56.jpg | 40.56 KB | Gábor Hojtsy |
Comments
Comment #1
Gábor HojtsyPatch.
Comment #2
Gábor HojtsyWith proof of concept test.
Comment #4
Gábor HojtsyWith proper assertions for contextual links :) Committing this one. I think having these contextual links is a great motivation for having the tabs in the first place :)
Comment #5
Gábor HojtsyComment #6
Gábor HojtsyCommitted :)