I'm very confused as it used to work just fine.
I have a blogdown website hosted on GitHub Pages, that includes reveal.js slides.
I presented those slides in the summary of 2019 from that website.
The pages where slides should be are now generating a 404 error when browsing the website on GitHub Pages (e.g., https://kevinrue.github.io/slides/bioc2019-flashtalk/#/), while the site served locally by blogdown::serve_site() shows those slides without problem at the corresponding local URL.
For instance the 404 error above should display the slides in this file
https://github.com/kevinrue/kevinrue.github.io/blob/master/slides/bioc2019-flashtalk/index.html
I'm really stuck after trying a number of things. I'm happy to take suggestions and report here on their success.
Any suggestion is welcome!
Kind regards
Kevin
PS1:
Somehow, netlify shows those pages just fine: https://quirky-jepsen-c23a11.netlify.app/slides/bioc2019-flashtalk/#/
I've also contacted GitHub Support in case it could be anything on their side.
Problem solved by the GitHub support team.
The issue was due to a new repository called "slides" on my account, which also deployed files to GitHub and interfered/overrode the "slides" subfolder of my github.io website.
Basically: make sure you avoid name conflicts between subdirectories of your main github website and repository names.
Related
I'm trying to update a project website using hugo via blogdown through R and RStudio.
I'm making edits to the Tweet embedded on the front page as well as the people on the committee page.
All of the updates work fine when I run the page locally with blogdown::serve_site(). However, the edits aren't being realised online.
The changes seem to be recorded on GitHub so I'm not sure where I'm going wrong. Here's the associated GitHub page.
It turned out the issue was related to the build image on Netlify.
Netlify gives some background about it here https://answers.netlify.com/t/please-read-end-of-support-for-xenial-build-image-everything-you-need-to-know/68239
As they say on the site, "You can upgrade to the latest build image in the Netlify UI under Site settings > Build & deploy > Continuous Deployment > Build image selection."
I already have a site created with blogdown and want to make it live. To try it out, I built the site using blogdown::build_site() . After managing to upload all the content from the public folder on Github. I see that the formatting of my site does not match what I have on the localhost when I run blogdown::serve_site(). The site I created is slightly complex since there are many subfolders created under each topic. I used the Hugo Book theme from this github page. The format of the site is the same as shown on the theme's github page.
I also checked the index.html file from the public folder and it looks like the image above. I am not sure how can I make my site to look like the second picture. I would appreciate any help and thank you in advance.
I am following the instructions here: https://alison.rbind.io/post/up-and-running-with-blogdown/
I did everything except for the Netlify section which I am assuming is optional.
Here is my issue:
I was able to deploy what I have to github in the link here: https://github.com/nknauer/nknauer
How do I view my blog now and share that url? I can't seem to open it.
I did everything such as:
install_hugo()
blogdown::serve_site()
But I am kind of stuck at this point.
Any help would be great, thanks
Well, netlify is critical unless you want to host your website with GitHub pages. So you could follow the netlify documentation to set up your site and point to your GitHub repository. Alternatively, you could stick with GitHub pages, which means you need to change your repository name to nknauer.github.io and switch GitHub pages 'on' in your repository settings.
Some more info from the blogdown docs:
netlify: https://bookdown.org/yihui/blogdown/netlify.html
GitHub pages: https://bookdown.org/yihui/blogdown/github-pages.html
I had recently posted a question about the deployment of my blogdown based website here. I was not exactly following the instructions in the blogdown book, but I got the issue resolved - thanks to the answer by Yihui.
I am trying to load my website exactly as instructed in the documentation. So, I have now the entire project in my git repo and I am using the options in netlify as mentioned in the documentation, i.e., Build command: option set to hugo, Publish directory: set to public and HUGO_VERSION set to 0.30 in deploy settings.
I am getting successful deployment (in netlify) and the site shows fine up at
https://typesetter-signs-43683.netlify.com/
but, my earlier url (from github pages)
https://sn248.github.io/
shows a 404 ,file not found error.
netlify does not give any deployment error and github page settings says that site is published. I get the favicon of the theme but nothing else, and I find this very perplexing!
I am suspecting, there is yet another crucial step that I am missing. Any pointers here would be very helpful!
Thanks, SN248
The site you built on Netlify is published on Netlify, and the address https://sn248.github.io/ only shows content published on GitHub.
GitHub Pages publishes the contents of your GitHub repo. If you have a Jekyll config file in there, it will build a Jekyll site based on that config, but otherwise it won't run any other builds. Without the build, there are no html files to host. For example, when you go to https://sn248.github.io/, GitHub pages looks for an index.html file in the root of your repo. It returns a 404, because the file is indeed not found.
The easiest solution is to stop using the sn248.github.io address, and use a Netlify address instead. You can change your current address to sn248.netlify.com by going to the site Settings > Site information and clicking the Change site name button. Then enter sn248 in the box and save.
If you want to keep using sn248.github.io, you'll have to build your site on GitHub. The is a more complex process than what you've done so far, but the blogdown docs do have fairly detailed instructions on how to do it, either by building locally, or by setting up Travis CI to build for you.
One last option is to request an Rbind address like sn248.rbind.io. The blogdown docs explain how this works, and link to full instructions in the Rbind support site. Basically, you start by filing an issue in the Rbind support repo to request an address.
I recently set-up a static-site using R blogdown package with Hugo theme 'kakawait/hugo-tranquilpeak-theme'. While everything works perfectly fine, I couldn't get disqus-plugin and social share-URLs to work. Site is hosted in Github Pages.
Tried changing config.toml settings and Disqus short-names, but couldn't make it work.
As you can see at the end of blog-article here, Disqus fails with error message "We were unable to load Disqus. If you are a moderator please see our troubleshooting guide." On the other hand, Social URLs (for the share icons at the end of blog) show-up in html with the baseURL prefix missing.
Disqus-Team has mentioned in one of their help pages that this normally happens when there are incorrectly-formatted JS variables.
In View-Source of my blog-article, this.page.url variable appears only with relative URL
this.page.url = '\/2017\/05\/tamilnadu-2016-election---a-data-story\/';
This is how social URLs are showing up along-side Twitter/Facebook/G-Plus icons in the page.
Twitter: https://twitter.com/intent/tweet?text=%2f2017%2f05%2ftamilnadu-2016-election---a-data-story%2f
Facebook: https://www.facebook.com/sharer/sharer.php?u=%2f2017%2f05%2ftamilnadu-2016-election---a-data-story%2f
G Plus: https://plus.google.com/share?url=%2f2017%2f05%2ftamilnadu-2016-election---a-data-story%2f
I think some issue in baseURL config setting is causing both the problems.
Thank you.
This is one of the many reasons why I don't recommend GitHub pages but Netlify. You can choose to publish with GitHub pages, but you always have to run blogdown::hugo_build() before you publish the site. See the blogdown documentation for more details.