Closed (fixed)
Project:
Drupal core
Version:
10.3.x-dev
Component:
config_translation.module
Priority:
Minor
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
13 May 2015 at 22:02 UTC
Updated:
21 Nov 2024 at 09:02 UTC
Jump to comment: Most recent, Most recent file


Comments
Comment #1
mikemadison commentedNote that this behavior is inconsistent with the content translations, where I can add a translated node without changing anything and it simply clones the English text into the "Spanish" version.
The view translation component seems to work the same way as the menu, so depending on what is found / decided here, we may need to dup this issue for Views.
Comment #4
pameeela commentedGiven this is quite an old issue and was against an early version of D8, I wasn't surprised to find that I can't reproduce this. It seems to have changed quite a bit in fact, as the 'Add' option no longer appears at all.
If there is still a similar issue please feel free to re-open with updated steps.
Comment #5
pameeela commentedJust realised how to reproduce this. Will update steps later.
Comment #6
pameeela commentedUpdated title and IS but bumping this to minor because if you haven't made any changes there is really no risk here. Agree the message could be more clear though.
Comment #7
mohit.bansal623 commentedCreated a patch for this issue, I have updated the message when there is no changes in the configuration while adding.
Comment #10
mohit_aghera commented- Adding simple test cases for the same.
- The failures in the current patch seem a bit unclear to me as they are passing on local.
Note: Tuvan language lablel is throwing cspell errors on local, so I've added language title in local dictionary.
Comment #11
abhijith s commentedApplied patch #10 and it worked fine.
Before patch:

After patch:

RTBC +1
Comment #12
guilhermevp commentedPatch works as intended. Adding image as evidence.
Moving to RTBC.
Comment #15
catchCommitted/pushed to 9.2.x and cherry-picked to 9.1.x, thanks!
Comment #17
erwangel commentedSorry to reopen this but I find this wording very confusing:
To add a translation, you must modify the configuration. Which configuration ? I had to check all kind of settings/configurations, in structure (content type, content type field), in settings (region and languages, content language and translation, configuration translation), in module settings (I faced this problem while translating meta settings with metatag module) etc., before I realize that I just had to change something in a field of the present form!So I suggest to change this message to
To add a translation, you must modify at least a field on this form.