Bug #37292

PropertyMappingConfiguration::mapUnknownProperties is not passed down to Subconfiguration

Added by Marc Neuhaus about 1 year ago. Updated 11 months ago.

Status:New Start date:2012-05-18
Priority:Should have Due date:
Assignee:Sebastian Kurfuerst % Done:

0%
Category:Property
Target version:-
PHP Version: Complexity:
Has patch:Yes FLOW3 version affected:Git 1.1
Votes: 0

Description

if i set allowAllProperties on my PropertyMappingConfiguration it still can fail because the setting doesn't get passed down in line 152 from getConfigurationFor.

I've attached a patch to pass down this setting.

PropertyMappingConfiguration.diff (599 Bytes) Marc Neuhaus, 2012-05-23 14:57

Related issues

related to TYPO3.Flow - Feature #37436: PropertyMapper should allow settings like allowCreationFo... Resolved 2012-05-23
blocks Foo.ContentManagement - Major Feature #37293: Refactor Admin to work inside Phoenix as Foo.ContentManag... New 2012-05-18

History

#1
Updated by Marc Neuhaus 12 months ago

forgot to add the Patch :)

#2
Updated by Bastian Waidelich 12 months ago

  • Category set to Property
  • Assignee set to Sebastian Kurfuerst
  • Target version set to 1.1 beta 2

Sebastian, I assign this to you as you are more into that topic ;)
I had similar issues: especially when working with the Form framework it's really tedious to get the PropertyMappingConfiguration right.. There should be some easy way to disable the pessimistic checks (as the form is secured by HMAC anyways) and/or to allow creation/modification & property changes for nested elements

#3
Updated by Bastian Waidelich 12 months ago

  • Target version changed from 1.1 beta 2 to 1.1

#4
Updated by Karsten Dambekalns 12 months ago

  • Target version changed from 1.1 to 1.1 RC1

#5
Updated by Karsten Dambekalns 11 months ago

  • Target version deleted (1.1 RC1)
  • FLOW3 version affected changed from Git master to Git 1.1

Also available in: Atom PDF