-
-
Notifications
You must be signed in to change notification settings - Fork 7.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prevent resource publishing if only its .Content
is outputted.
#4944
Comments
Vice-versa, I was trying to move a site from my pre-43 system to post-43 and I ran into the issue that my font files were in a subfolder from my SCSS and so when I just moved the SCSS folder from My preference is that everything in |
Another issue: My SCSS refers to a background image. Ideally, the background image should also be hashed somehow? But in any event, I also had to split the |
Hi @carlmjohnson. Files in the assets directory m should not be automatically published because a lot of them are there to be processed. Furthermore this issue is about tightening the « publishing » rules for the assets, so your comments appear to be out of scope. You do make an interesting case though and I encourage you to bring it up in the discourse if you have not done already. |
Why not? The file size is probably trivial, and I'm not worried about someone hacking my site by reading the SCSS. :-) I do see the case for not wanting to publish, e.g., large images multiple times, but in general, I think there's no reason to publish it all by default. |
That will never happen (for several reasons, but I'm not takin that debate -- but it is a fundamental difference between /static and /assets). I think this was a "glitch in my implementation", as in -- it was meant to be the way @regisphilibert wants it. And that is in line with what happens if you do
The transformed resources behave differently, possibly because of an implementation optimization -- I can create an |
This issue has been automatically marked as stale because it has not had recent activity. The resources of the Hugo team are limited, and so we are asking for your help. |
That is, if only `.Content` is accessed. Fixes gohugoio#4944
That is, if only `.Content` is accessed. Fixes gohugoio#4944
That is, if only `.Content` is accessed. Fixes gohugoio#4944
That is, if only `.Content` is accessed. Fixes gohugoio#4944
That is, if only `.Content` is accessed. This means that, for a transformed resource to be published to `/public`, you need to access either `.RelPermalink` or `Permalink`. Fixes gohugoio#4944
That is, if only `.Content` is accessed. This means that, for a transformed resource to be published to `/public`, you need to access either `.RelPermalink` or `Permalink`. Fixes #4944
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Currently, a resource will be published even if only its
.Content
is outputted in the template (and not its.Permalink
):I guess this could cost some build time in the rare case where a user needs to output both the
.Content
of a resource and its.Permalink
.The text was updated successfully, but these errors were encountered: