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.
How can I navigate to the translation overview?
As administrator I have the permission to see the overview. The module is installed and enabled.
But I'm unable to figure out how to access it.
Comment | File | Size | Author |
---|---|---|---|
#13 | translation_overview-is_manager-1529938-13-D7.patch | 528 bytes | kyberman |
#11 | add_extra_parameter_to_access_callback_to_capture_the_default_access_argument.patch | 935 bytes | dazz |
Comments
Comment #1
whitingx CreditAttribution: whitingx commentedI'm having the same issue, I can see the module is working as when I go to the translate tab on an item of content the translation_overview icon and the priority radio buttons are available.
It seems as if the link to the main translation_overview page is missing from where it used to be located under
configuration > content authoring
Any assistance with this would be greatly appreciated.
Thanks.
Comment #2
sonuku CreditAttribution: sonuku commentedLooks like its living at:
admin/content/translation-overview-manage
and
admin/content/translation-overview-assignments
Could be a work in progress?
Subscribing.
Comment #3
Ritch CreditAttribution: Ritch commentedSubscribing.
Comment #4
redben CreditAttribution: redben commentedThe overview page is accessible under Config : admin/config/content/translation-overview-manage
Comment #5
rondev CreditAttribution: rondev commentedIt seems that there is something broken in 7.x-2.x-dev.
admin/config/content/translation-overview-manage
fallback toadmin/config/content
There is no "Translation overview" in "Content authoring"
Comment #6
shadysamir CreditAttribution: shadysamir commentedSame for me with latest dev.
admin/content/translation-overview-manage
works but there is no link anywhere in config.Comment #7
rondev CreditAttribution: rondev commentedWhat I find strange is that on my test, which database is a copy of my online site, I just saw that I can access admin/config/content/translation-overview-manage and see it on Configuration page. The differences between test and online sites are:
With two sites that are so similar with two different behavior, I may find where is the issue. But help is appreciated to find too.
Edit: On the test working site, the Translation overview version is 7.x-2.0-beta1
Comment #8
rondev CreditAttribution: rondev commentedLine 12 of translation_overview.module:
The page is no more in
admin/config/content/translation-overview-manage
but in
admin/content/translation-overview-manage
It doesn't appear in the configuration page but it should in content page and it doesn't either.
Change come frome here: #1158294-8: Patch that resolves all the issues with 7.x
Edit: It appears on menu management for content /admin/structure/menu/manage/management but not on the content page.
Comment #9
rondev CreditAttribution: rondev commentedCategory change was not wanted for the moment.
Comment #10
FriOne CreditAttribution: FriOne commentedAccess argument apply default access arguments that is 'access content overview'. Module must use another access callback for this page, where will be set default language string.
Workaround:
Comment #11
dazz CreditAttribution: dazz at iO commentedPatch to fix FriOne's discovery
Comment #13
kybermanI have to reopen this issue, because there are still problems with permissions in current dev.
Function translation_overview_is_manager is used in translation_overview.pages.inc for testing $lang_code permissions, so we don't need to change its arguments. But the main problem is that the callback of "admin/content/translation-overview-manage" page gets string "access content overview" in $lang_code (I don't know why - maybe inherited from "admin/content"), so it always returns FALSE for no-admin.
I created simple dirty patch for that - user also needs the "access content overview" permission assigned.
Could you please test it? Thanks.
Comment #14
Jej CreditAttribution: Jej as a volunteer commented#13 solved for me. Thank you kyberman.
J.
Comment #15
stefan.r CreditAttribution: stefan.r commentedThis solves the immediate issue, but not the underlying problem, so setting back to NW as $lang_code should not be equal to "access content overview"
Comment #16
fox mulder CreditAttribution: fox mulder commented#13 solves the problem, thanks kyberman
Comment #17
kyberman