- Can I use Callisto Mailer in Laravel without Symfony components like Symfony Mailer or Twig?
- No, Callisto Mailer is a Symfony bundle and requires Symfony Mailer and Twig to function. You’ll need to integrate these via Laravel’s Symfony bridge (e.g., `symfony/mailer`, `twig/extra-bundle`) or a custom facade to abstract dependencies. If you’re not using Symfony, this adds overhead but isn’t impossible.
- How do I migrate existing Laravel Mailables or Notifications to Callisto Mailer?
- Callisto Mailer replaces static Mailables with database-driven Twig templates. Start by exporting your existing email templates to the package’s schema (via migrations or seeders), then update your code to use Callisto’s API for sending. For notifications, you’ll need to refactor logic to fetch templates dynamically from the database.
- Does Callisto Mailer support Laravel’s queue system for delayed email sending?
- Yes, Callisto Mailer integrates with Laravel’s queue system natively. You can dispatch emails as jobs, defer them, and process them asynchronously just like standard Laravel Mailables. The package leverages Symfony Mailer under the hood, which supports queues seamlessly.
- What Laravel versions are compatible with Callisto Mailer 1.0.0?
- Callisto Mailer 1.0.0 is designed for Laravel 10+ and requires PHP 8.3+. While it’s Symfony-based, Laravel’s Symfony bridge (e.g., `spatie/laravel-symfony-mailer`) can help abstract compatibility. Test thoroughly, as some Symfony 7/8 features may not align perfectly with older Laravel versions.
- How do I handle Twig errors or debugging in a Laravel application?
- Twig errors may not surface cleanly in Laravel’s exception handler by default. Configure Twig’s error handling in your Symfony bridge setup to log errors or display them in Laravel’s debug bar. Alternatively, wrap Twig template rendering in try-catch blocks to log errors to Laravel’s log channel for consistency.
- Is there a performance impact from storing email templates in the database?
- Yes, database-stored templates introduce query overhead compared to static Blade files. However, the package caches compiled Twig templates to mitigate this. For high-volume email systems, consider pre-compiling templates or using a hybrid approach (e.g., static Blade for templates, database for dynamic content).
- Can I use Blade templates instead of Twig with Callisto Mailer?
- No, Callisto Mailer is Twig-centric and doesn’t natively support Blade. However, you could create a custom wrapper to convert Blade templates to Twig or use a package like `spatie/laravel-twig-view` to render Blade in Twig contexts. This adds complexity and isn’t officially supported.
- What happens if Callisto Mailer is abandoned or no longer maintained?
- Since the package is new (0 dependents), assess the risk by reviewing its codebase and documentation. If abandoned, you could fork it or migrate to alternatives like `spatie/laravel-newsletter` (for newsletters) or Laravel’s native `Notifications` system. Export your templates to static files as a fallback.
- How do I configure multi-language email support in Callisto Mailer?
- Callisto Mailer supports multi-language emails via Twig’s translation extensions. Configure your Symfony bridge to load translation files (e.g., from `resources/lang`) and pass the locale to templates. The package’s documentation covers dynamic language switching and fallback mechanisms for missing translations.
- Are there alternatives to Callisto Mailer for Laravel that don’t require Symfony?
- Yes, consider `spatie/laravel-newsletter` for newsletters, Laravel’s built-in `Notifications` system for simple emails, or `beberlei/mailable` for advanced templating without Symfony. For database-driven templates, you could also build a custom solution using Eloquent and Blade, though it lacks Callisto’s premium layouts and validation features.