I'll have more questions in the coming weeks, but for now I'd like to
know how to secure custom AdminInterface menu buttons.
Give the role read access to the menupoint (to the node you defined in
the config) or deny it if this role should not see the button.
I love how easy magnolia 2.1 makes it to add a buttons to the
admininterface (add a node in Config and then refresh and get the
change
immediately). Huge improvement over 2.0. Kudos! I was really hoping
that when I went to setup a role that I would be able to restrict
visibility of this button just like I can with the other 4 (website,
users, roles, config).
Do it in the config (see the the editor role as an example)
It turns out that the drop-down list for the roles ACL is static
rather than dynamic. How can I extend this list? Ideally I would like
for it to be dynamic, but I will settle for being able to manually
edit the list.
The dropdown contains a list of the repositories. Since you store the
most of the data in one of this repositories this should do the job. If
you add a new repository you would get a new entry in the dropdown too.
But you are right in future version we must think about a more straight
forward user interface.
Philipp Bracher
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
