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
I confirm that this is an issue rather than a question.
Bug report
Setting build.publicUrl seems to correctly change the expected path for importing out of _saber, but the generated site still thinks that 'home' is / not /publicURL/.
I'm attempting to use saber to generate internal documentation on a self-hosted gitlab instance, using GitlabPages. Our pages urls are in the form of https://group-name.pages.git.example.com/project-name/. Setting publicUrl to /project-name/, while the site technically works, means that going to the index page takes me to the 404, and I have to hit 'back to home' to get the index, which has changed the url to be https://group-name.git.example.com/.
All that was required to reproduce it, however was:
Start a basic saber project.
Set publicUrl
Serve on a location other than /
Note: When I didn't have a theme set, I got a weird combination of the 404 page with some of the index page's content mixed in. Setting a theme just gets me just the normal 404 page.
What is expected?
I would expect to see the site.
What is actually happening?
I get the 404 page, and the 'Back' button takes me to the site correctly, but the URL is wrong, and refreshing the page, of course, generates a 404.
Other relevant information
Result of running saber -v:
saber/0.6.7 darwin-x64 node-v12.4.0
Browser version (optional):
Chrome Version 74.0.3729.169 (Official Build) (64-bit)
Is Saber a global or local install?
local
Which package manager did you use for the install?
yarn
Does this issue occur when all plugins are disabled?
Bug report
Setting
build.publicUrl
seems to correctly change the expected path for importing out of_saber
, but the generated site still thinks that 'home' is/
not/publicURL/
.I'm attempting to use saber to generate internal documentation on a self-hosted gitlab instance, using GitlabPages. Our pages urls are in the form of
https://group-name.pages.git.example.com/project-name/
. SettingpublicUrl
to/project-name/
, while the site technically works, means that going to the index page takes me to the 404, and I have to hit 'back to home' to get the index, which has changed the url to behttps://group-name.git.example.com/
.Version
v0.6.7
Steps to reproduce
You can see an illustration of this here:
https://morgul.gitlab.io/saber-publicurl-bug/
All that was required to reproduce it, however was:
publicUrl
/
Note: When I didn't have a theme set, I got a weird combination of the 404 page with some of the index page's content mixed in. Setting a theme just gets me just the normal 404 page.
What is expected?
I would expect to see the site.
What is actually happening?
I get the 404 page, and the 'Back' button takes me to the site correctly, but the URL is wrong, and refreshing the page, of course, generates a 404.
Other relevant information
saber -v
:yarn
IssueHunt Summary
krmax44 has been rewarded.
Sponsors (Total: $60.00)
Tips
The text was updated successfully, but these errors were encountered: