My app has a form with several dates and datetimes in it in the format
dd/mm/ or dd/mm/ HH:MM. These worked fine in my local
development environment (using postgresql) but it causes 500 errors
once posted to heroku.
I've come across a few suggestions for how to deal with this on the
web
I'm not entirely sure but is your problem related to this issue -
http://github.com/ricardochimal/taps/issues#issue/25
Using ruby 1.8.7 with taps produced better results for me that 1.9.1.
Perhaps try that.
On Jun 26, 2:40 am, lsiden lsi...@gmail.com wrote:
I am having the same problem
I am trying to install routing filter gem in my app, the problem with
routing filter is the gem name is different from lib file name, this is how
I use it from environment.rb
config.gem routing-filter, :version = '0.0.1', :lib = 'routing_filter'
what will be the equivalent line in .gems file ?
Facing a couple of other issues.
Do I need to specify all the gems I am using in my specs too ? Because my
rake tasks are failing saying cucumber is not in path.
Regards,
Amiruddin Nagri
On Sat, Jun 26, 2010 at 10:53 PM, Amiruddin Nagri amir.na...@gmail.comwrote:
I am trying to install
The issue seems to be I have a lot of rake tasks which are related to
running specs. All these rake files are in lib/tasks folder.
Should I keep them somewhere else ?
Regards,
Amiruddin Nagri
On Sat, Jun 26, 2010 at 10:53 PM, Amiruddin Nagri amir.na...@gmail.comwrote:
I am trying to install
Hi,
I had a field called main_entity_id on a query table on heroku, which
I hence renamed to entity_id in dev. I have pushed the new code out to
heroku but the schema still has main_entity_id and fails in different
places. For example:
ActiveRecord::StatementInvalid (PGError: ERROR: column
Was working fine until I upgraded MongoMapper. I have installed 'thin'
locally and everything works. It also works in production mode locally
but I get this error when I try to load the app in heroku:
App failed to start
An error happened during the initialization of your app.
This may be due
On Jun 24, 2010, at 7:56 PM, Jesse wrote:
http://github.com/jtrupiano/rack-rewrite/issues/#issue/7
I've replied inline on GitHub:
http://github.com/jtrupiano/rack-rewrite/issues/#issue/7/comment/288774
## config/environments/production.rb (fails)
config.gem 'rack-rewrite', '1.0.0'
require
I'm having encoding problems on heroku, where I can't fetch unicode
from the database.
I've setup a simple program following the steps in the first demo in:
http://rubyonrails.org/screencasts (except I use postgres instead of
sqlite)
So my site has some pages that are just barely more than
Actually, the problem is the inverse of what I describe below: the db schema
is fine - but ActiveRecord::Base#save! is seeing my query type as having a
main_entity_id in production, whereas it works correctly locally. I am using
the bamboo stack. I dont have any reference to queries#main_entity in
I just fixed this.
I was on a heroku stack that had unicode issues (bamboo-mri-1.9.1
(beta)) I'm not having problems after migrating to bamboo-ree-1.8.7.
On Jun 26, 12:21 am, JL jlee.j...@gmail.com wrote:
I'm having encoding problems on heroku, where I can't fetch unicode
from the database.
11 matches
Mail list logo