Closed (works as designed)
Project:
Internationalization
Version:
7.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
30 Aug 2011 at 16:17 UTC
Updated:
2 Nov 2020 at 12:16 UTC
Jump to comment: Most recent
Comments
Comment #1
kilrizzy commentedAlso getting authorization error when going to "node/1/translate" which is what would work for d6. Permissions are set for admin
Comment #2
jose reyero commentedLooks like its working. Are you using any potentially conflicting module like 'entity translation' ?
Comment #3
kilrizzy commentedNot using entity translation. I have Locale, Language Icons, and most of the I18n. Don't see anything that could be an issue
Comment #4
jose reyero commentedCannot reproduce. And btw, we are using the very same permission checking the core content translation module is using.
So unless someone else has this issue or you can provide steps to reproduce (on a clean install)...
Comment #5
datarazor commentedsame issue, brand new website, localization module enabled, two languages defined, everything works but I have no translate tab at the top of my translation-enabled nodes. What information do you need to be able to reproduce this problem?
Comment #6
datarazor commentedsame issue, brand new website, localization module enabled, two languages defined, everything works but I have no translate tab at the top of my translation-enabled nodes. What information do you need to be able to reproduce this problem?
Comment #7
jose reyero commentedTry disabling i18n. You should see a translate tab if you have Content Translation (core) enabled and the content type properly configured.
Now, if you can tell me the tab is there and goes away by enabling any i18n module, reopen the issue. If not, it must be something else.
Comment #8
seren10pity commentedI had the same problem until I set "Multilingual content" module active, and selected
Multilingual support :
o Disabled
o Enabled
x Enabled, with translation
in the "content type" > "edit" page.
Hope it helps ;)
Comment #9
int_ua commentedSame issue. I have no "Multilingual support" tab on content type edit page, only "Multilingual settings".
Comment #10
int_ua commentedi18n disabled, still no translate tab on a node page and no "Multilingual support" tab on a content type edit page. translation module enabled.
Comment #11
int_ua commentedSorry, "Multilingual support" is present, it's just not a tab but a part of "Publishing options".
Comment #12
int_ua commentedMultilingual support = "Enabled, with translation"
solves the issue.
Comment #13
nigelss commentedThe translate tab also doesn't appear if your pages are marked as 'Language Neutral'. Change the page(s) to 'English' or your chosen language and then the translate tab will appear.
Cheers, Nigel
Comment #14
lukehollis commentedGah! Spent hours trying to make this work until I found your comment, Nigel. Thanks--that does the trick.
Comment #15
pieterdcThanks, int_ua.
Comment #16
jdjeet commentedThanks int_ua, That really helped me out.
Comment #17
alpinisteThank you int_ua! A real help! To clarify for other people (like me, as I didn't get it straightaway, as I was hugely confused by the time I found this thread...), the option of
Publishing options(which int_ua mentioned) is available in "Content types", that is,/admin/structure/types/manage/articleComment #18
kenorb commentedRelated:
- How to displaying translate tab in the node?
- “Translate” tab does not appear for every content
Comment #19
nehapandya55 commentedThanks nigelss comment #13 worked for me as i changed 'Language Neutral' to page to 'English' translate tab appears.
Comment #20
mcdoolz commentedConfirmed. Translate tab wasn't appearing because I had not resaved out the node with a language assigned.
Comment #21
avinash_thombre commented#8 is the correct steps; once you enable the translation related modules.
Comment #22
aguycalledmax commentedIn my case, upon checking reports>recent log messages after trying to access example.com/node/[node-id]/translate I saw an access denied error. All permissions for translate blocks and translate content where unchecked, checking the administrator permission for these resolved the issue