Extracted source (around line #17):
14: <%= link_to 'Add to Cart',
15: {:action => 'add_to_cart',
16: :id => product },
17: class => 'addtocart' %>
18: </br>
19: </td>
20: </tr>
Trace of template inclusion: /app/views/store/index.rhtml
I've compared what I have with the book and they seem the same. I'm
thinking that either I'm missing something (very possible) or maybe the
error is actually being generated somewhere else but I'm very green (a
newbie)...
Does anyone have any ideas?
b
--
Posted via http://www.ruby-forum.com/.
This is better posted to the Rails list:
http://lists.rubyonrails.org/mailman/listinfo/rails
-austin
--
Austin Ziegler * halos...@gmail.com
* Alternate: aus...@halostatue.ca
> I am doing a tutorial from the Thomas~Hansson book and am getting this
> error:
>
> Extracted source (around line #17):
>
> 14: <%= link_to 'Add to Cart',
> 15: {:action => 'add_to_cart',
> 16: :id => product },
> 17: class => 'addtocart' %>
> 18: </br>
> 19: </td>
> 20: </tr>
You are missing one character from the book. On the last line it's
":class", not "class". The latter is a reserved word in Ruby with
special meaning, thus the problem.
Hope that helps.
James Edward Gray II
> On 13/01/06, bimo remus <bmor...@yahoo.com> wrote:
>> I am doing a tutorial from the Thomas~Hansson book and am getting
>> this
>> error:
>>
>> Extracted source (around line #17):
>>
>> 14: <%= link_to 'Add to Cart',
>> 15: {:action => 'add_to_cart',
>> 16: :id => product },
>> 17: class => 'addtocart' %>
>> 18: </br>
>> 19: </td>
>> 20: </tr>
>>
>> Trace of template inclusion: /app/views/store/index.rhtml
>>
>> I've compared what I have with the book and they seem the same. I'm
>> thinking that either I'm missing something (very possible) or
>> maybe the
>> error is actually being generated somewhere else but I'm very
>> green (a
>> newbie)...
>
> This is better posted to the Rails list:
>
> http://lists.rubyonrails.org/mailman/listinfo/rails
Is it, this time?
I know this has become our standard response, but the issue above is
a Ruby syntax mistake. It has nothing to do with Rails. Is that not
squarely in our area of expertise here?
I'm not trying to be argumentative. I'm honestly trying to
understand when we should forward them and when we should not.
James Edward Gray II
By the way, you will be doing yourself a service to get a text editor
that includes syntax highlighting for Ruby and rhtml. Little mistakes
like this will be much easier to spot.
I know jEdit, Textmate and RadRails all support rhtml highlighting.
Jon
--
Jonathan Leighton
http://turnipspatch.com/ | http://jonathanleighton.com/ | http://digital-proof.org/
As well as the closing brace after 'addtocart'
Caleb
No, I don't think so. Here's the call again:
> <%= link_to 'Add to Cart', {:action => 'add_to_cart', :id =>
> product }, class => 'addtocart' %>
Don't let that second Hash argument throw you.
James Edward Gray II
> On Sat, 2006-01-14 at 06:20 +0900, James Edward Gray II wrote:
>
> By the way, you will be doing yourself a service to get a text editor
> that includes syntax highlighting for Ruby and rhtml. Little mistakes
> like this will be much easier to spot.
>
> I know jEdit, Textmate and RadRails all support rhtml highlighting.
>
> Jon
>
Speaking of which, I'll have to get a multimode.el for XEmacs somewhere.
Making rhtml-mode shouldn't bee too difficult.
David Vallner
It did! Oh well, it's Friday.
Caleb
Yes, it's a Ruby syntax mistake. However, it's *not* code that's
runnable without Rails.
Not only is it Friday, but it's the thirteenth ;)
> On 13/01/06, James Edward Gray II <ja...@grayproductions.net> wrote:
>> On Jan 13, 2006, at 3:17 PM, Austin Ziegler wrote:
>>> This is better posted to the Rails list:
>>> http://lists.rubyonrails.org/mailman/listinfo/rails
>> Is it, this time?
>>
>> I know this has become our standard response, but the issue above is
>> a Ruby syntax mistake. It has nothing to do with Rails. Is that not
>> squarely in our area of expertise here?
>
> Yes, it's a Ruby syntax mistake. However, it's *not* code that's
> runnable without Rails.
I see a lot of code posted here that requires external libraries and
we fix that. Is there a reason Rails is different?
James Edward Gray II
I'd say that it's the fact that Rails already has a large support
community that we should point them in that direction. A lot of
libraries aren't as easily supported, as if the developers may not get
to the questions in a timely fashion, etc etc.
I think though it seems a bit harsh, sending people to the Rails
mailing list actually does a service, rather than a disservice. If
they did not know it existed before, they find a great new resource,
otherwise, they just know where to ask next time.
Though, I usually try to offer whatever help I can with a question,
THEN point people to the rails list, just to be nice ;)
If a person wants to use Rails to build their web app and they aren't
interested in the Ruby that Rails is built in, I'm comfortable with
that. Referring them to the Rails list where they can talk Rails
without having to filter out all of the noise about that "Ruby" thing is
the best we can do.
If, on the other hand, they want to fix up some Ruby code or learn more
about what makes Rails tick then I think they've come to the right
place. I'll be surprised on the day that I see this list turn someone
away that needs help with their Ruby code just because it's for use in a
Rails app.
Matthew
It kind of reminds me of M. Bison in street fighter.
Though it would be interesting if I were a google project.
My pockets are not overflowing with money, so i know that can't be true ;)
I'm not sure, but I think a good slogan would be, "What can
Brown do for you?"
Hal
A google / UPS merger in the works? I doubt I'd be creative enough to
figure that one out ;)
Oh, is that UPS? I thought it was Ex-Lax. :D
Hal