Trying out Translation for the first time, and was surprised to find... nothing.
A peek at the source code told me that there should be translation tabs on the node page, but they are not there.
A few quick dsm-s showed me that when the cache is cleared (devel/cache/clear/all),
$info['translation']['translation']['base path'] is not present, so the tabs don't get added.
I see the comment above that line telling me:
// Menu is rebuilt while determining base paths so we might not have them
// available yet.
but I'm not sure what I'm supposed to do about that.
Any ideas? Cheers!
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | 1012054.patch | 915 bytes | bojanz |
Comments
Comment #1
bojanz commentedRC3 install. Updated it to the latest D7 dev, but still nothing.
I nailed the $path to 'node/%node', but found that the tabs still weren't there because translation_node_tab_access() returns FALSE, and it returns false because one of it's conditions is checking for variable_get('language_content_type_' . $type, 0) which is also FALSE (I see no option to enable when editing content types).
So, I'm officially confused :)
Comment #2
sunMight be another scenario of #996236: drupal_flush_all_caches() does not clear entity info cache
Comment #3
bojanz commentedThat was my thought as well, but the access code still seems just wrong. Seems to me that instead of translation_node_tab_access() the default should be _translation_node_tab_access()
Edit: with the access code fixed, the menu() problem doesn't matter, the Translate tabs show either way (with or without patch above).
Comment #4
plach@bojanz:
You should find multilingual options under the Publishing options tab.
Comment #5
bojanz commentedFound it, and now it works despite the menu strangeness.
So the main problem was between the keyboard and the chair.
Guess a line in the README would help :)
Thank you for your help!
Comment #6
plachComment #7
bojanz commentedHere's an attempted README patch. I'm not very good at this, but it's a start.
Also, here's Views support: #1006176: Add support for field based translation :)
Comment #8
Guillo commentedI'm sorry... I know the info on how to solve this problem is in this thread, but I'm afraid it all went a little bit over my head.
I have two problems, the first being the same as the OP's: I don't see the Translation options when going in as a user. Nada, 0, nothing at all. Would you mind spelling out the solution for someone who isn't really a programmer??
(I do English to Spanish Translation, and we are trying to separate that section of the main site into a completely new one... but I write content, I'm only on programmer duty cause my partner is on holidays, and I'm afraid I'm in over my head!!)
Thank you! Any other suggestions for the new site are welcome!
Comment #9
bojanz commentedEnable translation for the desired entity types at admin/config/regional/translation. Nodes should be enabled by default, I think.
If translating nodes, you need to set Multilingual support to "Enabled, with content translation" in settings for each content type.
(from my readme patch above)
Comment #10
sunRelated, but not the same: #1030038: Initial setup lacks UX
Comment #11
plachMoving to the Entity Translation queue. Read #902760: Change module name so it can work with Core translation for details.
Comment #12
plachText needs to be updated after #11.
Comment #13
sunMarking as duplicate of #1030038: Initial setup lacks UX