Bug #4170

Form Viewhelper creates hidden identity field even for new objects

Added by Robert Lemke about 10 years ago. Updated almost 9 years ago.

Status:
Resolved
Priority:
Must have
Assignee:
Category:
ViewHelpers
Target version:
Start date:
2009-08-06
Due date:
% Done:

100%

Has patch:

Description

Every entity has a uuid, no matter if it's new, reconstituted or clone of a reconstituted object.

Earlier the form view helper only rendered the hidden identity field for objects which were not new. However that stood in the way for implementing the new edit mechanism which should expects that the identity of a clone is also render, although a clone is "new".

We need a check which assures that the identity field is render for objects being new and clone but nor for object being new and not a clone.

Associated revisions

Revision 5dfceac0 (diff)
Added by Robert Lemke about 10 years ago

[+FEATURE] FLOW3 (Persistence): The persistence framework (Dirty Monitoring Aspect to be exact) now traces if an entity is a clone of an existing (= reconstituted) entity. This allows for intelligently rendering a hidden identity field in forms by Fluid's Form Viewhelper. Relates to #4170
[+BUGFIX] Fluid (ViewHelpers): Added an additional check for rendering the hidden identity field: the hidden field is only rendered for "new" objects if they are in fact a clone of an existing object. Resolves #4170
[~TASK] FLOW3 (Core): Only touched the bootstrap so that all caches are flushed on the next hit, because old proxy classes would call a fatal error otherwise.

History

#1 Updated by Robert Lemke about 10 years ago

  • Status changed from Accepted to Resolved
  • % Done changed from 0 to 100

Applied in changeset r2991.

Also available in: Atom PDF