Other Bundle Events
Individual Pimcore bundles dispatch their own events beyond those in the core framework and Studio Backend. Each bundle defines event constants in dedicated event classes.
Bundles Within pimcore/pimcore
These bundles ship with the pimcore/pimcore package but define separate event classes:
- RedirectEvents (SeoBundle) - redirect create, update, delete
- JobRunStateChangedEvent (GenericExecutionEngineBundle) - job execution state changes
Data Hub
The Data Hub bundle defines events for configuration management and GraphQL operations:
- ConfigEvents - Data Hub configuration changes
- AdminEvents - Data Hub admin operations
- GraphQL events for queries, mutations, and listings
(see
Pimcore\Bundle\DataHubBundle\Event\GraphQLnamespace)
Ecommerce Framework
The Ecommerce Framework provides events for checkout, order processing, and indexing:
- CheckoutManagerEvents - checkout process lifecycle
- CommitOrderProcessorEvents - order commit processing
- IndexServiceEvents - product index operations
- OrderAgentEvents - order agent actions
- OrderManagerEvents - order management operations
Personalization
The Personalization bundle provides targeting and visitor profiling events:
- TargetGroupEvents - target group assignment changes
- TargetingEvents - targeting rule evaluation and visitor profiling
Other Bundles
Additional bundles with their own events include:
- Web-to-Print - document rendering events
(see
Pimcore\Bundle\WebToPrintBundle\Event\DocumentEvents) - Generic Data Index - asset, document, and data object indexing events
(see
Pimcore\Bundle\GenericDataIndexBundle\Eventnamespace)
Refer to each bundle's documentation and source code for the full list of available events, event objects, and usage examples.