Details
-
Bug
-
Resolution: Timed out
-
Low
-
1
-
Severity 3 - Minor
-
Description
Issue Summary
If a page created in the new editor format, via API is reverted to a previous version, in the page history option, it is converted to the legacy editor, instead of keeping the new editor.
Steps to Reproduce
- Create a page via API call, making sure it is being created with the v2, new editor. ( { "key": "editor", "value": "v2" })
- Access the created page and confirm it is on the new editor in the UI
- Publish the page with some content on it two or three times
- Access the page history option, in the page menu
- Restore the version 1 of the page
- Confirm it and reload
- Access the page
Expected Results
The page is restored from its version 1 and it is on the new editor format, as it was originally created.
Actual Results
The page is converted to the legacy editor.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
Attachments
Issue Links
- relates to
-
CONFCLOUD-68057 Creating a page via API doesn't load the New Editing Experience
- Closed