Netlify jekyll boilerplate new post not working

magnuspi · July 23, 2022, 1:54pm

The Jekyll blog boilerplate is not working with new posts.
Goto:

danurbanowicz/jekyll-netlify-boilerplate/blob/master/README.md

# Jekyll Netlify Boilerplate

*Note: Check out my [Eleventy Netlify Boilerplate](https://github.com/danurbanowicz/eleventy-netlify-boilerplate). It does pretty much the same as this project but uses the [Eleventy](https://www.11ty.io/) static site generator. It's fast, flexible and doesn't require Ruby.*

**A really simple Jekyll template for creating a fast, static website on Netlify with
a continuous deployment workflow.**

🔥 **This project is featured on Netlify's official [template showcase](http://templates.netlify.com/template/jekyll-with-netlify-cms-boilerplate/) and blog: [The top 10 Static Site Generators to watch in 2018](http://templates.netlify.com/template/jekyll-with-netlify-cms-boilerplate/)** 🔥

* Minimal styling, ready to make your own
* Example blog posts, pages and contact form
* Responsive CSS Grid layout with fallbacks for older browsers
* Continuous Deployment workflow via Netlify and Github
* Netlify CMS for managing content
* Netlify Identity for authenticating users
* Netlify Forms for processing your static HTML forms with reCAPTCHA
* Optional Netlify `_redirects` and `_headers` files ready to use
* Jekyll SASS pipeline
* Minified HTML and CSS

This file has been truncated. show original

Click “Deploy to Nettlify”.
Click “Save & Deploy”. Wait for the deploy.
Accept the identities invite sent to your email.
Go to your new site admin and login in my case it’s:
https://effervescent-dragon-54befd.netlify.app/admin
Add a new post. Publish.
In the following deploy log you will notice there are “0 new files to upload”.
The deploy added new a new .md file to github but no html was renderd or added to netlify:

Please advise on this issue!

2:48:44 PM: Build ready to start
2:48:46 PM: build-image version: 0e2f4c52031ab562db66aec633308326e3b108d0 (focal)
2:48:46 PM: build-image tag: focal
2:48:46 PM: buildbot version: 17781eb43cf82ba1890150fe75c9ab9320d6a721
2:48:46 PM: Fetching cached dependencies
2:48:46 PM: Starting to download cache of 114.6MB
2:48:47 PM: Finished downloading cache in 608.405085ms
2:48:47 PM: Starting to extract cache
2:48:48 PM: Finished extracting cache in 1.210843383s
2:48:48 PM: Finished fetching cache in 1.887731835s
2:48:48 PM: Starting to prepare the repo for build
2:48:48 PM: Preparing Git Reference refs/heads/master
2:48:49 PM: Parsing package.json dependencies
2:48:50 PM: Starting build script
2:48:50 PM: Installing dependencies
2:48:50 PM: Python version set to 2.7
2:48:50 PM: Started restoring cached node version
2:48:51 PM: Finished restoring cached node version
2:48:52 PM: v16.16.0 is already installed.
2:48:52 PM: Now using node v16.16.0 (npm v8.11.0)
2:48:52 PM: Started restoring cached build plugins
2:48:52 PM: Finished restoring cached build plugins
2:48:53 PM: Attempting ruby version 2.7.2, read from environment
2:48:54 PM: Using ruby version 2.7.2
2:48:54 PM: Using bundler version 1.16.1 from Gemfile.lock
2:48:55 PM: Successfully installed bundler-1.16.1
2:48:55 PM: 1 gem installed
2:48:55 PM: Using PHP version 8.0
2:48:55 PM: Started restoring cached ruby gems
2:48:55 PM: Finished restoring cached ruby gems
2:48:55 PM: Started restoring cached go cache
2:48:55 PM: Finished restoring cached go cache
2:48:55 PM: Installing Go version 1.17 (requested 1.17)
2:49:03 PM: unset GOOS;
2:49:03 PM: unset GOARCH;
2:49:03 PM: export GOROOT=‘/opt/buildhome/.gimme/versions/go1.17.linux.amd64’;
2:49:03 PM: export PATH=“/opt/buildhome/.gimme/versions/go1.17.linux.amd64/bin:${PATH}”;
2:49:03 PM: go version >&2;
2:49:03 PM: export GIMME_ENV=“/opt/buildhome/.gimme/env/go1.17.linux.amd64.env”
2:49:03 PM: go version go1.17 linux/amd64
2:49:03 PM: Installing missing commands
2:49:03 PM: Verify run directory
2:49:04 PM:
2:49:04 PM: ────────────────────────────────────────────────────────────────
2:49:04 PM: Netlify Build
2:49:04 PM: ────────────────────────────────────────────────────────────────
2:49:04 PM:
2:49:04 PM: ❯ Version
2:49:04 PM: @netlify/build 27.4.2
2:49:04 PM:
2:49:04 PM: ❯ Flags
2:49:04 PM: baseRelDir: true
2:49:04 PM: buildId: 62dbfc3c720c1400083a1a87
2:49:04 PM: deployId: 62dbfc3c720c1400083a1a89
2:49:04 PM:
2:49:04 PM: ❯ Current directory
2:49:04 PM: /opt/build/repo
2:49:04 PM:
2:49:04 PM: ❯ Config file
2:49:04 PM: /opt/build/repo/netlify.toml
2:49:04 PM:
2:49:04 PM: ❯ Context
2:49:04 PM: production
2:49:04 PM:
2:49:04 PM: ────────────────────────────────────────────────────────────────
2:49:04 PM: 1. build.command from netlify.toml
2:49:04 PM: ────────────────────────────────────────────────────────────────
2:49:04 PM:
2:49:04 PM: $ jekyll build
2:49:05 PM: Configuration file: /opt/build/repo/_config.yml
2:49:05 PM: Source: /opt/build/repo
2:49:05 PM: Destination: /opt/build/repo/_site
2:49:05 PM: Incremental build: disabled. Enable with --incremental
2:49:05 PM: Generating…
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/convertible.rb:41: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/convertible.rb:41: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/convertible.rb:41: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/convertible.rb:41: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/convertible.rb:41: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/convertible.rb:41: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/convertible.rb:41: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/convertible.rb:41: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/document.rb:449: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/document.rb:449: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/document.rb:449: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/document.rb:449: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/document.rb:449: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/convertible.rb:41: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/convertible.rb:41: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/convertible.rb:41: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/convertible.rb:41: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/convertible.rb:41: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/convertible.rb:41: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/tags/include.rb:194: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/tags/include.rb:194: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/tags/include.rb:194: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/tags/include.rb:194: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/tags/include.rb:194: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/tags/include.rb:194: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/tags/include.rb:194: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/tags/include.rb:194: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/tags/include.rb:194: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/tags/include.rb:194: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/tags/include.rb:194: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/tags/include.rb:194: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/tags/include.rb:194: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/tags/include.rb:194: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/tags/include.rb:194: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/tags/include.rb:194: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/tags/include.rb:194: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/tags/include.rb:194: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/tags/include.rb:194: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/tags/include.rb:194: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/tags/include.rb:194: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/tags/include.rb:194: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/tags/include.rb:194: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/tags/include.rb:194: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/tags/include.rb:194: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/tags/include.rb:194: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/tags/include.rb:194: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/tags/include.rb:194: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/tags/include.rb:194: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/tags/include.rb:194: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/tags/include.rb:194: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/tags/include.rb:194: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/tags/include.rb:194: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/tags/include.rb:194: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/tags/include.rb:194: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/tags/include.rb:194: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/tags/include.rb:194: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/tags/include.rb:194: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/tags/include.rb:194: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/tags/include.rb:194: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/tags/include.rb:194: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/tags/include.rb:194: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/tags/include.rb:194: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/tags/include.rb:194: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: /opt/build/cache/bundle/ruby/2.7.0/gems/jekyll-3.8.5/lib/jekyll/tags/include.rb:194: warning: Using the last argument as keyword parameters is deprecated
2:49:05 PM: done in 0.574 seconds.
2:49:05 PM: Auto-regeneration: disabled. Use --watch to enable.
2:49:05 PM:
2:49:05 PM: (build.command completed in 1.2s)
2:49:05 PM:
2:49:05 PM: ────────────────────────────────────────────────────────────────
2:49:05 PM: 2. Deploy site
2:49:05 PM: ────────────────────────────────────────────────────────────────
2:49:05 PM:
2:49:05 PM: Starting to deploy site from ‘_site’
2:49:05 PM: Creating deploy tree
2:49:05 PM: Creating deploy upload records
2:49:06 PM: 0 new files to upload
2:49:06 PM: 0 new functions to upload
2:49:06 PM: Site deploy was successfully initiated
2:49:06 PM:
2:49:06 PM: (Deploy site completed in 251ms)
2:49:06 PM: Starting post processing
2:49:06 PM:
2:49:06 PM: ────────────────────────────────────────────────────────────────
2:49:06 PM: Netlify Build Complete
2:49:06 PM: ────────────────────────────────────────────────────────────────
2:49:06 PM:
2:49:06 PM: (Netlify Build completed in 1.5s)
2:49:06 PM: Post processing - HTML
2:49:06 PM: Processing form - contact
2:49:06 PM: Caching artifacts
2:49:06 PM: Started saving ruby gems
2:49:06 PM: Finished saving ruby gems
2:49:06 PM: Started saving build plugins
2:49:06 PM: Finished saving build plugins
2:49:06 PM: Started saving pip cache
2:49:06 PM: Detected form fields:

name
email
phone
message
2:49:06 PM: Finished saving pip cache
2:49:06 PM: Started saving emacs cask dependencies
2:49:06 PM: Finished saving emacs cask dependencies
2:49:06 PM: Started saving maven dependencies
2:49:06 PM: Finished saving maven dependencies
2:49:06 PM: Started saving boot dependencies
2:49:06 PM: Post processing - header rules
2:49:06 PM: Finished saving boot dependencies
2:49:06 PM: Started saving rust rustup cache
2:49:06 PM: Finished saving rust rustup cache
2:49:06 PM: Started saving go dependencies
2:49:06 PM: Finished saving go dependencies
2:49:06 PM: Build script success
2:49:06 PM: Post processing - redirect rules
2:49:06 PM: Post processing done
2:49:08 PM: Uploading Cache of size 114.3MB
2:49:10 PM: Site is live
2:49:11 PM: Finished processing build request in 24.854024908s

hrishikesh · July 24, 2022, 12:33pm

Did you try to re-deploy? Not sure about Jekyll, but Hugo checks the date with the system date and doesn’t publish a page if it’s in the future. So maybe, due to timezone differences, the file didn’t get included?

magnuspi · July 24, 2022, 1:30pm

This seems to be the issue. Please can you suggest a fix? I did not make a local repo so the time difference seems to be between Netlify and GitHub. Please forgive my ignorance!

hrishikesh · July 24, 2022, 1:31pm

I did:

Go here: Netlify App, click on Trigger deploy.

magnuspi · July 25, 2022, 8:04am

Thanks for the suggestion but this does not fix the issue with new posts from admin not appearing until the time offset has been passed. If I am on GMT and github is recording a time of say 11:00 an admin would need to wait until Jekyll agrees it is 11:00 which if it is on PT is 8-9 hours (? I think) and then ask me to re-deploy from Netlify, as they don’t have access to it. This is not a fix and the bug is still a problem. How do I get rid of the time discrepancy altogether?

gualter · July 28, 2022, 2:25pm

Hello @magnuspi

You’ll need to enable the future flag on Jekyll options:

or build locally and Deploy with the CLI.

Hope this helps!

magnuspi · July 29, 2022, 4:07pm

@ gualter Thanks for your tip!

I’ve found setting the publish day to the previous day fixes the issue but explaining this to an admin is a bit clumsy.

I’d like to retain the jekyll future feature that does not publish future posts. I’m assuming this means admin are able to publish posts in admin that are not published (by jekyll on Netlify) until a future date?

So I’d like I am looking at using the CLI, should I build a new site or connect an existing site? Thanks in advance!

fool · July 29, 2022, 9:47pm

No need to use a separate site, it is ok to mix CLI + our automatic git builds for a site if you want to test out without setting up a new site. This has a benefit that the CLI, once you use netlify link, will also be able to use your environment variables already set in the netlify UI!

But, no problem using two sites, too.

magnuspi · August 27, 2022, 11:44am

Sorry for the delay in responding, I have been busy with other concerns. I have been using CLI and even when I deploy via the CLI the timezone offset bug is an issue. It seems Netlify/Github is treating the GMT dates as future dates and not considering the time offset. If I adjust the publish date manually to the previous day/8 hours ago the post is rendered on Jekyll build. I can work with this for now but admins might get caught out by it.

hrishikesh · August 27, 2022, 11:49am

Hi!

If this is happening when using CLI on your machine, this sounds more some problem with the tool (Jekyll in this case). If it’s happening on CLI using GitHub Actions - you need to check if it’s possible to set timezone on GitHub.

hrishikesh · August 27, 2022, 11:50am

Also, I believe you can set timezone on Netlify: