On Nov 16, 4:27 pm, Marnen Laibow-Koser <[email protected]> wrote:
> No, I mean where did you *set* @tags, not where did you read it? within the tag_cloud action defined within the controller from which i was calling tag_cloud > That's pretty standard Rails. You can use a before_filter to remove the > duplication. will do, thanks > Doesn't look wrong to me. i suppose i was expecting tag_cloud to output the tags wherever it was called, and link back to the tag_cloud definition despite it being inserted into the view of an index action sort of like a 'create' action doesn't need a corresponding create.html.erb file in order to work, but i am understanding why it wasnt working that way now > Probably the same way you did with this one. yes, i have it all more or less working correctly across models now > It looks to me like you need a review of basic Rails practices. probably a wise idea...ive been teaching myself rails when i have the time by diving in and trying to do things with it. but it would be smart to study the API a bit further thanks again -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
