[Flow] SOLVED Re: propertyMapping bug?

[mario chiari]

Hi All

finally, I got the point. 
I need to initialize the createAction to configurate subProperties.
Indeed it seems to work fine for further levels too: Father/Son/Toy/...
see updated  http://pastebin.com/mYEHXt6K .

please forget, and sorry to bother
cheers
mario

On Fri, 2013-10-18 at 11:58 +0200, mario chiari wrote:
> Hi Helmut, All, 
> 
> yes, the patch helps and seems to fix the issue with validation.
> For the other issue, see 
> http://riesvantwisk.com/cms/home/irc-logs/typo3-flow-irc-log/2013/October/16.html
> around 10.00, ChristianM's suggestions. Method 1 helps. 
> 
> Still, I am not sure that everything is fine. 
> I have tried to boil down a minimal example, see
> http://pastebin.com/mYEHXt6K 
> As far as I am able to check, things go thru for (in your example terms)
> two users, a invoice each; but fails for two users, more invoices each. 
> 
> It seems to me a sort of bug, althogh I am not sure how to describe it.
> Note that I find an ad-hoc way out, but clearly I do not know what I am
> doing.
> 
> I appreciate any help to clarify the issue.
> 
> Thanks, Cheers
> mario
> 
> 
> On Wed, 2013-10-16 at 00:08 +0200, Helmut Hummel wrote:
> > Hi!
> > 
> > On 15.10.13 16:11, mario chiari wrote:
> > 
> > > Anyway, I have some update, see at http://pastebin.com/2Gip3DSJ (see
> > > description of what happens at the very end)
> > > Now, it seems that something goes wrong because there are input fields
> > > for both father and sons objects. Do you spot anything I wrote wrong?
> > 
> > Do you use Flow 2.0 ?
> > 
> > You may run into this issue regarding the validation:
> > 
> > https://review.typo3.org/24218
> > 
> > 2.0 is affected but the patch has not been backported yet to 2.0
> > 
> > Regarding the fact, that the father property of the sons is NULL:
> > 
> > I'm not sure if it is a bug, but at least it also did not work for me.
> > 
> > Let's take another example, the viewhelpertest package.
> > 
> > A User[1] has invoices[2] which point to the user
> > 
> > With a Fluid form of a new action with user.firstname, user.lastname, 
> > user.invoices.0.subject form fields, the property mapper maps a correct 
> > user object with a invoice object that lacks the user object in the 
> > customer property.
> > 
> > I guess this is an issue with the property mapper which might need 
> > workarounds with hidden fields to set the customer correctly, but I also 
> > don't know how to set this up correctly
> > 
> > Kind regards,
> > Helmut
> > 
> > 
> > [1]https://git.typo3.org/Packages/Viewhelpertest.git/blob/10e40061e731bd402b33e67182172d3c7e469a49:/Classes/TYPO3/Viewhelpertest/Domain/Model/User.php
> > 
> > [2]https://git.typo3.org/Packages/Viewhelpertest.git/blob/10e40061e731bd402b33e67182172d3c7e469a49:/Classes/TYPO3/Viewhelpertest/Domain/Model/Invoice.php
> > 
> 
> 
> _______________________________________________
> Flow mailing list
> Flow at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/flow