Hi Tom
Thanks for the pointer.
It's possible that this is the bug, but activation only fails when the
node is already active... Does magnolia only create this temporary
node at the root level when it needs to replace a node?
BTW: it does not matter which user has activated the node.
-will
On 09.11.2009, at 12:13, Tom Wespi wrote:
Hello
i think it is this:
http://jira.magnolia-cms.com/browse/MAGNOLIA-2903
On 09.11.2009, at 12:01, Will Scheidegger wrote:
Dear Magnolians
We're experiencing strange activation problems on Magnolia 4.
Actually, our users are experiencing the problems, because with
"superuser" everything works fine (and super fast) of course.
The problem:
When a user "johndoe" tries to activate a page the superuser has
activated before he will get the following error message:
"User not allowed to (Add, Set, Read) path [/39f73a94-
cd1e-11de-84fd-1d038000d537] on web8092"
When the user deactivates the page (works fine) and activates it
again, things work fine. Before I file a JIRA issue: has anyone
experienced the same misbehavior? Or is there something wrong with
our installation?
Thanks!
-will
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
--
Leitung Bereich Entwicklung & Programmierung
esense GmbH
Leonhardsstrasse 38
CH-4051 Basel
[email protected]
+41 (0)61 271 35 01
http://www.esense.ch
P please consider the environment before printing this e-mail.
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
