Problem/Motivation
By design, when content moderation and content translation are enabled, translation forms include only translatable fields. See https://www.drupal.org/project/drupal/issues/2878556.
ETUF attempts to make all forms the same, with all fields available. The functionality listed above conflicts with this goal.
Steps to reproduce
- Install content moderation and content translation
- Setup a content type with translatable and non-translatable fields
- Create content of the type created above. See the translation page doesn't include the non-translatable field.
Proposed resolution
I've provided an in-progress solution that gives ETUF an option to replace translation node edit forms with the original form. The form is translated with the interface language, as usual. So long as the moderation is synchronized, the issue fixed in https://www.drupal.org/project/drupal/issues/2878556 shouldn't be an issue.
I've seen a variety of solutions for this issue. None have worked for me. These are a few.
- https://www.drupal.org/project/drupal/issues/2955321#comment-12541730
- https://www.drupal.org/project/drupal/issues/2955321#comment-13257405
Remaining tasks
This is an early version of this solution. It needs to be tested.
User interface changes
A checkbox was added to the content translation configuration page, next to other ETUF options, with the label "Replace node edit"
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | 3559833_enity_translation_unified_form__replace_node_form.patch | 15.86 KB | bzaher |
Issue fork entity_translation_unified_form-3559833
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
bzaher commentedComment #4
joseph.olstadWow great initiative Barry!
Creating a merge request now.
Comment #6
joseph.olstad@bzaher , from the merge request, newest version of your patch.
Comment #7
joseph.olstadTesting this now
Comment #8
joseph.olstadWow, great, works well in my testing.
My only comment is, I'm wondering if we should just enable this by default rather than add a new configuration for
"Replace node edit" however maybe the approach is good, people can intentionally enable this functionality. I think it's good to merge!
Comment #9
joseph.olstadGoing ahead with the merge, let's cut a release!
Comment #11
joseph.olstadComment #13
joseph.olstadhttps://www.drupal.org/project/entity_translation_unified_form/releases/...
I'll announce this now in LinkedIn, major improvement!
Thank you very much @bzaher!
Comment #14
bzaher commentedThanks for taking it the rest of the way @joseph.olstad. I considered "enable this by default" too, but my concern is that since this issue's been present for 8 years, this might interfere with the workarounds that people have found.
Comment #15
joseph.olstadhttps://www.drupal.org/project/entity_translation_unified_form/releases/...
Comment #18
bzaher commented