export adds a / to path of static resources
See original GitHub issueThe export feature works nearly perfectly, but all my static resources got an extra / in front of them, making them break. building from the blog or portfolio template, if I export
src="{% static 'images/heroImage.jpg' %}"
It generates out too
src="/static/images/logo.jpg"
When it should be
src="static/images/logo.jpg"
maybe a feature request for a modal asking the domain you will be hosting the site on would make sense (and prefix it to the path)? That way all resource links are absolute, a best practice.
Issue Analytics
- State:
- Created 9 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Generated static files html files have wrong assets paths #8158
I'm tried to generate a static site with Next js v9.0.2 and got assets linking by default to /_next/static/something/something.js . But by ...
Read more >LWC loadScript from static resource with export inside
I have tried modified the library (the calc.js file) like removing export keyword and it load successfully. I have many libraries in my...
Read more >Node: how to export/require correctly? Cannot serve static files
When I add app.use() to serve my static files to my server/index.js file it all works, but when I leave app.use insight my ......
Read more >Referencing a Static Resource in Visualforce Markup
To reference a standalone file, use $Resource. · To reference a file in an archive, use the URLFOR function. · You can use...
Read more >Exporting Workspace Static Files - APEX - Oracle Help Center
Export a workspace static files using the apex export command and -expFiles option.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
hey all. I fixed this for myself with an ugly hack.
This is a plugin, which overrides the default static and url tags and computes relative URLS using the builtin python relpath() Happy if someone else wanted to clean this up and add a config flag. For now it’s clean enough for my purposes.
@cjrider is there anything special I need to do, to get this plugin to work? Do I just toss it into a .py file and dump it into the plugin directory? Do I need to include it?
Sorry, I’m a total noob with the plugin paradigm in cactus.