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
If you generate a site that will be served at https://example.com/foo/bar/ in directory output all your links will point to /foo/bar/… and htmltest will try to look in output/foo/bar/…. Add a conf option to move the site root.
As a workaround you could put your site in output/foo/bar/ and the run htmltest as before with DirectoryPath set to output.
The text was updated successfully, but these errors were encountered:
A related issue is if you have absolute URLs like https://example.com/page.html and page.html exists in your project folder, but not yet on the site (because it hasn't been uploaded yet, since you're running the pre-upload test now). You should be able to specify the base URL so this is properly interpreted.
This this issue currently being worked on? I'd like to contribute to the project but It seems like this is an old issue. My interest in taking this on is because I would like to be able to test Docusaurus built static sites. I'm currently encountering the need to set a basepath.
As a workaround you could put your site in output/foo/bar/ and the run htmltest as before with DirectoryPath set to output.
Also this workaround did not work for me. I get errors because the absolute path starts with the name of the DirectoryPath so the files can't be found in /output/output/foo/bar/.
If you generate a site that will be served at https://example.com/foo/bar/ in directory
output
all your links will point to/foo/bar/…
and htmltest will try to look inoutput/foo/bar/…
. Add a conf option to move the site root.As a workaround you could put your site in
output/foo/bar/
and the run htmltest as before withDirectoryPath
set tooutput
.The text was updated successfully, but these errors were encountered: