Beware of activating the anonymous role - I just did it (it seemed a
reasonable thing to do at the time) and it made my public instance
inaccessible. The anonymous role in the authoring instance seems to be
set to deny anonymous access to any URLs. That makes sense once you
think about it, but the problem is that these kinds of asymmetries
between the authoring and public instances are not at all obvious to
the user - there's nothing to tell me that it's a bad idea to publish
that role. Almost every problem I've had with Magnolia has ended up
coming down to these kinds of problems - the two instances getting out
of sync or something from the authoring instance not being pushed to
the public instance or being pushed when it shouldn't have.
Magnolia seems to be getting a lot more user friendly these days, but
it still seems to me that the way that it exposes very brittle
configuration in a very raw way is extremely dangerous - it's just too
easy to do the wrong thing and break something without having the
faintest idea why.
I've always thought that the Dialog mechanism would be ideal for
making preference pages - surely it would be better if higher level
configuration pages could be defined in a similar way to the way that
we define paragraph editing dialogues?
just a thought,
josh
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
