You are here: Foswiki>Tasks Web>Item14256 (18 Feb 2017, GeorgeClark)Edit Attach

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

pencil
Priority: Urgent
Current State: Closed
Released In: 2.1.3
Target Release: patch
Applies To: Engine
Component: DataForms
Branches: Release02x01 master
Reported By: MichaelDaum
Waiting For:
Last Change By: GeorgeClark
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

 

ItemTemplate edit

Summary Data loss of certain formfield names when moving content from 1.x to 2.x.
ReportedBy MichaelDaum
Codebase 2.1.2, 2.1.1, 2.1.0, 2.1.0 beta1, 2.0.3, 2.0.2, 2.0.1, 2.0.0, 2.0.0 RC, trunk
SVN Range
AppliesTo Engine
Component DataForms
Priority Urgent
CurrentState Closed
WaitingFor
Checkins distro:47238cf68eef distro:026a713017d6
TargetRelease patch
ReleasedIn 2.1.3
CheckinsOnBranches Release02x01 master
trunkCheckins
masterCheckins distro:47238cf68eef distro:026a713017d6
ItemBranchCheckins
Release02x01Checkins distro:47238cf68eef distro:026a713017d6
Release02x00Checkins
Release01x01Checkins
Topic revision: r6 - 18 Feb 2017, GeorgeClark
The copyright of the content on this website is held by the contributing authors, except where stated elsewhere. See Copyright Statement. Creative Commons License    Legal Imprint    Privacy Policy