search

remi-daigle / studyGroup

http://r-bar.ca
Other
0 stars 1 forks source link

r-bar not displaying events #31

Closed DanielleQuinn closed 8 years ago

DanielleQuinn commented 8 years ago

I've gone through all of the new posts and issues that have been added since the r-bar site events have stopped showing up, and checked it all out for problems with no luck

Still not appearing... if you have a chance could you take a peek? I've tried taking out punctuation that might be messing things up, shortening text, etc. and have looked into tutorials etc that might be able to point me in the right direction but I can't seem to figure out why things won't post. Hmm.

DQ

paleolimbot commented 8 years ago

I cloned the site and built it locally using jekyll with the same results...no error messages!

dravery commented 8 years ago

So what does that mean ;-) ?? I'm happy to host the site however. There is an acadia overlay on things as well that took Remi a bit to sort with the tech services folks. If they change something, it may affect the site.

trev

On 3/30/2016 6:24 PM, Dewey Dunnington wrote:

I cloned the site and built it locally using jekyll with the same results...no error messages!

— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub https://github.com/remi-daigle/studyGroup/issues/31#issuecomment-203641510

remi-daigle commented 8 years ago

It has 'something' to do with the Jekyll version. Github now uses Jekyll 3.0.3, and I have 2.5.3 on my machine and it build properly using the old version... just need to figure out what is getting broken by the the new version. I can't look at this for a few days though!

rystanley commented 8 years ago

Strange that a new version would create this issue. My expertise (ahem google) didn't turn up much, but I am a bit of a lame duck for the layout stuff. I might also have a previous version of Jekyll on my older Surface.

remi-daigle commented 8 years ago

not that I actually read this, but I remember this popping up on my GitHub notifications a while back http://jekyllrb.com/docs/upgrading/2-to-3/

paleolimbot commented 8 years ago

good eye @remi-daigle ...the problem was a change in the default option for future in the _config.yml file (see http://jekyllrb.com/docs/upgrading/2-to-3/#future-posts). The solution was to put future: true in _config.yml