Hi there,
Without knowing what your custom helper actually does, I guess you
could take this in a couple of directions:
- You could refactor it so that the functionality in the Custom Helper
Class is in the Model, If you have controller specific logic, then
perhaps you can create another
Vibhor you are missing Jeroen's point.
Calling action helpers inside models would be a poor design decision.
The model should not need anything that isn't supplied to it by the
code calling it.
Having an action helper which provides a large amount of functionality
would be putting too much
Hello Jorean,
Thanks for your reply.
Let me explain you my case. Hope it helps.
I have made a custom Helper file that is used by many controller files in a
modular ZF application. So I have placed it in a folder at the root level,
so that it can be accessed wherever necessary.
There i
Hi Vibhor,
I don't think it's good MVC to call action helpers (part of the
controller) directly from your model.
I would write the functionality (can you explain a bit what you want
to do), in separate classes in your library and wrap the action helper
around it for use in the controller.
