While all of us are waiting for the new dev release and testing of it, there is one more question.
How this module deals with translatable content? If user can create only one node of some content type, can it translate that node to other languages?

Comments

mortician’s picture

mortician commented

Any update on this?

duaelfr’s picture

duaelfr
he/him
Primary language French
Location Montpellier, France
commented
Version: 6.x-1.x-dev » 7.x-1.x-dev
Status: Active » Needs work

Sorry I did not see your question before...

Currently, multilingual content is not supported by the module. Indeed, it have to be in the future.
Another problem is that 6.x branch is bugfix only and regarding to my current free time, I will not be able to fix it quickly (and some issues may be more important).
However, I pledge this will be integrated to the 7.x branch as soon as I will have a little free time to spend here.

Regards.

rockie667’s picture

rockie667 commented
Issue summary: View changes

Any news on this issue? Three years have gone since the last update of the maintainer...

kopeboy’s picture

kopeboy
Primary language Italian
Location Milan
commented
Category: Support request » Feature request
Status: Needs work » Closed (won't fix)

Yes, this module potential is great but seems abandoned :(
I am just now looking at the code myself (even if I'm not a coders) do understand if I can make myself what I need to add (I am interested in having custom url redirects based on limit types).

Anyway, this module doesn't support Content translation (the method that duplicates nodes and link them as translations of each other), but I would recommend you to use Entity Translation, which translates at field level without creating a new (translated) node. Entity translation works with this module (of course, you will still have only 1 nid for all the translations) and is also the concept behind Drupal 8 translation (the way to go!).