so bad i18n issues
soupp - January 28, 2009 - 21:58
| Project: | Node clone |
| Version: | 6.x-1.0 |
| Component: | Miscellaneous |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
Hi guys,
I was not very deep into the problem yet, but: (so beloved) node_clone module may have unpredictable cloning results and may cripple nodes and translations if you use it with i18n. The behavior is about the same in 5.x and 6.x branches. I've had this issues on few different installs (fresh and upgraded).
I just feel it would be nice to make a note about that on module's page. Something like "Warning: not recommended together with internationalization (i18n) module due to unpredictable translations behavior in certain circumstances".
#1
ok
#2
What sort of problems did you run into? I'd really like to be able to use this with i18n enabled, so I'd be glad to help track this down.
#3
The main problem was: when you create a cloned node it is recognized by i18n as new translation (of the same language sometimes!). But then you could not chose the next language to translate to (in i18n logic it was done already).
Then if there were the menu item with this node it would sit in the db even after cloned node deletion. So if you will go with translation (but not cloning) the menu item would clash with previously created (which then may unpredictably show up or not).
There were some more. The worst in my situation was that I even could not find a pattern for problem. The project was pretty urgent.
#4
Anybody did any further investigation on this subject? I might be need to look at this as well and worth knowing any findings in advance.
#5
Sounds like in D6 at least the tnid needs to be nulled out?
#6
I'm also interested in your experience with this combo.
#7
subscribing, and will invstigate...