The #1188388: Entity translation UI in core issue was committed with a considerable number of follow-ups planned. The main reasons for this were reducing the initial patch size to something not too painful to review and ensuring we had an MVP in before feature freeze to be able to refine it afterwards.
This metaissue has the goal to track all the most important ET improvements: a new issue queue component has been created but we have some issues that don't belong to it.
Usability improvements
#2290101: UI telling you a field is shared across languages is way too subtle
#1832836: Discuss how to view original translation from translation form
#1498724: Introduce a #multilingual key (or similar) for form element
#1498880: Theme language switcher for seven theme
#1807902: add hint to field collapsed global settings: GLOBAL SETTINGS: Number of values (1), Field translation (disabled)
#1807908: Autofill revision log with text that describes action like: German translation added or Spanish translation edited
#1807830: Improve UI by adding hint to add translation: source language collapsed field set
API improvements and code clean-up
#2155787: Introduce more flexible access control for content translation operations
Additional features
#1807322: Filter comments taking into account the current content language
Translation UI issues
- Full list of usability issues.
Comments
Comment #0.0
plachUpdated issue summary.
Comment #0.1
plachUpdated issue summary.
Comment #0.2
plachUpdated issue summary.
Comment #1
plachFeel free to add new issues to the summary and/or announce them below, but let's try to limit the summary to important issues or ones that do not belong to the ET queue for easier tracking.
Comment #1.0
plachUpdated issue summary.
Comment #1.1
plachUpdated issue summary.
Comment #2
Gábor HojtsyFound this bug as well: #1849316: Undefined function _field_ui_bundle_admin_path when no field is translatable
Comment #3
YesCT CreditAttribution: YesCT commentedMinor: #1876122: Missing new line near enable/disable translation on global field settings tab
Comment #3.0
YesCT CreditAttribution: YesCT commentedAdded http://drupal.org/node/1848904
Comment #4
YesCT CreditAttribution: YesCT commenteddoes #1896268: Add Views integration for translation_entity fit here?
Comment #5
plachTotally :)
Comment #5.0
plachUpdated issue summary.
Comment #6
YesCT CreditAttribution: YesCT commentedadded #1914800: Dropbutton width is smaller than longest item to the issue summary.
(for example: "no translatable fields")
Comment #6.0
YesCT CreditAttribution: YesCT commentedUpdated issue summary added issue for dropbutton cutting off long text: no translatable fields
Comment #6.1
plachUpdated issue summary.
Comment #6.2
plachUpdated issue summary.
Comment #6.3
plachUpdated issue summary.
Comment #7
YesCT CreditAttribution: YesCT commentedadding these I found going through my tracker
#1807902: add hint to field collapsed global settings: GLOBAL SETTINGS: Number of values (1), Field translation (disabled)
#1807908: Autofill revision log with text that describes action like: German translation added or Spanish translation edited
#1807830: Improve UI by adding hint to add translation: source language collapsed field set
they might have to be re-evaluated to see if they are now duplicates or wont fix, etc
Comment #7.0
YesCT CreditAttribution: YesCT commentedUpdated issue summary.
Comment #7.1
YesCT CreditAttribution: YesCT commentedUpdated issue summary, added older et ui follow-ups
Comment #7.2
plachUpdated issue summary
Comment #7.3
plachUpdated issue summary.
Comment #8
YesCT CreditAttribution: YesCT commented#1938384: "Undefined property" error only after adding translations to existing content. was found by @craychee I'm pretty sure we came across that before, and now we have reliable steps to reproduce it.
Comment #8.0
YesCT CreditAttribution: YesCT commentedI was not sure if http://drupal.org/node/1938384 was a ui improvement or api.. it's really a bug. added the issue though.
Comment #8.1
plachUpdated issue summary.
Comment #8.2
plachUpdated issue summary.
Comment #8.3
YesCT CreditAttribution: YesCT commentedadded ones from 1977784
Comment #8.4
plachUpdated issue summary
Comment #8.5
YesCT CreditAttribution: YesCT commentedadd idea about renaming config page title
Comment #8.6
plachUpdated issue summary.
Comment #8.7
plachUpdated issue summary.
Comment #9
Gábor HojtsyComment #9.0
Gábor HojtsyUpdated issue summary.
Comment #9.1
plachUpdated issue summary.
Comment #9.2
plachUpdated issue summary.
Comment #9.3
plachUpdated issue summary.
Comment #9.4
plachUpdated issue summary.
Comment #9.5
plachUpdated issue summary.
Comment #10
plachComment #11
plachComment #12
plachComment #13
plachComment #14
plachComment #15
plachComment #16
plachComment #17
plachComment #18
plachComment #19
plachComment #21
Anonymous (not verified) CreditAttribution: Anonymous for The Linux Foundation commentedComment #22
mikeryan@Ryan Weal - not clear why this was tagged "Migrate critical"? It's not actionable in itself, and has no open migration children. Better I think would be to tag any individual children of #2208401: [META] Remaining multilingual migration paths that we feel are critical and aren't already tagged.
Comment #28
andypostComment #29
andypostComment #36
quietone CreditAttribution: quietone at PreviousNext commentedBecause of bugsmash I've come across this page a couple of times. This time I decided to remove the fixed issues from the Issue summary. to make it easier to see what is left to done. Changed the entity translation UI issue link to search for issue in the translation components and tagged 'usability' or 'needs usability review'.
Comment #38
jasonawantI came across #3222997: Allow disable non translatable fields on translation forms, which sounds like could be considered among these others.
Comment #39
jasonawantMaybe another related issue, #3266293: Media items translate items in modal?
Comment #40
jasonawantAnother possible related issue, #3221720: Improve workflow for translating Media entities with the Media Library