-
Notifications
You must be signed in to change notification settings - Fork 26k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
RSS feed no longer generated #417
Comments
feed.xml is generated with the Jekyll Feed plugin so make sure that's properly working and installed. The bit in If you have a public repo I can give you a better idea of what could be setup wrong. |
Uncommented the gems:
- jekyll-paginate
- jekyll-sitemap
- jekyll-gist
- jekyll-feed
- jemoji Fixed in |
I'm having this problem, I don't know what's going on. I checked
And in
But there is no |
So I browsed a bit, saw this and got the idea that I should use
Now it works. What is the difference between |
Both should work. There was an update to Jekyll a few releases (I forget which version) ago that changed
|
As per their docs
Smells like you're on an older version of Jekyll. |
Hmmm. No it's Jekyll 3.7.0. Strangely it outputs this warning when serving:
Nevertheless, if I use plugins and no gems, the feed.xml disappears. Perhaps it's a bug in the plugin. |
You're using Bundler correct (eg. That'll tell you really quick what versions of the gems you're using and verify you're on the latest. |
Yes, Looks all normal to me? Although I don't understand yet, why the gems have to be specified twice, once in |
Yeah looks fine to me. In my experience plugins are inconsistent with theme gems. I have no idea if it's gotten better with later releases or if it's up to the plugin to autoload. I err on the side of caution and just add them all to the |
Fix mmistakes#417 - Avoid appearance of dark border around visited code links in Safari.
bundle update
.bundle exec jekyll build
.Environment informations
github-pages
orjekyll
gem version: 89 (github-pages)Expected behavior
Feed.xml (or whatever is in
atom_feed.path
) is generated automatically like it used to be.Steps to reproduce the behavior
Simply build as normal.
The text was updated successfully, but these errors were encountered: