A full-featured, open-source content management framework built with Node.js that empowers organizations by combining in-context editing and headless architecture in a full-stack JS environment.
The admin UI now functions reasonably when the current URL was rendered directly with sendPage and there is no "in context" page or piece.
What are the specific steps to test this change?
I tested this fix in BM's project, then gave them a simpler way since their situation really did call for a "current page" to exist anyway (they were implementing fancy rendering of a parked page and didn't know about dispatch yet).
What kind of change does this PR introduce?
(Check at least one)
[X] Bug fix
[ ] New feature
[ ] Refactor
[ ] Documentation
[ ] Build-related changes
[ ] Other
Make sure the PR fulfills these requirements:
[X] It includes a) the existing issue ID being resolved, b) a convincing reason for adding this feature, or c) a clear description of the bug it resolves
[X] The changelog is updated
[ ] Related documentation has been updated
[ ] Related tests have been updated
If adding a new feature without an already open issue, it's best to open a feature request issue first and wait for approval before working on it.
linear[bot]
commented
1 month ago
Summary
The admin UI now functions reasonably when the current URL was rendered directly with
sendPageand there is no "in context" page or piece.What are the specific steps to test this change?
I tested this fix in BM's project, then gave them a simpler way since their situation really did call for a "current page" to exist anyway (they were implementing fancy rendering of a parked page and didn't know about dispatch yet).
What kind of change does this PR introduce?
(Check at least one)
Make sure the PR fulfills these requirements:
If adding a new feature without an already open issue, it's best to open a feature request issue first and wait for approval before working on it.
Other information: