Weave Code
Contao Theme Manager Bridge Laravel Package
oveleon/contao-theme-manager-bridge
Bridge package for integrating the Contao Theme Manager with other systems. Adds compatibility glue so themes and Theme Manager features can work smoothly in a bridged setup, simplifying installation, updates, and runtime interactions.
Contao Extension to install products from contao-thememanager.com.
Frequently asked questions about Contao Theme Manager Bridge
- Can I use oveleon/contao-theme-manager-bridge in a pure Laravel project without Contao?
- No, this package is specifically designed for Contao CMS and its Theme Manager. While it bridges Contao’s theme workflows into Composer-based setups, it lacks Laravel-specific integrations (e.g., Blade templates, Laravel Mix). For Laravel-only theme management, consider alternatives like spatie/laravel-theme or Laravel Mix/Vite.
- How do I install this package in a Laravel + Contao hybrid app?
- First, install via Composer: `composer require oveleon/contao-theme-manager-bridge`. Then configure Contao’s Theme Manager hooks in `config/services.yaml` (Symfony) or Contao’s `config/autoload.php`. For Laravel, you’ll need to manually bridge Contao services into Laravel’s container, as this package doesn’t provide Laravel-specific bindings.
- Does this package support Laravel’s service container or Facades?
- No, this package is built for Contao/Symfony and doesn’t include Laravel service provider bindings or Facade support. To integrate Contao services into Laravel, you’d need to create a custom Laravel service provider that proxies Contao’s Theme Manager functionality, which adds complexity.
- What Laravel versions does this package officially support?
- This package doesn’t officially support Laravel—it’s for Contao (which may or may not integrate with Laravel). However, if you’re using it in a hybrid Laravel + Contao app, ensure your Laravel version (8.x–10.x) aligns with the Symfony components Contao 5+ relies on (Symfony 5.x–6.x). Test thoroughly for compatibility.
- Will this package help with theme asset pipelines (e.g., Laravel Mix/Vite)?
- No, this package focuses on theme *management* (installation, updates, and runtime interactions) rather than asset compilation. For Laravel Mix/Vite integration, you’d need to manually configure Contao themes to output assets to Laravel’s `public/` directory or use a custom build script to bridge the two workflows.
- Is there a risk of license conflicts if I use this in a proprietary Laravel app?
- Yes, this package is licensed under AGPL-3.0, which requires open-sourcing your entire project if you distribute modifications. If your Laravel app is proprietary, this package may not be suitable unless you comply with AGPL terms or find a MIT/LGPL alternative.
- How do I migrate existing Laravel theme workflows to use this package?
- This package isn’t designed for Laravel themes, so migration isn’t straightforward. If you’re using Laravel’s theme packages (e.g., spatie/laravel-theme), you’d need to rebuild your themes to work with Contao’s Theme Manager, which involves rearchitecting your asset and template structure. Consider alternatives like Laravel Forge or custom solutions for smoother transitions.
- Are there alternatives for Laravel that avoid Contao dependencies?
- Yes, for Laravel-specific theme management, use packages like `spatie/laravel-theme` for dynamic themes or `laravel-mix`/`vite` for asset pipelines. If you need theme inheritance or multi-tenancy, explore `orchid/platform` or build a custom solution. These avoid Contao’s ecosystem entirely.
- Does this package work with Contao 4 or older versions?
- No, this package is designed for modern Contao installations (Contao 5+) that leverage Symfony components. Contao 4 uses a different architecture and won’t be compatible without significant modifications or a custom bridge.
- How do I test this package in a Laravel environment?
- Since this package isn’t Laravel-native, testing requires a hybrid setup: install Contao alongside Laravel (e.g., using `symfony/http-kernel` to bootstrap Contao’s kernel). Mock Contao’s Theme Manager in PHPUnit and verify theme installation/update workflows. Document edge cases like service container conflicts or AGPL compliance in your tests.
Weaver
How can I help you explore Laravel packages today?