-
Bug
-
Resolution: Fixed
-
Major
-
1.3.9
-
-
Empty show more show less
-
Nucleus 38
-
3
-
Yes
Steps to reproduce
In Magnolia Demo Author do
- Â Open pages app
- Â select /travel/about
- ensure that this page is published (i.e. "travel/about" exists on the public instance)
- edit page and change headline or intro or any other field
- close editor and click "publish" and "publish" to start the workflow (now there exists a new version "1.0" of "about" and a publication task that points to this page and version)
- rename the page to "test"
- open the tasks, choose the publication request created in step 5, click "preview", "assign to me" and "approve" to publish the change in /travel/about
- after successful publication, there is a page "/travel/test" on the public instance which contains the changes made above. And on the autor instance the publication state is yellow.
Â
Expected results
Page should not be renamed when approving a publication task for a version with the original name.
Actual results
Page is renamed on public instance when publishing a version of a page that is in the workflow while renaming it.
Workaround
None.
Acceptance criteria
- is related to
-
MAGNOLIA-8929 Restoring node ignores node name
- Open
-
PUBLISHING-188 Publishing children of a renamed parent throws exception
- Closed
1.
|
Implementation | Completed | Adam Siska | |
2.
|
Code review | Closed | AntonĂn Juran | |
3.
|
Preint QA | Completed | Jaromir Sarf | |
4.
|
QA | Completed | Jaromir Sarf |