Item14256: Data loss of certain formfield names when moving content from 1.x to 2.x.

Before 2.x, unicode chars have been stripped off from a formfield name. now we allow arbitrary unicode chars in there: see this code change from June 2015 made as per Item4419

Problem is when people move content from an old to a new site: they run into potential data loss due to the new naming scheme.

Given a form definition such as

| *Name*  | *Type* | *Size* | *Values* | *Description* | *Attributes* | *Default* |
| Fühler | text | 10 | | | | |

net data is stored as

% META:FIELD{name="Fhler" title="Fühler" value="123"}%

in an 1.x-er system whereas it is expected in %META:FIELD{name="Fühler" title="Fühler" value="123"}% by an 2.x-er system. As it is not there a next trivial edit-save cycle will result in data loss.

There is no way to switch back into the old way other than reverting this particular patch. We need a legacy switch of some kind.

-- MichaelDaum - 19 Dec 2016

Commenting is disabled while not logged in