Application helper problema

I am calling a function I made in application_helper but when I try to
call it it keeps saying method undefined. If I put the function in
the controller it runs just fine. any ideas?

did you mean when you put it in your controller’s helper file, it works?

make sure you are using your helpers in your views, and not in your
controller.

Chris H. wrote:

I am calling a function I made in application_helper but when I try to
call it it keeps saying method undefined. If I put the function in
the controller it runs just fine. any ideas?

Should have used Hamburger Helper.

I think application.rb doesn’t reload unless you restart the server.
Maybe
application_helper is the same way

and it looks like this post agrees:

Plugins - helper function is an "undefined method", Objects "can't be referred" - Rails - Ruby-Forum

On Fri, Feb 6, 2009 at 11:30 PM, Eddie S.
<[email protected]

wrote:

the controller it runs just fine. any ideas?


Posted via http://www.ruby-forum.com/.


Available for Ruby on Rails development opportunities

That sounds strange. All controllers reload, therefore application
controller does too, because it’s an abstract class.

Blog: http://random8.zenunit.com/
Learn rails: http://sensei.zenunit.com/

OK, so you can only call functions in a controller that are in a
model?

I have an app that does not have a model but I guess I can create one
if need be.

Where are you trying to call it from? Helpers are for views

Blog: http://random8.zenunit.com/
Learn rails: http://sensei.zenunit.com/

On 07/02/2009, at 6:30 PM, Eddie S. <rails-mailing-list@andreas-

On Feb 7, 1:28 pm, Me [email protected] wrote:

OK, so you can only call functions in a controller that are in a
model?

You can call methods from pretty much anywhere, but that is not the
point. In Rails, you want to follow their MVC pattern to get the most
of the framework.You want to call methods within the scope of where
you are at.

The browser requests go from Dispatcher → Controller → View

The purpose of the controller is to get the request, maybe validate
the user, then instantiate an object that will be rendered in the
view. That’s it. Any logic about the specifics of how to instantiate
the object should be handled by the model classes. So in that part,
you are correct when you say “only call functions in a controller that
are in a model”. You are making a call to instantiate an object that
will be used in the view.

The model classes usually have a database back end but it does not
have to be. It is common to have model classes for specialized reports
for example, that have aggregation methods, etc. So you should create
a model class for what you are trying to do, to separate those methods
in their own domain.

Finally, the purpose of the Helper classes is to provide methods for
the View. When you need to format something, etc. you put call methods
in either the controller_helper class or the generic application
helper class.

Hope that helps.