After installing the Translation Management module and following all instructions, I experienced this problem when submitting a translation job to a "local translator." From the Translation Dashboard, I select the node that I want to be translated and then the langauge and translator for it to go to. In this case I selected a translator that I added as a "local translator" from the selection of Drupal users. As expected, a notification is sent to that user with a link to www.sitename.com/translate/1. However when he clicks on the link, he only get's an "Access Denied" error. (he was logged in)
As I understand this module, there is no need to assign roles to the translators - the module will create a custom role. However, when I look at the drupal users and their roles, all I see is a "⋅" (bullet point) followed by nothing. I would expect to see "translator" or something following that.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | Screen shot 2011-07-13 at 10.21.58 PM.png | 42.59 KB | kevinhurley8179 |
Comments
Comment #1
kevinhurley8179 commentedbump.
Still having the same problem. Anyone else?
Comment #2
brucepearson commentedThe module should usually create a translator role.
I suggest you create a new translator role and then set the permission to "icl_translate module :
can do translation jobs".
Comment #3
kevinhurley8179 commentedThanks Bruce.
That is exactly what I did. I created the role "translator" and assigned it to the person. However, when I do so, it removes the pseudo roll created by translation management and I have to go back in and make them a translator again in the "manage translators" interface. So once I do that, the translator is able to click on the direct link to edit the content, however if they try to view their translation jobs (www.sitename.com/translator), All they receive is a warning message "translator is not a translator. Configure translator"
It seems that the module generated role is not giving the correct permissions.
What can i do?
Comment #4
grasmash commentedI am having this same issue-- the translator module does not create a role when installed.
I've created a 'local_translator' role and given permissions (to that role) to do and view translation jobs. But this still results in an 'access denied' error when a user with this role tries to view translation jobs.
More interesting details:
-When using the translation management interface to 'add translator' for local translator with username my_translator, it simply adds a new, blank role for the user. So, instance, if I look at a list of my_translator's roles on the user admin page, I see two bullet points listed: one blank, one 'local_translator'
-As mentioned in the previous post, assigning local_translator role to user my_translator will remove my_translator as a translator in the translation management interface
Comment #5
grasmash commentedWell I'm not sure what caused the problem, but I did find a fix.
After uninstalling, reinstalling, rolling back to old versions, etc, I finally decided that I'd simply try installing the module on a fresh Drupal install. That worked. So, I compared the databases on the working instance and the broken instance. Here's what I found.
1) Problem: On the broken instance, translation_management failed to create the "ICanLocalize translator" role. Solution: Create the role manually.
2) Problem: Since the module failed to create the role, it also failed to set the correct value for the "icl_translate_role" variable. This is intended to correspond to the RID of the "ICanLocalize translator" role. Solution: On my site, the manually created "ICanLocalize translator" had an RID of 10. So, I entered "i:10;" as the value of the "icl_translate_role" variable in my site database.
This fixed the problem, but I'm still not sure why the module is failing to create the role.
Comment #5.0
grasmash commentedbump