- Can I use Croct’s Symfony bundle (plug-symfony) directly in a Laravel project?
- No, the Symfony bundle is designed for Symfony’s architecture (DependencyInjection, EventDispatcher, Twig) and won’t work natively in Laravel. Laravel’s ServiceProvider, Facade, and Blade systems are incompatible without significant custom adaptation.
- What’s the easiest way to integrate Croct with Laravel?
- Use the underlying **plug-php** package directly via Composer (`composer require croct/plug-php`). It’s Laravel-compatible and handles core features like content fetching, A/B testing, and personalization without Symfony’s abstractions.
- Will Croct’s Symfony bundle work with Laravel’s Blade templating?
- No, the bundle relies on Symfony’s Twig integration. For Blade, you’d need to manually adapt Croct’s content injection logic or build a custom wrapper to bridge Symfony’s templating system with Laravel’s Blade.
- How do I handle Croct’s event system in Laravel?
- Laravel’s event system is incompatible with Symfony’s `EventDispatcherInterface`. You’d need to create custom event listeners in Laravel’s `EventServiceProvider` or use a middleware-based approach to trigger Croct logic at specific request stages.
- Does Croct provide official Laravel support or documentation?
- No, Croct’s official documentation and SDKs are Symfony-focused. For Laravel, you’ll rely on the **plug-php** package’s docs or community-built wrappers, which may lack Symfony-specific features like Bundle integration.
- What Laravel versions does the Symfony bundle support?
- The Symfony bundle is irrelevant for Laravel—it targets Symfony 5.4+. For Laravel, **plug-php** (v2026+) is the relevant package, which supports modern Laravel (8.x+) but requires manual setup for Laravel’s ecosystem.
- Are there performance concerns using Croct in Laravel?
- Performance depends on your integration approach. Direct **plug-php** usage avoids Symfony overhead, but custom middleware or event listeners could introduce latency if not optimized. Test API call timing in Laravel’s request lifecycle.
- Can I use Croct’s queue system in Laravel?
- Yes, but you’ll need to manually configure **plug-php** to work with Laravel’s queue system (e.g., `Queue::dispatch()`). The Symfony bundle’s queue integration won’t apply, so use Croct’s PHP SDK’s queue clients directly.
- What alternatives exist for Laravel if Croct’s Symfony bundle isn’t viable?
- Consider Laravel-native packages like **spatie/laravel-activitylog** for personalization, or build a lightweight wrapper around **plug-php** to adapt Symfony features (e.g., caching, HTTP clients) to Laravel’s ecosystem.
- How do I handle caching with Croct in Laravel?
- Use Laravel’s `Cache` facade with **plug-php**’s caching layer. The Symfony bundle’s cache integration (e.g., Symfony’s `CacheInterface`) won’t work—configure Croct’s client to use Laravel’s cache store (e.g., Redis, file) via its PHP SDK options.