-
-
Notifications
You must be signed in to change notification settings - Fork 7.4k
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
Partial live reload not working for mixed case templates #12165
Comments
I have to downgrade for now using this version to experience a fully working live reload:
|
We re-implemented the partial server rebuilds in Hugo |
original partial filename is in a camel case form.
I'm new to hugo, any information you can deduce from this, thanks. |
Another set of debug messages:
|
@FN-FAL113 See bep's response:
That means we need a small test repo that successfully builds and consistently reproduces the condition you describe. |
https://github.com/FN-FAL113/hugo-test-partial-live-reload |
Seems like renaming the partial to all lowercase fixes the issue. Idk if this is a small fix but if its a great first issue I would like to contribute else I'm happy to share to you guys what may be the problem. |
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. |
The css are declared in a style declaration tag. CSS from the parent element are being updated properly in the page but with partials I have to change to different page then go back. I tried updating hugo from v0.123.3 to the latest but no to avail.
OS: Windows 11 (22H2)
IDE: vscode
BROWSER: Chrome/Edge/Firefox
UPDATE: Even the partial does not get updated when changing its html, I have tried various arguments like no http cache, ignore cache and disable fast render, still not working unfortunately. The partial is in a loop that receives an iterated regular page context.
What version of Hugo are you using (
hugo version
)?Does this issue reproduce with the latest release?
Yes
The text was updated successfully, but these errors were encountered: