Weave Code
Notification Bundle Laravel Package
softspring/notification-bundle
Softspring Notification Bundle adds a flexible notification system to Symfony apps, with database storage, multiple delivery channels, templates, and user preferences for sending and managing notifications with minimal setup.
At a glance
Frequently asked questions about Notification Bundle
- Can I use softspring/notification-bundle in a Laravel application?
- No, not directly. This is a Symfony bundle built on DependencyInjection extension classes, compiler passes, tagged services and the Symfony event dispatcher, none of which Laravel's service container or package discovery mechanism loads. Using it in Laravel would require a bespoke adapter layer, which is usually more work than adopting a Laravel-native notification system. If your application is Laravel, treat this package as out of scope and re-source the requirement.
- How do I install softspring/notification-bundle?
- Install it with Composer using composer require softspring/notification-bundle inside a Symfony application. Register the bundle in config/bundles.php if your Flex recipe does not do it automatically, then create the bundle configuration file for your channels and storage options. The installation flow assumes Symfony's kernel and container, so there is no Laravel service provider or facade to publish.
- Is softspring/notification-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle. The Composer name, the Bundle suffix and the Softspring vendor namespace all point to Symfony, and the package relies on Symfony-specific integration points such as DI extensions and tagged services. That distinction should be confirmed before any integration work starts, because it determines whether the package is viable for your project at all.
- What features does Softspring Notification Bundle provide?
- It adds a flexible notification system with database storage for notification records, multiple delivery channels, templates for message content, and per-user preferences that control how notifications are sent and managed. The intent is to give you a working notification layer with minimal setup in a Symfony application. Channel behaviour and template rendering depend on how you configure the bundle and which transport services are available in your app.
- How do I configure channels, templates and user preferences in this bundle?
- Configuration is done through the bundle's Symfony config tree, where you define the available channels, template settings and preference handling. Because config schema changes are the most common silent breakage in bundle minor releases, dump the resolved configuration before and after any upgrade and compare the output. Wire channel services through Symfony's container and tag them as the bundle expects.
- Does softspring/notification-bundle require a database migration?
- Yes, the bundle stores notifications in the database, so the corresponding tables and Doctrine mappings must exist in your schema. Generate and review a Doctrine schema diff in a scratch database before deploying, especially after an upgrade that may have altered mappings. Treat any persistence change as migration-sensitive even if the release is labelled a minor version.
- What changed in softspring/notification-bundle 5.6.0?
- The 5.6.0 release notes contain only a compare link to the previous tag, with no summary, migration notes or deprecation list, so the change content is effectively unverified. A minor bump under semver suggests additive, backwards-compatible changes, but that is a weak prior rather than evidence. Pin to v5.5.10 in composer.json and the lockfile, then require a written diff review before scheduling the upgrade.
- Which PHP, Symfony and Doctrine versions does softspring/notification-bundle support?
- Read the composer.json inside the specific tag rather than trusting the release page, because a minor release can raise a transitive version floor without announcing it. Confirm the PHP constraint, the minimum Symfony version, and the Doctrine ORM and messenger ranges against your runtime. A mismatch here will surface as a Composer resolution failure or, worse, a runtime error in staging.
- How should I test a notification bundle upgrade before production?
- Upgrade in an isolated branch with composer update softspring/notification-bundle --with-dependencies and resolve lockfile conflicts deliberately. Then exercise every configured channel and dispatch a notification through whatever queue or transport you use in a staging environment. Combine that with a resolved-config diff and a Doctrine schema diff so configuration and persistence regressions are caught before release.
- What are the alternatives to softspring/notification-bundle for a Laravel app?
- For Laravel, use the framework's built-in notification system, which already covers mail, database, broadcast and chat or SMS channels with queued delivery and per-user preferences. Maintained community notification packages are also an option if you need extra channels. Bridging a Symfony bundle into Laravel is not a recommended path, so confirm your framework before evaluating this package further.
Weaver
How can I help you explore Laravel packages today?