You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Save As loses the requested page path when parent folders do not exist
#8267
When creating a page at a nested URL whose parent folders do not
exist, the requested path survives into the editor, but the Save As
dialog selects the site root and retains only the filename.
This can result in the page being saved at the root instead of its
intended project location.
Environment
Wiki.js: 3.3.0
Deployment: official container image on Kubernetes
Database: PostgreSQL
Browser: Microsoft Edge on Windows
Editor: Markdown
No application source or compiled assets modified
Steps to reproduce
Choose a nested path whose parent folders do not exist, for example:
/repos/path-test/project-1/overview
Navigate to that URL.
On the missing-page screen, click Create Page.
In the Markdown editor, click Create Page to open Save As.
Inspect the selected folder and Path Name.
Expected behavior
The complete requested destination should be preserved.
If parent folders do not exist, the dialog should retain the intended
path and either create those folders when saving or explicitly ask
how to proceed.
Actual behavior
Save As selects root, displays "/" as the directory, and shows only
"overview" in Path Name.
The editor's page state still contains the complete requested path
while the dialog is open.
Browser verification
The behavior was reproduced in Edge using Playwright.
The missing-page screen displayed the complete requested path.
The editor retained that path.
Save As selected root when the parent folders were missing.
The proposed save request omitted the parent path.
A control using an existing parent folder correctly retained it.
Using hyphens instead of underscores reproduced the same failure.
Save requests were intercepted and blocked before reaching the server.
No test pages or folders were saved.
The same missing-folder behavior was also reproduced by opening:
/_create/markdown?path=
This therefore reproduces independently of the external application
that originally supplied the documentation link.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Summary
When creating a page at a nested URL whose parent folders do not
exist, the requested path survives into the editor, but the Save As
dialog selects the site root and retains only the filename.
This can result in the page being saved at the root instead of its
intended project location.
Environment
Steps to reproduce
/repos/path-test/project-1/overview
Expected behavior
The complete requested destination should be preserved.
If parent folders do not exist, the dialog should retain the intended
path and either create those folders when saving or explicitly ask
how to proceed.
Actual behavior
Save As selects root, displays "/" as the directory, and shows only
"overview" in Path Name.
The editor's page state still contains the complete requested path
while the dialog is open.
Browser verification
The behavior was reproduced in Edge using Playwright.
Save requests were intercepted and blocked before reaching the server.
No test pages or folders were saved.
The same missing-folder behavior was also reproduced by opening:
/_create/markdown?path=
This therefore reproduces independently of the external application
that originally supplied the documentation link.
All reactions