I'm sure I am missing a minor detail / setting / module but when I used this in D6 I had a tab that would essentially copy the current node for another language, I don't see that tab anymore, it seems I would have to create a brand new node without it and then assign the language. Is there a way to turn this on I may have missed? Everything else is working correctly

Comments

kilrizzy’s picture

Also getting authorization error when going to "node/1/translate" which is what would work for d6. Permissions are set for admin

Jose Reyero’s picture

Status: Active » Postponed (maintainer needs more info)

Looks like its working. Are you using any potentially conflicting module like 'entity translation' ?

kilrizzy’s picture

Not using entity translation. I have Locale, Language Icons, and most of the I18n. Don't see anything that could be an issue

Jose Reyero’s picture

Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

Cannot 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)...

datarazor’s picture

same 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?

datarazor’s picture

same 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?

Jose Reyero’s picture

Try 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.

seren10pity’s picture

I 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 ;)

int_ua’s picture

Same issue. I have no "Multilingual support" tab on content type edit page, only "Multilingual settings".

int_ua’s picture

Status: Closed (cannot reproduce) » Active

i18n disabled, still no translate tab on a node page and no "Multilingual support" tab on a content type edit page. translation module enabled.

int_ua’s picture

Sorry, "Multilingual support" is present, it's just not a tab but a part of "Publishing options".

int_ua’s picture

Status: Active » Closed (works as designed)

Multilingual support = "Enabled, with translation"
solves the issue.

nigelss’s picture

The 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

lukehollis’s picture

Gah! Spent hours trying to make this work until I found your comment, Nigel. Thanks--that does the trick.

PieterDC’s picture

Thanks, int_ua.

jdjeet’s picture

Thanks int_ua, That really helped me out.

alpiniste’s picture

Issue summary: View changes

Thank 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/article

kenorb’s picture

nehapandya55’s picture

Thanks nigelss comment #13 worked for me as i changed 'Language Neutral' to page to 'English' translate tab appears.

mcdoolz’s picture

Confirmed. Translate tab wasn't appearing because I had not resaved out the node with a language assigned.

avinash_thombre’s picture

#8 is the correct steps; once you enable the translation related modules.

aguycalledmax’s picture

In 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