al-folio: Blog post is not showing
Acknowledge the following
- I carefully read and followed the Getting Started guide.
- I read through FAQ and searched through the past issues, none of which addressed my issue.
- The issue I am raising is a potential bug in al-folio and not just a usage question.
[For usage questions, please use gitter chat instead of raising an issue.]
Describe the bug
I created a copy of the website and migrate everything from my old blog. I run bundle exec Jekyll serve
and checked the local pages and it looks perfect. But when I put it onto the page, I found that everything works still great except the blog section where I cannot find my post.
I checked my naming of file and it’s in the right form I believe: 2020-08-23-summary.md
, where the date is same as what is included in the heading:
---
layout: post
title: xxx
date: 2020-08-23 11:12:00-0400
---
I also put one of the sample posts in the repository to _posts
and run bundle exec jekyll serve
before pushing it but same issue happened.
System (please complete the following information):
- OS: Mac OS X 10.15
- Browser (and its version): Chrome 87, Firefox, Safari
- Jekyll version: 3.9.0
- Ruby version: 2.7.0
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 21 (2 by maintainers)
Commits related to this issue
- try settings baseurl to fix missing blog posts in home page (see here - https://github.com/alshedivat/al-folio/issues/150#issuecomment-754196985) — committed to antony-scott/antony-scott.github.io by antony-scott 2 years ago
- Try solution from https://github.com/alshedivat/al-folio/issues/150 — committed to tostenzel/tostenzel.github.io by tostenzel a year ago
This solution worked for me:
I still can’t figure out why it works on the local server and doesn’t on the github server. For some reason
{% for post in paginator.posts %}
in blog/index.html doesn’t iterate on anything.Thanks for the workaround @taxminion your approach works. I forked the latest
al-folio
repo, renamed it, cloned it, migrated all the required content (_pages
,_posts
,_projects
,assets/img
) from the broken repo to the new clone repo folder, updated the_config.yml
file (also changed thebaseurl
from “/al-folio” to the renamed repo name) and finally deployed it using./bin/deploy
(without-u|--user
flag). All the pages are working now.@alshedivat @underdogliu @taxminion Thanks for the input guys!
When I created a new clone it didn’t work until I had changed
baseurl
in_config.yml
to the name of the GitHub repository. I also had to use./bin/deploy
without the--user
flag (I am on Windows) to deploy to github pages. I had to redo my blog from scratch, but that didn’t take long, and now everything is working perfectly. Hopefully that can fix everyone else’s blogs. Thank you alshedivat for your help!