Why is my blogdown website not updating despite working locally? - r

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."

Related

'Visual Composer' plugin is outputting weird image links

Morning everyone, i'm having a super weird issue with my recent wordpress migration. I moved the (working) site to another webspace and i'm slowly running out of ideas (jk, already ran out).
Issue: After the migration, the plugin Visual Composer is outputting nonsense image links to the frontend that look like this: https://i.imgur.com/7RocCmE.png instead of the uploaded images url. Result: No images are showing on the frontend.
This issue only happens when i use the single image block provided by VC itself. Inputting an image the wordpress way, inside of a text block, works.
What could be the reason for this? i'm super thankful for any advice since i'm not a programmer.
I have already tried:
Enabling wp debug, not getting any errors
Installing different versions of Visual Composer, multiple times
Reinstalling Wordpress, multiple times
disabling all plugins
completely reinstalling and reuploading everything from scratch
different php versions
As I saw in your screenshot with the src attribute of your image and it has data-src attribute also, I think that it's because the new site (or maybe the new hosting) is using lazy load which will update all images source of the site to the lazy load image for better performance.
Lazy load images mean that the image won't load at the beginning, when you start to scroll down to each section, the images of this section will be loaded. In this way, the site will be optimized and won't load many resources at the beginning.
I think you can:
Check if there is any cache plugin installed, try to deactivate this plugin.
Check with the hosting provider if there is any cache setting installed, try to deactivate this setting also.
See if the image is working in the backend or not, if it's still loaded in the backend, I'm pretty sure that it's the cache issue. If it doesn't load in the backend, I think there is something wrong with your theme source code.
Compare the hosting environment, especially the PHP version of the old and new site to see if there is any differences.

Reveal.js slides generating 404 on GitHub Pages

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.

How to run a wordpress.com hosted website locally using docker?

Currently we have a WooCommerce webshop hosted on wordpress.com. This webshop was setup as a prototype and because of its succes we want to start developing the webshop further. We don't want to change the production website directly, but we want to develop inside a closed development environment (e.g. locally using docker).
I have tried to run the webshop locally by exporting all its data using the All-in-One WP Migration plugin. Afterwards I have created a docker environment with a wordpress and a mysql container. On the wordpress container I've also installed the All-in-One WP Migration plugin and I've imported all the data. It looked like this worked fine, but after a few clicks I saw that I could not navigate to any other URL besides the homepage. I have read online that the Wordpress codebase being used on wordpress.com differs from the default codebase which can be download on wordpress.org. So I think this means the wordpress.com export file can't be imported into a default wordpress container.
Because of this I've tried to download all the files on wordpress.com using FTP and run the website myself using a php container. This also didn't work, because I can't download all the files using FTP because of the permissions. I also contacted the support of wordpress.com, and they told me they couldn't sent me the contents of these files. But without these files, I don't know how I can run the wordpress.com website locally.
I hope someone can help me with getting the wordpress.com website to run locally in a development environment. A suggestion how we can implement a workflow where we can change the webshop in a development environment and deploy the changes to our production website is also very welcome.
Edit: For now I've chosen to run my site in a docker environment and write down all the changes I make locally. When I'm satisfied with the site locally, I will repeat the changes I made earlier on the production website. I've chosen this workflow because I don't really know the structures inside Wordpress. I don't know how I can migrate the files and database tables I need to switch theme, without overwriting the database tables I want to keep (e.g. WooCommerce orders table).
Have you tried running it on a localhost? MAMP is a good option for this.
https://www.mamp.info/en/

deploy blogdown in R

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

blogdown deployment newbie issue

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.

Resources