- there might be a problem with the versioning: the
version of a
structure is not the same as the version of the structures children
parent.
(structure version != structure children first parent version)
...I'm not sure if the version should always be the same.
No, all structures are versioned independently. There is no need to
create new version for the parent, if a child changes.
yes, but I wanted to say that a child doesn't reference back to the
right version of the parent.
e.g node01 (version 500) has child node011, but node011 has parent
node01 (version 477)
Ok, now I understand. The reasons for this is probably that I changed
the versioning a while back, but the swap on the running server caused
some references to get invalid. Fixing this, should be as easy as
writing a 3-line-visitor.
to render the admin menu I used some simple mechanism
that renders a
menu according to a class and their subclasses:
AdminAction
AdminSecurity
AdminUsers
AdminRoles
AdminStructuresTree
eg. do AdminAction: render the menu of their subclasses (Security
and StructuresTree)
do AdminSecurity: render super, render the menu of their
subclasses (AdminUsers and AdminRoles)
but this system is not very useful and fexible 'cause it uses only the
structure of classes and their subclasses and this should't have
anything to do with a html menu to render...
Yeah, we should look for something more declarative, like having an
explicit action that can hold an arbitrary number of sub-actions. I
think users should be able to specify the actions as flat/nested as
they prefer in the template-editor.
Cheers,
Lukas
--
Lukas Renggli
http://renggli.freezope.org