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:

Welcome to d8mi.localhost | d8mi.localhost 2013-09-10 16-35-34.jpg

Welcome to d8mi.localhost | d8mi.localhost 2013-09-10 16-35-56.jpg

Welcome to d8mi.localhost | d8mi.localhost 2013-09-10 16-36-25.jpg

API changes

None.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Gábor Hojtsy’s picture

Status: Active » Needs review
FileSize
3.12 KB

Patch.

Gábor Hojtsy’s picture

FileSize
4.28 KB

With proof of concept test.

Status: Needs review » Needs work

The last submitted patch, local-task.patch, failed testing.

Gábor Hojtsy’s picture

Status: Needs work » Fixed
FileSize
6.29 KB

With 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 :)

Gábor Hojtsy’s picture

Status: Fixed » Needs review
Gábor Hojtsy’s picture

Status: Needs review » Fixed

Committed :)

Automatically closed -- issue fixed for 2 weeks with no activity.