- How do I install Firefly Filament Blog in an existing Laravel project with Filament?
- First, ensure Filament is installed. Run `composer require firefly/filament-blog` and publish assets with `php artisan vendor:publish --tag=filament-blog-assets`. Then, register the plugin in your Filament panel configuration. Follow the README’s installation steps for exact commands and dependencies.
- Does this package work with Filament 3.x and 5.x? Are there breaking changes between versions?
- Yes, the package supports both Filament 3.x and 5.x. However, Filament 5.x was added in v4.0.0, so ensure you’re using a compatible version. Check the changelog for breaking changes if upgrading between major Filament releases. Always test in a staging environment first.
- Can I customize the frontend templates (e.g., post layouts, comment forms) without overriding core files?
- Templates are published via `php artisan vendor:publish --tag=filament-blog-views`, allowing you to extend or override them without modifying the package directly. For complex UIs, integrate Livewire or Inertia for dynamic features like real-time comments or interactive elements.
- How do I handle database conflicts if my Laravel app already has blog-related tables (e.g., posts, comments)?
- Use the `tables.prefix` config option (e.g., `fblog_`) to avoid naming collisions. Run `php artisan vendor:publish --tag=filament-blog-migrations` to inspect migrations before applying them. For shared databases, test migrations in a staging environment to ensure no conflicts.
- Is the package compatible with Laravel 10 or older versions? What about Filament 4.x?
- The package is officially supported for **Laravel 11** and Filament 3.x/5.x only. Laravel 10 may work with minor adjustments, but Filament 4.x is unsupported. Check the [GitHub issues](https://github.com/thefireflytech/filament-blog/issues) for community patches or compatibility reports.
- How do I enable comments on blog posts and prevent spam? Does it support reCAPTCHA?
- Comments are enabled by default in the Filament admin panel. To prevent spam, integrate reCAPTCHA via the package’s extensibility hooks or third-party packages like `spatie/laravel-honeypot`. Configure spam protection in the `filamentblog.php` config file or extend the `CanComment` trait.
- Can I use a custom User model instead of Laravel’s default User model for author profiles?
- Yes, update the `auth.model` in the `filamentblog.php` config to point to your custom User model. Ensure the model includes the required fields (e.g., `name`, `avatar`) and add the `HasBlog` trait if needed. Test author blocks in the frontend to confirm compatibility.
- What’s the best way to schedule blog posts for future publishing?
- Use Filament’s built-in scheduling feature in the blog post editor. When creating or editing a post, set the `published_at` field to a future date/time. The package handles the rest, publishing the post automatically when the scheduled time arrives.
- Does this package support newsletter subscriptions and email notifications for new posts?
- Yes, the package includes newsletter subscription forms and email notifications for new posts. Configure the `mail` settings in `filamentblog.php` to specify the sender address and template. Use Laravel’s `Mail` facade or third-party services like Mailgun for delivery.
- Are there alternatives to Firefly Filament Blog for Laravel + Filament projects?
- Alternatives include **Filament Nova Blog** (for Laravel Nova), **Orchid Blog** (for Orchid platforms), or standalone packages like **Spatie Blog** (for non-Filament projects). However, Firefly Filament Blog is uniquely optimized for Filament’s UI/UX and leverages its resource system for seamless integration.