Don't forget, in most cases you want a Behavior (or Datasource) not a
Component (only if the component exists and writes data)
On Jan 29, 3:14 pm, Florian wrote:
> Thanks, to all.
>
> Worked with App::Import
>
> On 29 Jan., 08:55, "j0n4s.h4rtm...@googlemail.com"
>
> wrote:
> > While Miles J is r
Thanks, to all.
Worked with App::Import
On 29 Jan., 08:55, "j0n4s.h4rtm...@googlemail.com"
wrote:
> While Miles J is right in general, there are exceptions.
>
> This is how I used Emailcomponent from
> amodel:http://github.com/ionas/sna/blob/master/www/app/app_model.php#L98
> (1.2.5)
>
> I am n
While Miles J is right in general, there are exceptions.
This is how I used Emailcomponent from a model:
http://github.com/ionas/sna/blob/master/www/app/app_model.php#L98
(1.2.5)
I am not sure if an email datasource would be the best approach in
general (and the component as well as models could
You should not be using Components from your Model. If you are, then
your application structure is wrong.
There are if cases like the Email and Session component.
On Jan 28, 9:19 am, bujanga wrote:
> I have found 2 MVC use cases for this approach. One is to send email
> from a model and the othe
I have found 2 MVC use cases for this approach. One is to send email
from a model and the other is to send email from a shell task. Here is
how I go about it:
// IMPORT AND INITIALIZE EMAIL COMPONENT
App::import('Core', 'Controller');
App::import('Component', 'Email');
$this->Controller =& ne
you cant automatically use them
manual inclusion:
App::import('Component', 'My');
$this->My = new MyComponent();
...
On 28 Jan., 11:54, Florian wrote:
> Hi @ all,
>
> my Problem is that i can not call a component from a model.
>
> Source - Model:
>
> class Approval extends AppModel{
> $co
