One last question
Is there any way how to skip next filter?
I have a condition and I need my next filter (settings) not to be
executed if the result is false
I was thinking about setting some parameter to the request but I'd
appreciate some native symfony way (sth. like $filterChain-
>skipAn
Thank you
Exactly what I needed to hear ...
I've read about Filters and everything works now :)
Thank you again
On 3. Sep., 11:31 h., CaffeineInc wrote:
> I would suggest reading the filter chapter again.
>
> On Sep 2, 8:56 pm, javo wrote:
>
> > Hi there,
>
> > I've read many Symfony docs and
I would suggest reading the filter chapter again.
On Sep 2, 8:56 pm, javo wrote:
> Hi there,
>
> I've read many Symfony docs and tried to explore Symfony code but I
> can't figure out where can I put some code that will be executed by
> every module/action (something like frontendConfiguration.c
You should take a look at the symfony Routing Classes if your Criteria
is based on the url (sfRoute / sfPropelRoute). There you can catch the
url and do your database logic... Note, every defined route should
then use that class ;)
Or you should take a look at symfony Filters (sfFilter)
http://ww
I don't know what you want to do, but you can try in myUser.class.php
something like
class myUser extends sfBasicSecurityUser
{
public function initialize(sfEventDispatcher $dispatcher, sfStorage
$storage, $options = array())
{
parent::initialize($dispatcher, $storage, $options);
// y
