Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Problem/Motivation
Found while manually testing #2161801: Update hook_help for Config translation module
When there is only one language, translate pages exist, but do not give a hint that translation cannot happen until another language is added.
Proposed resolution
Add a message, and link to the language admin, when there is only one language to add enable
Remaining tasks
- discuss if this is really needed, or is wont fix.
User interface changes
Yes.
Content translation, before
Configuration translation, before (for comparison)
Note that configuration translation is different, because even with only the site default language, config text can be edited on the translate page. (For example, english can be translated.)
API changes
No.
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | screenshot-2286367-8-3.png | 64.62 KB | Thew |
| #8 | screenshot-2286367-8-2.png | 41.78 KB | Thew |
| #8 | screenshot-2286367-8-1.png | 69.71 KB | Thew |
| #3 | no-translatable-fields.png | 131.28 KB | YesCT |
| #2 | content_translation_with_second_language.png | 111.31 KB | YesCT |
Comments
Comment #1
YesCT CreditAttribution: YesCT commentedComment #2
YesCT CreditAttribution: YesCT commentedThis is what content translation looks like with more than one language
Comment #3
YesCT CreditAttribution: YesCT commentedhere is an example, where we give a hint and the button links to the place to add the translatable fields.
(this is the case where there is an additional language, and translation is enabled on the content type, but not on any of the fields for the content type [which can be done by editing the content type])
Comment #4
yoroy CreditAttribution: yoroy commented"No translatable fields" is status info. The label on the button should focus more on the action, not on conveying current status.
"Add translatable fields" For the button?
Maybe the "Not translated" status could say something like "No translatable fields available" or "No translatable fields defined".
If so, then the button text could maybe be shortened to "Add fields"
Comment #7
yoroy CreditAttribution: yoroy commentedComment #8
Thew CreditAttribution: Thew at Google Code-In commentedWhen there is only one language, I can't see the translate tab.
But in configuration translation, I can see the warning to have at least 2 languages.
However, I don't understand what does no translatable fields mean. Since, I can't disable all fields. It gives me error.
Comment #9
denutkarsh CreditAttribution: denutkarsh at Google Code-In commented@Thew You are right, i think this issue is not present in 8.2.x . I have checked it and was unable to reproduce the issue. When there is only one language, the "translate" tab is not shown and when i tried to access it from the url, it denied me the access.
Comment #10
denutkarsh CreditAttribution: denutkarsh at Google Code-In commented