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.If #2358923: Config translation module cannot deal with different base path ever gets fixed, we need to update the Configurable Help module to use it.
Currently, the Edit route is the base route for translations, which makes the tabs on configurable help topics be Edit / View / Translate. If that issue gets fixed, it should be possible to reverse that and make the View route be the base route, so the tab order can be View / Edit / Translate, which is more standard for other things like Nodes and etc.
| Comment | File | Size | Author |
|---|---|---|---|
| #11 | 2372585-11.patch | 373 bytes | andypost |
Comments
Comment #1
jhodgdonComment #2
jhodgdonwrong status
Comment #3
jhodgdonComment #4
andypostThis no longer depends on issue in IS
Comment #5
andypostProper patch, sorry
Tested it and "Translate" tab still not displayed also Delete have no tab to Edit
Comment #6
andypostPossible workaround is move edit/delete & locking to entity canonical patch. I will try to explore that
Comment #7
jhodgdonTo get the Translate tab to display, you need to have all 4 multilingual modules enabled. Well, probably you don't need Content Translation, just Config Translation and the Language and Locale modules. Plus you have to have more than one language installed.
There's also a Translate test in the Functional subdirectory if you didn't see that.
Anyway, I think the other Core issue is still relevant probably. I don't think you can have anything but Edit be the base route for purposes of translations... but see if you can get it working.
And yeah we should add a Delete tab. Nodes have one. Maybe we should make that a separate issue though?
#2921014: Add a Delete tab to View/Edit/Translate
Comment #8
jhodgdonWhat I recall from before is that if you don't make the config_help.links.task.yml have the edit form be the base route for the tabs, then the Translate tab doesn't work -- this is added by the Config Translate module and it assumes that the edit form is the base route for the tabs. That's half of #2358923: Config translation module cannot deal with different base path. There was also another problem, not relevant to this issue exactly.
So I don't think you can just switch it in the links.task.yml file.
Comment #9
jhodgdonComment #10
jhodgdonJust a question... I noticed on #2921014: Add a Delete tab to View/Edit/Translate that a weight was added to the Delete tab. Is it possible to use weights to make the route that is technically the base for tabs not be on the left side? I haven't tried it but noting it here since it is maybe possible and would sidestep the Core problem about Edit not always being the basis for translation route groups.
Comment #11
andypostNice idea, that makes order valid, "Edit" gets 0 as defailt
Comment #12
jhodgdonWoot! Excellent. Thanks for the patch. Committed to Sandbox and about to actually roll a new Core patch with the last 5 fixes. I can barely keep up with you today. :)