I hope you read what I wrote: $this->_set(...)! Don't forget the underscore 
before the "set"! ;-) Or did I miss something?


Cheers, Daniel

Sent from my iPhone

On Aug 4, 2010, at 4:03 AM, Tristan <tristan.bessou...@gmail.com> wrote:

> (daniel Lohse, we tryed $this->set('is_activated', true);   is the
> synthax wrong ?)
> 
> Ok, it took 3 men (2 symfony experts, and me (but i'm a beginner) to
> bypass that)
> 
> We tested every possible solution with that function before giving up
> and writing
> 
> - a batch custom action
> - plus a function like this :
> 
> public function set($param,$val,$load=true)
>                    {
>                      if($param == 'is_activated')
>                      {
>                        if ($this->is_activated == false && $val == true)
>                            {
>                                    $context = sfContext::getInstance();
>                                    $context->getConfiguration()-
>> loadHelpers('Partial');
> 
>                                    $email = $this->getSfGuardUser()-
>> getProfile()->getEmail();
> 
>                                    $message = $context->getMailer()->compose(
>                                            'no-re...@jojo.com',
>                                           $email,
>                                            'your offer has been published /
> votre offre à été publiée',
>                                            get_partial('newsletter/
> activation_offre')
>                                            );
> 
>                                    $message->setContentType('text/html');
>                                    sfContext::getInstance()->getMailer()-
>> send($message);
> 
>                            }
>                      }
>                      parent::set($param,$val,$load);
>                    }
> 
> The symfony experts said that the bug is caused by the backend
> administration (it involves symfony itslef, not me :D)
> 
> -- 
> If you want to report a vulnerability issue on symfony, please send it to 
> security at symfony-project.com
> 
> You received this message because you are subscribed to the Google
> Groups "symfony users" group.
> To post to this group, send email to symfony-users@googlegroups.com
> To unsubscribe from this group, send email to
> symfony-users+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/symfony-users?hl=en

-- 
If you want to report a vulnerability issue on symfony, please send it to 
security at symfony-project.com

You received this message because you are subscribed to the Google
Groups "symfony users" group.
To post to this group, send email to symfony-users@googlegroups.com
To unsubscribe from this group, send email to
symfony-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en

Reply via email to