![]() |
|
|
|
|
Change By:
|
Evzen Fochr
(05/Dec/14 1:56 PM)
|
|
Description:
|
Publishing a page tree might take some time. If this is the case and you're quick enough to trigger an unpublication of the same page tree, you might get an exception because Magnolia tries to deactivate something that wasn't properly activated yet (tested with ee 5.2.7 and 5.3.2). We should check how to prevent running into this situation. e.g. introduce a kind of dependencies between asynchronously executed action (only start second when the first is indeed finished).
Approach to solve
Solution of
this
will be
problem needs public API changes.
Proposed solution: Node need to know if it is part of recursive activation (only sub nodes, not parent) and if yes, check activation status of node on author. If node on Author is deactivated we should
quietly
ignore Exception for
skip activation of
this
case
node
,
because we know over recursiveActivation correctly activated it (no exception
and
continue activation
break of recursion) and somebody come after and deactivated it
.
For it you will need to change Syndicator interface.
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <
[email protected]>
----------------------------------------------------------------
