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
Generated paths during the output generation don't point to the right files.
For example the blog folder.
The static folder is in the parent directory, to fix this while creating any new folder all the paths inside it should start with ../ or be absolute path.
The text was updated successfully, but these errors were encountered:
Can you provide an example of the fix that you're suggesting.
If I understand correctly the issue is that the static path isn't pointing to an absolute path so you wind up with urls not always pointing to the correct path.
This is an issue that I've noticed a few times when dealing with GH Pages where your url may not be the root path. I think the best solution is one similar to other frameworks where there is a {{"<PATH/AFTER/STATIC>" | static }} or similar pattern be added to create an absolute URL for the path.
My main concern with this is do you use that in content for blog posts or do something different.
To my knowledge you cannot pass jinja variables into your content (perhaps this is a reason to change that).
We agreed on using absolute paths for the whole website during generation we substitute with the SITE_URL var instead of relative or current implementation to account for cases when you just want to double click on the page to open it instead of using a server.
Generated paths during the output generation don't point to the right files.
For example the blog folder.
The static folder is in the parent directory, to fix this while creating any new folder all the paths inside it should start with
../
or be absolute path.The text was updated successfully, but these errors were encountered: