« Return to Thread: [Bug 668] New: grouped collection w/ accessname throws up in certain case

[Bug 668] grouped collection w/ accessname throws up in certain case

by Bugzilla from bugzilla-daemon@helma.at :: Rate this Message:

Reply to Author | View in Thread

http://dev.helma.org/bugs/show_bug.cgi?id=668





--- Comment #2 from s o <nostalgiker@...>  2009-07-23 13:18:41 ---
[15:38] <hannesw> what does the subnode mapping look like in the collection you
add to?
[15:39] <simono> like so http://helma.pastebin.com/m6b2f161c
[15:40] <simono> problem with the filter?
[15:42] <hannesw> hm, but the children definition is not generic?
[15:42] <hannesw> shouldn't it have a constraint for the prototype?
[15:42] <hannesw> ah, i see, you have it in the filter...
[15:42] <simono> yes
[15:43] <simono> i'll try with local/foreign instead of filter
[15:43] <hannesw> yes, that should work.
[15:43] <hannesw> however, i want this code to work too...
[15:44] <hannesw> have to think some more about it

----------
_children                  = collection (Content)
_children.local.1            = STO_ID
_children.foreign.1          = CNT_PARENT_ID
_children.local.2       = $prototype
_children.foreign.2    = CNT_PARENT_PROTOTYPE
# BUG HELMA DON'T FILTER
# _children.filter           = CNT_PARENT_PROTOTYPE = 'Story'

--
Configure bugmail: http://dev.helma.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Helma-dev mailing list
Helma-dev@...
http://helma.org/mailman/listinfo/helma-dev

 « Return to Thread: [Bug 668] New: grouped collection w/ accessname throws up in certain case