Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

New posts not showing in Chrome due to caching! #641

why-el opened this Issue Sep 16, 2012 · 9 comments


None yet
4 participants

why-el commented Sep 16, 2012

I have been having this problem for a while now. I push a new post to github pages, I receive an email saying the page was built, but when I check the site, I don't see the new content unless I hit command shift R, which in Chrome reloads the page from the server. Clearing the cache also solves the problem.

This is really a hassle. Anyone facing a similar issue?

I have the same issue, however dumping cache/history doesn't solve this nor does performing a hard refresh ( cmd + shift + r )

why-el commented Oct 13, 2012

Strange. Usually I just do a hard refresh! According to their support, GitHub sets the cache to expire after one day, which is really not good for sites that push multiples pages a day, like mine.

Ah, I didn't realize that they set the cache to 24 hours. Hopefully it'll show up in the next 8 hours 👍


mattr- commented Oct 15, 2012

This isn't really an issue with Jekyll but with GitHub Pages. Please write support@github.com instead. Thanks!

Talked with github support, they found on my blog an error in the post. If it helps run this cmd to test the blog

jekyll --safe --no-lsi --pygments --no-server --no-auto

When I run this, I get

/Users/andredublin/.rvm/gems/ruby-1.9.3-p194@myblog/gems/jekyll-0.11.2/lib/jekyll/convertible.rb:81:inrescue in do_layout': undefined method name' for <Post: /2012/10/13/beginning-rack>:Jekyll::Post (NoMethodError) from /Users/andredublin/.rvm/gems/ruby-1.9.3-p194@myblog/gems/jekyll-0.11.2/lib/jekyll/convertible.rb:78:indo_layout'
from /Users/andredublin/.rvm/gems/ruby-1.9.3-p194@myblog/gems/jekyll-0.11.2/lib/jekyll/post.rb:189:in render' from /Users/andredublin/.rvm/gems/ruby-1.9.3-p194@myblog/gems/jekyll-0.11.2/lib/jekyll/site.rb:193:inblock in render'
from /Users/andredublin/.rvm/gems/ruby-1.9.3-p194@myblog/gems/jekyll-0.11.2/lib/jekyll/site.rb:192:in each' from /Users/andredublin/.rvm/gems/ruby-1.9.3-p194@myblog/gems/jekyll-0.11.2/lib/jekyll/site.rb:192:inrender'
from /Users/andredublin/.rvm/gems/ruby-1.9.3-p194@myblog/gems/jekyll-0.11.2/lib/jekyll/site.rb:40:in process' from /Users/andredublin/.rvm/gems/ruby-1.9.3-p194@myblog/gems/jekyll-0.11.2/bin/jekyll:250:in<top (required)>'
from /Users/andredublin/.rvm/gems/ruby-1.9.3-p194@myblog/bin/jekyll:19:in load' from /Users/andredublin/.rvm/gems/ruby-1.9.3-p194@myblog/bin/jekyll:19:in

from /Users/andredublin/.rvm/gems/ruby-1.9.3-p194@myblog/bin/ruby_noexec_wrapper:14:in eval' from /Users/andredublin/.rvm/gems/ruby-1.9.3-p194@myblog/bin/ruby_noexec_wrapper:14:in'`

I've gone through and removed what I thought might be incorrect syntax. But still no luck...

So found my syntax errors {% highlightruby %} should be {% highlight ruby %} doh!


mattr- commented Oct 15, 2012

Glad you found the error. Would you be so kind as to close this issue please, since its resolved now? Thanks!


mattr- commented Oct 15, 2012

@dublinan never mind. You can't actually close this issue.

@why-el Since this isn't really a Jekyll issue, would you mind closing it? Thanks!

why-el commented Oct 15, 2012

Sure thing.

@why-el why-el closed this Oct 15, 2012

@jekyllbot jekyllbot locked and limited conversation to collaborators Feb 27, 2017

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.