[Bug]: "undefined method `yaml_file?' for #<Jekyll::page @name="404.md"> in /_layouts/single/html #9553
Comments
|
This will be fixed by #9552. You'll need to wait for a new Jekyll release and for the GitHub pages gem to update. |
|
I'm facing exactly the same issue. When will this be released? Any plan? |
|
I'm also facing the same issue. Any plans to release the fix soon? |
|
Hi, academic-pages are all affected by this bug, any latest news to fix the bug soon? |
|
Adding my +1 to this, I also have a fork of academic-pages and I am affected by the bug. Is there any temporary workaround until the release comes out? |
|
+1 I am also facing this issue using the minimal mistakes template. |
1 similar comment
|
+1 I am also facing this issue using the minimal mistakes template. |
|
Liquid Exception: undefined method `yaml_file?' for #<Jekyll::Page @name="app.md"> in /_layouts/default.html |
|
While awaiting the fix - is there a workaround? |
|
Same error here. |
|
I've sorted it out using a custom GitHub Actions workflow. Under Settings > Pages > Build and deployment select Github Actions instead of the default Deploy From a Branch then choose (or create) a jekyll configuration. Here is what the file that i've used looks like : # This workflow uses actions that are not certified by GitHub.
# They are provided by a third-party and are governed by
# separate terms of service, privacy policy, and support
# documentation.
# Sample workflow for building and deploying a Jekyll site to GitHub Pages
name: Deploy Jekyll site to Pages
on:
# Runs on pushes targeting the default branch
push:
branches: ["main"]
# Allows you to run this workflow manually from the Actions tab
workflow_dispatch:
# Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
permissions:
contents: read
pages: write
id-token: write
# Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued.
# However, do NOT cancel in-progress runs as we want to allow these production deployments to complete.
concurrency:
group: "pages"
cancel-in-progress: false
jobs:
# Build job
build:
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v4
- name: Setup Ruby
uses: ruby/setup-ruby@8575951200e472d5f2d95c625da0c7bec8217c42 # v1.161.0
with:
ruby-version: '3.1' # Not needed with a .ruby-version file
bundler-cache: true # runs 'bundle install' and caches installed gems automatically
cache-version: 0 # Increment this number if you need to re-download cached gems
- name: Setup Pages
id: pages
uses: actions/configure-pages@v4
- name: Build with Jekyll
# Outputs to the './_site' directory by default
run: bundle exec jekyll build --baseurl "${{ steps.pages.outputs.base_path }}"
env:
JEKYLL_ENV: production
- name: Upload artifact
# Automatically uploads an artifact from the './_site' directory by default
uses: actions/upload-pages-artifact@v3
# Deployment job
deploy:
environment:
name: github-pages
url: ${{ steps.deployment.outputs.page_url }}
runs-on: ubuntu-latest
needs: build
steps:
- name: Deploy to GitHub Pages
id: deployment
uses: actions/deploy-pages@v4Hope this helps! |
|
Same error here. This error was raised this week. Last week, there was no problem building the pages: /usr/local/bundle/gems/jekyll-3.9.5/lib/jekyll/excerpt.rb:91: warning: Jekyll::Excerpt#yaml_file? at /usr/local/lib/ruby/2.7.0/forwardable.rb:154 forwarding to private method Jekyll::Page#yaml_file?
Liquid Exception: undefined method `yaml_file?' for #<Jekyll::Page:0x000056309be129f0> in /_layouts/default.html |
|
This should be fixed now. Via #9544 (comment). |
|
I did create a jekyll.yml file as described above. I got a Ruby error
The pages are building now after fix #9544 was applied. |
You probably should create your own file depending on the versions you are using. The fix is just a revert of jekyll-relative-links to version 0.6.1. So we will likely to expect the same dependency error should they consider upgrading the versions in the future. |
|
Without changing anything and pushing a build just now everything is back to working fine. Thank you to those who made the fix on this. |
Thanks jekyll folks for fixing jekyll/jekyll#9553
and others
Operating System
windows 10
Ruby Version
whatever github builds with
Jekyll Version
whatever github builds with
GitHub Pages Version
Latest
Expected Behavior
When I push code I except the build to not fail, it worked last week but something changed this week and it no longer builds
Current Behavior
it fails to build after pushing code to github
Relevant log output
Code Sample
I forked the repo: https://github.com/academicpages/academicpages.github.io
I had uploaded it to my own GitHub page and it worked fine, however this week I tried to make some changes and nearly went insane thinking I broke something, but after deleting my fork and reforking it still did not build. seeing as that original repo hasn't been changed in 5 years I do not think it was that.
The error seems to be something with the 404.md file or related to it, but I saw no use of that file anywhere that had been changed. specifically, the error above says in the single file in _layouts, but I see no mention of 404 in that file
The text was updated successfully, but these errors were encountered: