Welcome Guest Login Register Member List
ExpressionEngine Forums
Advanced Search
Username: Password:
Remember Me? forgot password?
You are here: Forum Home  >  Installation  >  Windows  >  Thread
   
 
Problem with recurring actions
 
mcraven
Posted: 23 April 2009 08:07 PM   [ Ignore ]  
Newbie
Rank
Total Posts:  10
Joined  2009-04-02

Have install Tracks 1.7 on Windows Server 2003 without any problems. Accessing it though the browser on the localhost. Everything seems to be working OK except when I click on the “Manage recurring actions” button. When I do the attached error is displayed. Any idea what is going wrong?

Regards,
Mark C.

Image Attachments  Action Controller_ Exception caught.jpg
Click thumbnail to see full-size image
Profile
 
Reinier Balt
Posted: 23 April 2009 09:01 PM   [ Ignore ]   [ # 1 ]  
Sr. Member
RankRankRankRank
Total Posts:  578
Joined  2006-10-05

The error is difficult to read, but I think it complains about Time. This is part of ruby. What version of ruby are you using?

Profile
 
mcraven
Posted: 23 April 2009 09:59 PM   [ Ignore ]   [ # 2 ]  
Newbie
Rank
Total Posts:  10
Joined  2009-04-02

I am using Ruby 186-26 and Gems 1.3.2. If I back Gems back down to 1.3.1 recurring actions now work. Ruby Gems 1.3.2 was just released on April 15th so there may be issues with Tracks that had not yet been found.

Regards,
Mark C.

Profile
 
Reinier Balt
Posted: 24 April 2009 06:33 AM   [ Ignore ]   [ # 3 ]  
Sr. Member
RankRankRankRank
Total Posts:  578
Joined  2006-10-05

I’ll look into this. Thanks.

Profile
 
technodolt
Posted: 27 April 2009 07:03 PM   [ Ignore ]   [ # 4 ]  
Newbie
Rank
Total Posts:  1
Joined  2009-04-27

Two things:

This is a bug in Rubygems 1.3.2 on Ruby 1.8.*, not a bug in Tracks.  You can fix it by editing rubygems/specification.rb (wherever that is on your system; I run MacOS so it’s under /Library/Ruby/Site/1.8) and changing the line that contains location_of_caller to instead contain Gem.location_of_caller.

Secondly, the reason for this whole mess is that the function Time.today is provided by Rubygems, not by Ruby, and is being deprecated in Rubygems because Ruby 1.9 added this into the core.

Basically, Tracks needs to implement its own Time.today function, or it will be completely broken when Rubygems 1.4 comes out and doesn’t contain the function at all, instead of containing it with a broken deprecation function.

Also, will comment the same thing on the thread on the ticket.

Profile
 
Reinier Balt
Posted: 03 May 2009 08:06 PM   [ Ignore ]   [ # 5 ]  
Sr. Member
RankRankRankRank
Total Posts:  578
Joined  2006-10-05

thanks for the info. I’ve replaced the usage of Time.today (was only used at the recurring todos) with regular Time function.

Profile
 
kevina047
Posted: 03 November 2009 06:43 PM   [ Ignore ]   [ # 6 ]  
Newbie
Rank
Total Posts:  1
Joined  2009-11-02

Reiner: In what version is your change applied?  I am having the same issue on DreamHost using Tracks 1.7stable.  thanks.

Profile
 
Reinier Balt
Posted: 04 November 2009 08:30 AM   [ Ignore ]   [ # 7 ]  
Sr. Member
RankRankRankRank
Total Posts:  578
Joined  2006-10-05

it is in 1.7.1devel. This tree still needs to be released (where is the time if you need it grin ) But you can download it from github if the bug is bugging you…

Profile
 
   
 
 
‹‹ I’ve downloaded the files for 1.7, Now what?      Issues with Exporting in Tracks 1.7 ››

Powered By ExpressionEngine
Template Design By Sonnenvogel.com
Select a theme:

ExpressionEngine Discussion Forum - Version 2.1.2 (20091002)
Script Executed in 0.1216 seconds

Atom Feed
RSS 2.0