adamziel / Redmine-Todo-lists

Basecamp-like todo lists for redmine

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Syntax error

ptoly opened this issue · comments

todo_list_controller.rb:18: syntax error, unexpected '.', expecting kEND
.where('todo_lists.is_private

This is what I get when I try to access the ToDos tab.

curious! looks like this is relevant:
https://www.ruby-forum.com/topic/128509
could you play with indentation near that line a bit and post any results in here?

Did that. No luck.

On Mar 2, 2014, at 1:24 PM, Adam Zielinski notifications@github.com wrote:

curious! looks like this is relevant:
https://www.ruby-forum.com/topic/128509
could you play with indentation near that line a bit and post any results in here?


Reply to this email directly or view it on GitHub.

same error for me

I'll try to review it today or tomorrow

took me a while but I think I have a fix for that - could you check if it helps?

I'm afraid not. Here's what I get now:

todo_list_controller.rb:79: syntax error, unexpected '.', expecting kEND
.where(:project_id=>@project.id).each \

todo_list_controller.rb:87: syntax error, unexpected '.', expecting kEND
.where("todo_items.id in (?)", params[:items].keys())

todo_list_controller.rb:88: syntax error, unexpected '.', expecting kEND
.where(todo_lists: { project_id: @project.id }).each
^

and a bunch more.

If it helps I can send the whole output, I just don't want to put the url output in public, so if you give me an email...

I got your info about the bug persisting on new ruby version, I will try to track it down

I ended up updating to ruby 1.9.1 and it works!

On Mar 18, 2014, at 7:33 PM, Adam Zielinski notifications@github.com wrote:

I got your info about the bug persisting on new ruby version, I will try to track it down


Reply to this email directly or view it on GitHub.

Ah great to hear that! I am closing this issue then and will just update README

Thanks so much for your help!

On Mar 18, 2014, at 9:48 PM, Adam Zielinski notifications@github.com wrote:

Ah great to hear that! I am closing this issue then and will just update README


Reply to this email directly or view it on GitHub.

I just stumbled over this topic. I have the same error. would you please return investigating the error. Sadly i have no chance to upgrade to a higher Ruby version (using 1.8.7...) at the moment, because my provider won't...

I got stuck with that, I believe it is somehow related to ruby version but I don't know how or why :(