Closed (fixed)
Project:
Metatag
Version:
7.x-1.x-dev
Component:
Multilingual/intl
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
13 Jun 2014 at 13:49 UTC
Updated:
12 Jul 2014 at 04:30 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
SebCorbin commentedAnother maybe related bug:
Bug: another revision is created, but the english version has the french custom meta
Comment #2
SebCorbin commentedPatch solving the first problem. Just state your mind, don't commit, I've still some performance improvements to do.
Also if you could explain this part (line 426):
That's actually what's causing the second bug (but in the same function)
Comment #3
SebCorbin commentedAnd here is another one, with performance fix and trying to mitigate "these certain occasions"
Comment #4
SebCorbin commentedTypo here
Comment #5
damienmckennaWe actually have a category for internationalization/multilingual support :)
Thanks for putting this together, I'll review it shortly.
Comment #6
damienmckennaMinor tweak.
Comment #7
damienmckennaData loss == critical, sorry for not noticing that earlier.
Comment #8
rmunsky commentedMaybe it is not related to this issue but we have a similar behaviour.
Even if we have just activate ML settings on a node so we can specify a language there but no translation the custom meta data gets deleted after a node gets published with the scheduler module.
Could you give me some information if this post here is related to this? Its, sure, also kind of very important for us not to loose the custom meta data when getting a ml enabled node live.
Comment #9
rmunsky commentedan update: if i save a node with set schedule settings before it gets published automatically, the meta data remains to be there properly.
Comment #10
damienmckenna@rmunsky: Did you test the patch above?
Comment #13
damienmckennaCommitted (twice, because I forgot to give proper attribution to Seb). Thanks SebCorbin!