I'm using i18n. When I use the "translate" page function, the translated page is created fine. However the original page loses its url alias and also its association with the translated page.

So where example.com is the base domain:

example.com/page > translate

[it doesn't seem to matter what I do with the domain affiliation settings - if I have it on the current domain and also de.example.com or just example.com or just de.example.com same thing happens]

de.example.com/page and/or www.example.com/de/page is created

example.com/page now only exists as example.com/node/11

example.com/node/11 has no translation

I'm not using any other node access modules.

Comments

apemantus’s picture

Title: Translations don't seem work » Translations don't seem to work
agentrickard’s picture

Category: bug » support

I have only tested with core Locale and Content Translation modules.

nonsie’s picture

Status: Active » Postponed (maintainer needs more info)

Can you provide a list of modules you are using on your site? I'm running DA with i18n on multiple sites without any problems like you described above.

apemantus’s picture

Status: Postponed (maintainer needs more info) » Closed (fixed)

Actually, looking into it I don;t think it was a problem with Domain Access. I uninstalled DA and even without it I still had the same problem. I rolled my database back a week before I started with the i18n stuff and started again, and things now seem to be working OK. Sorry for the false accusation!