test case:

Assume you view node/10
"Translations"
"create translation" (for language Greek lets say)
Don't save the translation node

Later on
browse to node/10
You press "Translations"
You press "create translation" (for Greek language again)
Don't save the translation node (again)

if you go to admin/content/node you have node/10 + 2 translations of node/10

is there any way to check before creating another node ?

I think the most logical would be to associate each node with its translation immediatelly after pressing "create translation"

CommentFileSizeAuthor
#6 localizer_6.patch20.3 KBsun
#5 localizer_5.patch20.38 KBsun
#4 localizernode.module.patch2.64 KBsun

Comments

Roberto Gerola’s picture

Roberto Gerola commented

The "problem" is the node cloning system.
It make a clone of the node, save it and then shows it.
Yes, the association is not yet saved at this level.
Yes, it is better save it immediately.

Thanks

hass’s picture

hass commented

however this sounds to be a garbage creation system... but if i press cancel this shouldn't be saved... i think it is not a good behavior if something is saved i don't want to be save.

node_clone have such a feature you can manually activate... "create node if 'clone node' tab is clicked". I don't know who uses this stupid setting... another garbage system build in a module.

giorgosk’s picture

giorgosk
Location Chios, Greece 🇬🇷
commented

Roberto take a look at this http://drupal.org/node/110294 discussion
if you ever want to do a custom copy function

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Title: "Create translation" creates a translation that is not immediatelly associated with its base node (parent) » "Create translation" creates content in front of submit
Assigned: Unassigned » sun
Status: Active » Needs work
StatusFileSize
new localizernode.module.patch2.64 KB

Just wanted to let you know that I'm working on this issue. The attached patch contains the changes that have been made so far. It's not functional yet.

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Priority: Normal » Critical
Status: Needs work » Needs review
StatusFileSize
new localizer_5.patch20.38 KB

@Roberto: Here's the patch I was talking about.

Functionality is the same, but localizernode no longer creates a new node in front of submitting a translation.

Please test. Do not test on productive sites.

Would be glad to receive feedback as soon as possible, because we're currently working on major localizer improvements that need to be finished in the next days.

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Status: Needs review » Reviewed & tested by the community
StatusFileSize
new localizer_6.patch20.3 KB

smk-ka has reviewed and partially reworked the last patch.
I've tested it once again and this seems to be RTBC now.

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Status: Reviewed & tested by the community » Fixed

Committed to 5.x. Thanks smk-ka.

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)