Sulu Bulk Actions Bundle Laravel Package

Product Decisions This Supports

• Bulk content operations as a baseline CMS admin capability. v1.2.0 makes bulk delete available by default for articles, snippets, testimonials, and events, and adds copy_locale for testimonials and events. This supports roadmap decisions around editorial efficiency rather than one-off custom admin work.
• Localization and translation workflows. The new copy_locale bulk action copies the draft through the content manager, which supports product decisions around multi-market, multi-language content operations and reduces manual duplication.
• Safe destructive actions and permission governance. Delete is gated by the “Delete” permission in the “Bulk actions” context and by list context; sulu_bulk_actions.delete_enabled can disable it globally. This supports decisions about editor autonomy versus administrative control.
• Trash and recovery behavior. ContentEntityBulkActionHandler now mirrors bundle controller behavior: entities go to trash when available, are removed, and a “removed” domain event is collected. This supports product decisions around recoverability and compliance.
• Auditability and downstream integrations. Publish/unpublish for testimonials and events now collect “published” and “unpublished” domain events, fixing gaps where activity logs and search indexes were not updated. This supports decisions about audit trails, activity feeds, and search consistency.
• Build vs. buy / reuse. The package provides reusable bulk-action infrastructure across content types. Product should prefer extending this package over building bespoke bulk operations per entity, unless requirements are highly specialized.
• Incremental roadmap coverage. The release extends coverage to testimonials and events and standardizes delete behavior. This supports phased rollout decisions: enable delete first where permission models and trash behavior are well understood, then expand localization copy workflows.

When to Consider This Package

Consider adoption when:

• You run a Sulu CMS on Symfony/PHP and need editor-facing bulk actions for articles, snippets, testimonials, or events.
• Editors need permission-aware bulk delete with trash/recovery semantics rather than raw deletion.
• You need bulk locale copying for testimonials or events and want it to use the existing content manager and draft workflow.
• You need publish/unpublish transitions to emit domain events so activity logs and search indexes stay consistent.
• You are comfortable with Symfony service configuration and can absorb the migration from services.xml to Resources/config/services.yaml, including the new symfony/yaml requirement.
• You can review customizations around ContentEntityBulkActionHandler, because its constructor now takes the content manager, domain event collector, trash manager, and domain event classes, with the last three optional.
• You can accept that sulu_bulk_actions.delete_enabled now defaults to true, with safety provided by permission gating rather than a default-off flag.

Look elsewhere when:

• You are not using Sulu/Symfony, or you need a Laravel-native package rather than a Sulu bundle.
• You have a headless-only CMS setup with no admin bulk-action surface.
• You cannot tolerate the constructor signature change or the YAML service-definition migration in your integration.
• You require delete to be disabled by default for all roles and cannot manage that through configuration.
• Your content types or permission model are substantially different and would require more customization than reuse.

How to Pitch It (Stakeholders)

For executives: This release turns common editorial chores into safe, permission-controlled bulk operations. Editors can delete or locale-copy content in batches, reducing manual work and localization delay. Delete is recoverable through trash where available, gated by permissions, and can be disabled globally. Publish/unpublish now feeds activity logs and search indexes, improving auditability and content freshness. The main adoption cost is a small Symfony configuration migration and awareness that bulk delete is enabled by default but permission-gated.

For engineering: v1.2.0 adds bulk delete and copy_locale, standardizes delete through ContentEntityBulkActionHandler with trash and domain-event integration, and fixes missing publish/unpublish domain events. It moves services to YAML, adds a symfony/yaml requirement, and changes the handler constructor to accept content manager, domain event collector, trash manager, and domain event classes, with the latter three optional. Review custom service definitions and handler wiring before upgrading; validate permission contexts, trash availability, and search-index/activity-log behavior in staging.