Tracks | Problem editing actions

Problem editing actions

Posted: 25 April 2009 04:56 PM

[ Ignore ]

Newbie

Total Posts: 3

Joined 2009-04-25

Just upgraded Tracks from 1.6 to 1.7 and now I can’t edit my actions. When I click on the “update” button there is the usual spinning circle animation and then nothing happens. What could be causing this, and is there a fix?

I’m running Windows, though the Tracks installation is on my brothers server running linux and ruby/rails.

I also may add that it works perfectly when making the update through the mobile interface.

Thanks!

Reinier Balt

Posted: 04 May 2009 06:56 AM

[ Ignore ] [ # 1 ]

Sr. Member

Total Posts: 580

Joined 2006-10-05

there is probably an error message in your log file. Could you copy-and-past it here?

mirbogat

Posted: 06 May 2009 09:39 PM

[ Ignore ] [ # 2 ]

Newbie

Total Posts: 3

Joined 2009-04-25

This is what my log file states when I try to save an entry with a date:

ArgumentError (3 elements of civil date are necessary):

    /usr/lib/ruby/1.8/date.rb:650:in `new_with_hash'

    /usr/lib/ruby/1.8/date.rb:675:in `strptime'

    /app/models/preference.rb:30:in `parse_date'

    /vendor/rails/activerecord/lib/active_record/associations/association_proxy.rb:214:in `send'

    /vendor/rails/activerecord/lib/active_record/associations/association_proxy.rb:214:in `method_missing'

    /app/controllers/application.rb:225:in `parse_date_per_user_prefs'

    /app/controllers/todos_controller.rb:217:in `update'

    /vendor/rails/actionpack/lib/action_controller/base.rb:1253:in `send'

    /vendor/rails/actionpack/lib/action_controller/base.rb:1253:in `perform_action_without_filters'

    /vendor/rails/actionpack/lib/action_controller/filters.rb:617:in `call_filters'

    /vendor/rails/actionpack/lib/action_controller/filters.rb:610:in `perform_action_without_benchmark'

    /vendor/rails/actionpack/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue'

    /usr/lib/ruby/1.8/benchmark.rb:293:in `measure'

    /vendor/rails/actionpack/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue'

    /vendor/rails/actionpack/lib/action_controller/rescue.rb:136:in `perform_action_without_caching'

    /vendor/rails/actionpack/lib/action_controller/caching/sql_cache.rb:13:in `perform_action'

    /vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/query_cache.rb:34:in `cache'

    /vendor/rails/activerecord/lib/active_record/query_cache.rb:8:in `cache'

    /vendor/rails/actionpack/lib/action_controller/caching/sql_cache.rb:12:in `perform_action'

    /vendor/rails/actionpack/lib/action_controller/base.rb:524:in `send'

    /vendor/rails/actionpack/lib/action_controller/base.rb:524:in `process_without_filters'

    /vendor/rails/actionpack/lib/action_controller/filters.rb:606:in `process_without_session_management_support'

    /vendor/rails/actionpack/lib/action_controller/session_management.rb:134:in `process'

    /vendor/rails/actionpack/lib/action_controller/base.rb:392:in `process'

    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:183:in `handle_request'

    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:110:in `dispatch_unlocked'

    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:123:in `dispatch'

    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:122:in `synchronize'

    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:122:in `dispatch'

    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:132:in `dispatch_cgi'

    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:39:in `dispatch'

    /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel/rails.rb:76:in `process'

    /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel/rails.rb:74:in `synchronize'

    /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel/rails.rb:74:in `process'

    /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel.rb:159:in `process_client'

    /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel.rb:158:in `each'

    /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel.rb:158:in `process_client'

    /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel.rb:285:in `run'

    /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel.rb:285:in `initialize'

    /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel.rb:285:in `new'

    /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel.rb:285:in `run'

    /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel.rb:268:in `initialize'

    /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel.rb:268:in `new'

    /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel.rb:268:in `run'

    /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel/configurator.rb:282:in `run'

    /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel/configurator.rb:281:in `each'

    /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel/configurator.rb:281:in `run'

    /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/mongrel_rails:128:in `run'

    /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel/command.rb:212:in `run'

    /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/mongrel_rails:281

    /usr/bin/mongrel_rails:19:in `load

    /usr/bin/mongrel_rails:19

    Rendering /web/home/w00102/public/500.html (500 Internal Server Error)

Thanks!

Reinier Balt

Posted: 07 May 2009 05:31 PM

[ Ignore ] [ # 3 ]

Sr. Member

Total Posts: 580

Joined 2006-10-05

this looks like tracks cannot parse the date you entered in the form
* what date did you enter?
* what are your date preferences in tracks?

mirbogat

Posted: 07 May 2009 09:36 PM

[ Ignore ] [ # 4 ]

Newbie

Total Posts: 3

Joined 2009-04-25

I have now changed the way dates are formatted and it works as smooth as butter! When you pointed it out I remembered that I did change the the date format when upgrading from 1.6 to 1.7. After the installation I changed from YY/MM/DD to YYMMDD (which alas didn’t work as I had hoped). I have now changed it back.

Thanks for pointing it out to me!

Reinier Balt

Posted: 08 May 2009 06:59 AM

[ Ignore ] [ # 5 ]

Sr. Member

Total Posts: 580

Joined 2006-10-05

ok, so now we know Tracks does not handle invalid entry of dates very well. That is a bug. Could you create a bugreport for it?

‹‹ Unable to retrieve contexts using REST API (1.8-devel) Incorrect current date ››

Username:		Password:
	Remember Me?		forgot password?
You are here: Forum Home > Usage > Troubleshooting > Thread