I was pulling my hairs of (I am now bold.) on how to to make admin interface language always independent on the content. This goes bad when I am creating new node. If I use Slovenian as my default admin language on paths node/add/* then creating English blog post on /sl/node/add/blog will give me Slovenian menus (or their items), Slovenian terms (if I decide to have term language based, I do!) etc.

Now if I create blog post in Slovene first (notice Slovene is my default language in all cases) then I can translate it. the link is like that:
/sl/node/add/blog?translation=10&language=en

Now I am creating English blog post where I can see English terms, menu items etc on a Slovenian interface. Great!

But what if I don't have an original Slovenian post? I tried using this path:
/sl/node/add/blog?translation=null&language=en

As you can see I added null instead of node ID there and It works fine.

Now the questions:
- Is this OK or some kittens will die because of me?
- The language selector drop down still show default language (with more weight). Can I fix that?

I hope I made my case clear.

Thanks for help.
Iztok

Comments

iztok’s picture

iztok commented

I just figure it that when creating translation the node is already "created" as an object? So when I am opening it in node/add/blog the language select is populated because it is its language.

Am I correct?

Is this: /sl/node/add/blog?translation=null&language=en then a bad idea?

jose reyero’s picture

jose reyero commented
Status: Active » Closed (won't fix)

Cleaning old issues (> 1 year without follow up)