removal.md

The RemoveListener

By default, only the DBAL layer of doctrine is needed to run this bundle. This is because Acl does not use the ORM but plain queries for performance reasons. If you however choose to use Doctrine ORM, there are some more handy features this bundle brings along.

Inherently, Acl entries won't be deleted once the corresponding domain object is removed (default behaviour of the bundle). The OneupAclBundle comes with a RemoveListener which does this, if you enable it.

Turn on acl removal in configuration

Do so by setting the remove_orphans setting to true. So if you have the ORM installed, the acl entires will be automatically deleted.

# app/config/config.yml

oneup_acl:
    remove_orphans: true

Turn on acl removal for specific entity

You can use the DomainObject annotation to enable acl removal for a specific entity type if you disabled remove_orphans by configuration.

<?php

namespace Acme\DemoBundle\Entity;

use Oneup\AclBundle\Annotation as Acl;

/**
 * @Acl\DomainObject(remove=true)
 */
class Product
{
}

In this case Acl entries for the domain object Product will be deleted from database, if the entity gets deleted. Entries belonging to other domain objects will still be persistent.

Turn off acl removal for specific entity

You can use the DomainObject annotation to opt-out of acl removal for a specific entity type.

<?php

namespace Acme\DemoBundle\Entity;

use Oneup\AclBundle\Annotation as Acl;

/**
 * @Acl\DomainObject(remove=false)
 */
class Product
{
}

In this case Acl entries for the domain object Product will remain persistent in your database, even if the entity gets deleted. Entries belonging to other domain objects will still be removed.