-
Bug
-
Resolution: Fixed
-
Neutral
-
1.9
-
None
-
-
Empty show more show less
-
Yes
-
Yes
-
Maintenance 30, Maintenance 31, Maintenance 32, Maintenance 33, Maintenance 34, Maintenance 35, Maintenance 36
-
5
Investigation: initial estimate 3sp
Investigation outcome and action taken
Failure happens when you move/rename a node between different subtrees. There is a workaround: you can publish by hand the node with problems and then sync again.
As there is a workaround, first we are going to improve communication to the user. When user launches synchronization process and there is an error related to this problem, we will send a notification to the user with the error, description of the problem and way to fix manually starting a publish of parent. Later we will review the api way to launch synchronization to give similar information in the response.
- depends upon
-
MAGNOLIA-7935 Store original path versioning
-
- Closed
-
- is related to
-
PAGES-357 DOC: Best practice for moving pages after publication
-
- Closed
-
-
-
- Closed
-
- relates to
-
-
- Closed
-
- to be documented by
-
-
- Closed
-
- mentioned in
-
Page Loading...
