Jump to:
| Project: | Node clone |
| Version: | 5.x-2.4 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
If you try to clone a node with a language assigned (Localizer), the module localizer kicks in and doesnt let you save the clone saying there's already a translation asigned to that language.
A translation for language is already present in this set.
Remove the translation from this set before proceeding
If you save it as a different language with no translation asigned, its ok. However, even though after saving it's another node, it stil won't let you switch the language of the new cloned node back to the original, giving you the same error. So apparently the assignation is preserved through the clone process.
I dont know wether this bug belongs to this module or to localizer, I guess probably to both. Either way I thought I should let you know :)
Comments
#1
Well, the sooner i submit this report, the sooner I find a workaround... :s
I'll write it here in case someone else runs into it.
The workaround is
#2