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.Currenlty in core we have two competing UIs to create content translations. This can be confusing for early testers. I'd suggest that we hide the Content Translation module from the module list until we are able to fully replace it and provide an upgrade path.
| Comment | File | Size | Author |
|---|---|---|---|
| #11 | translation-hide-1834250-11.patch | 3.3 KB | plach |
| #1 | translation-hide-1834250-1.patch | 329 bytes | plach |
Comments
Comment #1
plachComment #2
plachHere is an example explaining why we should do this: #1831636-6: "Translation is not supported if language is always one of: Not specified, Not applicable, Multiple" reword to: "...." and #1831636-11: "Translation is not supported if language is always one of: Not specified, Not applicable, Multiple" reword to: "...." .
Comment #3
YesCT CreditAttribution: YesCT commentedThis is a great idea and will help when we do usability testing because we won't have people picking that one. This happened a few times at the sprint. Hiding it will also make the new contributor experience better for D8MI.
Comment #3.0
YesCT CreditAttribution: YesCT commentedUpdated issue summary.
Comment #4
YesCT CreditAttribution: YesCT commented@plach I opened #1834276: establish what needs to be done to remove Content Translation from core and then remove it
Comment #5
tstoecklerFor Profile in D7, we actually only marked it hidden for people who didn't already have the module enabled. I think that would make sense here as well.
Comment #6
plachThe aim is full removal if we are able to provide an upgrade path, are you suggesting to leave the module visible if a tester has enabled it?
Comment #7
tstoecklerUnlike Profile in D7 I do think we will be able to remove translation.module completely in the end, but the idea is that in case we don't, for whichever reasons, we wouldn't break the upgrade path for people who have that module enabled. That said, I'm not married to the idea (hence not marking "needs work") just wanted to point out that that is what we did before.
Comment #8
tstoecklerEdit: Duplicate post.
Comment #10
Gábor HojtsyLooks like Drupal\system\Tests\Module\DependencyTest depends on translation module :D Otherwise I pretty much agree with @tstoeckler, if we hide the module we would ideally hide it conditionally with the same condition as D7 profile module, but if that is too much work, we should continue the key work towards removing it instead and just hide it for now.
(Also fixing tag).
Comment #11
plachHere is a patch hiding the Translation module only if it is not already installed. It's modelled after the D7 code hiding the Profile module with some adjustments.
Comment #12
plach:(
Comment #13
Gábor HojtsyLooks good to me. As said, hoping to review the module before the D8 release.
Comment #14
catchCommitted/pushed to 8.x. We could leave this until the last minute instead as we did with Profile, but then it'd be 1. critical 2. not help early testers, so doing it now works well.
Comment #15.0
(not verified) CreditAttribution: commentedUpdated issue summary.
Comment #16
plach