-
Notifications
You must be signed in to change notification settings - Fork 132
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 building site: failed to render pages: render of "home" failed #72
Comments
I am getting the same error. @sbuvaneshkumar did you find a solution or workaround for this? |
@connor11528 Unfortunately no, still I don't find any workaround or solution. |
Hi @sbuvaneshkumar @connor11528 [[menu.main]] |
Okay thank you @pferretti I added this and am getting an error on the command line. For all my files in content/posts/ directory I have the date saved like:
|
Okay nvm, I think I was just missing some configuration options. I added the config and everything is working now. I believe this issue can be closed out Based config from the exampleSite (doh)
|
Hi, I am still unable to get solution of this. Can anyone please help me out?? |
Yeah me too, above solutions didn't work. |
@Ayush23Dash @mubashirjamali101 I had this exact issue and it was in the config.toml. In the theme 'Blonde', there's an exampleSite. I started copying and pasting the exampleSite files into mine, and finally when I got to config.toml the Try and find an exampleSite folder in your theme, or download one that does. |
I had the same issue, here is how I solved it: Step 1: Step 2: Go to the last line in that script in RStudio and type in this (see below) and save it: security: |
don't know why but it really works! |
I have the same problem with an existing site which worked before. Very frustrating. Will there ever be a proper fix? |
@krischik Can you create a new issue detailing the problem you're facing with steps to reproduce or code / repo that I can use to investigate your problem? |
After adding theme, I am getting following error.
I have tried with brand new site, without any content, facing the same issue.
The text was updated successfully, but these errors were encountered: