-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Content is not displayed #730
Comments
Hey, @fabiogeraci. Could you please provide us more information about the issue? But, this line |
Hey, Failed to load resource: the server responded with a status of 404 (Not Found) I am not actually sure that the issue is the theme I tried a different theme and it was not rendering correctly the examplesite |
Which version of Hugo are you using? Well, try running
(You might have problems to use the |
@luizdepra reappear process is as follows:
|
@luochenxi where this error appears? In the browser console or on the commandline output? I don't remember adding the |
@luizdepra In the browser console. I did not make any changes, but simply reproduced the steps above. |
@luochenxi, right. I tried reproducing the issue and I didn't get the error. Try accessing the page with other browsers or using the incognito mode. It looks like an extension or something is trying to access the file. As far as I know, the |
You reference the site.webmanifest here. Since it does not make sense for Hugo Coder to have it, should you remove that line from custom-icons.html in layouts? |
There are a few lines in this file that make assumptions about existing content. Some kind of settings should be checked before enabling these lines, else 404 errors are thrown in the browser console. |
Error handling response: TypeError: Cannot read properties of null (reading 'codescript')
at chrome-extension://iamhhblhmpldjchjecmapgoikpjmmfoe/content/content.js:4:18
site.webmanifest:1 Failed to load resource: the server responded with a status of 404 (Not Found)
site.webmanifest:1 Manifest: Line: 1, column: 5, Unexpected data after root element.
site.webmanifest:1 Failed to load resource: the server responded with a status of 404 (Not Found)
The text was updated successfully, but these errors were encountered: