-
Notifications
You must be signed in to change notification settings - Fork 888
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
Error Generating site when using Docsy as a module #833
Comments
To my dismay I realized that #801 is not valid, module dependencies were inadvertently disabled in the final version that was merged. Sorry for that, I will author a PR that fixes this shortly. Fortunately, there is a way to work around this. In your
This should get you up and running. Please let me know if this solves your problem. |
Hello! Thanks for working on this. I am also seeing this issue and the copying and pasting the above into the config did not resolve it. Do I need to run any command again? I followed this guide: |
To be on the safe side, you can run:
Afterwards, for diagnostic purposes, you may run
If you don't see these 3 dependencies, you are in trouble and it won't work. Ah, and don't forget to remove or uncomment the following line:
This isn't explicitly mentioned in the conversion docs, I just added the missing part (together with some minor improvements). |
This should be fixed in #837, right? |
Hello @LisaFC, It isn't resolved for me. I removed docsy as a theme in config.toml, ran hugo mod clean hugo mod graph < my-module > github.com/twbs/bootstrap@v5.1.3+incompatible |
This should be bootstrap@v4.6.1, not @v5.1.3. You pulled in the latest version, that's incorrect. < my-module > github.com/FortAwesome/Font-Awesome@v4.7.0+incompatible This should translate to Font-Awesome@7d3d774145ac, which is 5.15.4. Font-Awesome@v4.7.0 is ways to old. < my-module > github.com/google/docsy@v0.0.0-20220117100953-fbc516e8d1dd This one is correct. Do you want to convert an existing site or start from scratch? If you can't make it work, present error messages or contact me off-list (see github account info). |
Hey @deining, I am getting the same error as above. I am converting an existing project. How do I ensure that my installs have the latest Font-Awesome and Bootstrap. I am not familiar with how go or Hugo modules work. |
@deining Ok I am passed the original error but now my site doesn't show anything. It is not understanding the language. I am going to flip back to non module and then see if it still happens. |
So when switching back to git submodule I am getting the same issues as #836. The fix for #836 did fix the font awesome issue, but now back to not rendering any content under a lang folder. If i move all the content under content it renders fine, but if i move it into content\en it renders the top and bottom divs but no actual content. |
With github submodules I have the same problem that I'll get problems with rendering, the sidebar shows a navbar from a different part of the website (blog?) that I am on, the main page is not rendering at all (apart from header) and some other pages (eg. the blog) are also not rendering. I have the same setup with the language folder |
@deining Should we close this out as the original issue has been fixed and open a new one up for the rendering issue? |
Yes, please.
Again, yes. Can you provide as many details as possible please? Is your project available publicly (github, gitlab, or so) or can we get access to it? Ideally we could reproduce the faulty behaviour locally. That would make it much easier to track it down. Thanks. |
Closing per consensus. |
Error: Error building site: TOCSS: failed to transform "scss/main.scss" (text/x-scss): SCSS processing failed: file "stdin", line 6, col 1: File to import not found or unreadable: ../vendor/bootstrap/scss/bootstrap. Both Prereq are installed.
The text was updated successfully, but these errors were encountered: