- Is manuxi/sulu-event-bundle a Laravel package, or can I use it inside a Laravel application?
- It is not a Laravel package. It is a Sulu CMS bundle built on Symfony, shipping a Symfony DI extension, Doctrine entities, and Sulu admin XML/JS, so it cannot be consumed directly in a Laravel codebase. You need a working Sulu 2.x instance alongside, or the design would have to be ported.
- How do I install manuxi/sulu-event-bundle in a Sulu 2.x project?
- Install it with Composer, register the bundle in config/bundles.php, import its routing and Sulu admin configuration, and update the Doctrine schema. You still need a working Sulu 2.x skeleton first. Check composer.json for the supported Sulu and PHP constraints before committing.
- Which Sulu and PHP versions does manuxi/sulu-event-bundle v3.5.0 support?
- The release notes do not publish a compatibility matrix, so this question remains open. Read composer.json for the actual Sulu and PHP constraints and confirm them against your skeleton. The bundle is documented as requiring Sulu 2.x, and v3.5.0 adds an optional dependency on sulu/automation-bundle.
- Do I need sulu/automation-bundle to schedule event publishing and unpublishing?
- No, it is optional. The integration is guarded with interface_exists(), so the bundle degrades gracefully when the automation bundle is not installed. Install it only if you want scheduled publish and unpublish behavior for events.
- How do I render events on the frontend with Sulu Event Bundle?
- The bundle exposes template-friendly event data for custom frontend rendering, including dates, locations, descriptions, media, speaker, author, and PDF fields. You build your own templates and can use smart content that evaluates website categories and tags. Direct routes for event templates are also provided.
- What does sulu:events:clean-image-data do and should I run it when upgrading?
- Upgrade notes require running sulu:events:clean-image-data to reduce stored event image data to its id. Earlier versions appear to have written bloated or destructive data into template data, based on fixes such as event images no longer being written into templateData and template data no longer clearing image, pdf, speaker, or author. Audit existing records rather than only cleaning them, since existing installations may carry corrupt or oversized data.
- Does manuxi/sulu-event-bundle support multilingual event content?
- Yes. It uses Sulu's localization support, so editors can maintain event content per locale in the Sulu admin. Frontend rendering then follows Sulu's normal localization behavior.
- What are the MCP tools in this bundle, and are they safe to expose in production?
- The bundle adds MCP tools that provide a programmatic read/write surface over events and locations, aimed at content operations and AI-assisted editorial workflows. The event update tool intentionally mutates only the fields supplied, which is narrow semantics. However, its authentication, authorization, and audit characteristics are unevaluated, so treat it as a new attack surface and a new permission model to review before production use.
- Is manuxi/sulu-event-bundle actively maintained, and what is the bus factor risk?
- The release history from 3.1.7 to 3.5.0 shows six consecutive releases of fixes and features, which is meaningful evidence that the maintainer is shipping. The bus factor is still the dominant risk: a small maintainer base, no indicated commercial backing, zero dependents, and low stars mean you remain an early adopter. The MIT license is clean for commercial use and forking.
- What data-shape changes should I test for when upgrading to 3.5.0?
- Re-verify anything downstream that reads event payloads, such as templates, exports, and custom controllers. Referenced locations are now serialized as plain arrays, single event selection ids are treated as UUID strings, and start and end dates are normalized before persisting. The global admin override sulu_admin.smart_content_label was also removed, so check for admin UI label regressions.