Weave Code
At a glance
Frequently asked questions about Notifications
- Can I use ibexa/notifications in a standalone Laravel app without Ibexa DXP?
- No, this package is tightly coupled with Ibexa DXP and assumes a Symfony-based stack. You’d need a Symfony Bridge (e.g., symfony/console, symfony/notifier) and custom Laravel service bindings to abstract dependencies like Doctrine ORM and event dispatchers. Consider Laravel-native alternatives like spatie/laravel-notification-channels for simpler integration.
- What Laravel versions support ibexa/notifications?
- Laravel 10+ (PHP 8.3+) is required due to Symfony 7.4 LTS dependencies. Older Laravel versions will fail due to incompatible Symfony components. Test thoroughly with Laravel 10.x and 11.x, as Ibexa’s v5.x may introduce breaking changes.
- How do I handle Doctrine ORM in Laravel if ibexa/notifications uses it?
- Ibexa relies on Doctrine, but Laravel uses Eloquent. You have three options: 1) Use fruitcake/laravel-doctrine to integrate Doctrine alongside Eloquent, 2) map Ibexa’s entities to Eloquent models manually, or 3) store notifications in a hybrid approach (e.g., Laravel DB for metadata, Ibexa DB for content). Option 2 is simplest for most use cases.
- Does ibexa/notifications support Laravel’s Notification facade or Mail services?
- No, it uses Symfony’s Notifier/Mailer. You’ll need to create custom adapters to bridge Ibexa’s notification system with Laravel’s Mail or Notification facade. For example, wrap Symfony’s Mailer in a Laravel Mail transport or use event listeners to trigger Laravel’s notification channels.
- How do I trigger notifications in Laravel if Ibexa uses its own event system?
- Create Laravel event listeners that dispatch Ibexa’s notification services. For example, listen to Laravel’s `sent` event and trigger Ibexa’s `NotificationService` via a custom handler. Alternatively, use Laravel’s queue system (e.g., `ShouldQueue`) to defer notification processing to Ibexa’s services.
- What notification channels (email, SMS, push) does ibexa/notifications support?
- Ibexa supports typed notifications (emails, push, SMS) via Symfony’s Notifier, but Laravel’s native channels (e.g., Mail, Twilio, Echo) won’t work out-of-the-box. You’ll need to implement custom channel adapters or use Laravel’s Notification facade to route messages through Ibexa’s system.
- Is real-time notification delivery possible in Laravel with this package?
- Ibexa may use WebSockets for real-time delivery, but Laravel would require additional setup like Pusher, Ably, or Laravel Echo. You’d need to bridge Ibexa’s WebSocket events to Laravel’s broadcast drivers or use Laravel’s Echo server as a proxy.
- What’s the licensing cost for using ibexa/notifications in production?
- This package requires an **Ibexa Business Use License (BUL)**, which is tied to a commercial Ibexa DXP subscription. Non-commercial or trial use requires the Ibexa Trial and Test License (TTL). Check Ibexa’s licensing page for pricing and terms, as community support is limited without a paid subscription.
- Are there Laravel-native alternatives to ibexa/notifications?
- Yes. For email/SMS/push notifications, consider spatie/laravel-notification-channels (supports 100+ channels), laravel-notification-channels/mailgun, or laravel-notification-channels/twilio. For event-driven workflows, Laravel’s built-in events and queues may suffice without Ibexa’s overhead.
- How do I configure ibexa/notifications in Laravel’s .env or config files?
- Ibexa uses YAML/XML config, but you’ll need to convert it to Laravel’s `.env` or `config/notifications.php`. Key settings include Symfony Notifier transports (e.g., `DSN=mailer://default`), Ibexa’s API keys, and Doctrine connection strings. Document these mappings, as Ibexa’s config structure differs from Laravel’s conventions.
Weaver
How can I help you explore Laravel packages today?