I have this listed in the Toto Issues list on Git and know that it is affecting one other person and so far no ideas… just want to throw it out here if anyone else has had the issue or better yet has a fix:
I have a pretty stock instance of Toto. Locally I run it on thin and everything works. When I push it to heroku, the index loads but
on every article, instead of showing the date in the article file, it shows today’s date. This wrong date shows visually on the page and also in the links. So the links are all wrong and end in 404 errors. If I modify the link to the correct date of the article (in the article file), the article loads.
This is the header of the article file for this article:
title: Using wkhtmltopdf with Ruby and Rails
date: 2010-09-20
description: Pdf generation with wkhtmltopdf on Rails
I have this listed in the Toto Issues list on Git and know that it is
affecting one other person and so far no ideas... just want to throw it
out
here if anyone else has had the issue or better yet has a fix:
I have a pretty stock instance of Toto. Locally I run it on thin and
everything works. When I push it to heroku, the index loads but on every
article, instead of showing the date in the article file, it shows
today's
date.
[...]
I know nothing about Toto, but here's a wild guess. Are you using
something other than PostgreSQL for your development database? If so,
perhaps there's a SQL syntax issue in Toto...
I have this listed in the Toto Issues list on Git and know that it is
affecting one other person and so far no ideas… just want to throw it
out
here if anyone else has had the issue or better yet has a fix:
I have a pretty stock instance of Toto. Locally I run it on thin and
everything works. When I push it to heroku, the index loads but on every
article, instead of showing the date in the article file, it shows
today’s
date.
[…]
I know nothing about Toto, but here’s a wild guess. Are you using
something other than PostgreSQL for your development database? If so,
perhaps there’s a SQL syntax issue in Toto…
Thanks, actually Toto is database-less, just a rack app. It uses git as its datasource for blog posts which is pretty cool. Just that since starting to use this I spend more time figuring out what I have done wrong in Toto than writing anything to post
A month later, I just fought this same issue, so here is the solution
for the foggy sands of time and Google. It's based on Heroku's
version of 1.8.7 being at a patchlevel in which the YAML parser parses
strings that look like dates into dates; toto wants strings. heroku
stack:migrate bamboo-mri-1.9.1 and away you go.