Weave Code
Cms Extbase Laravel Package
typo3/cms-extbase
TYPO3 Extbase framework extension: provides the MVC foundation for TYPO3 CMS extensions, including controllers, domain models, persistence, validation, and property mapping. Used to build structured, maintainable TYPO3 applications and plugins.
[READ-ONLY] Subtree split of the TYPO3 Core Extension "extbase"
Frequently asked questions about Cms Extbase
- Can I use TYPO3 Extbase directly in a Laravel project without major refactoring?
- No, direct integration is not feasible due to architectural conflicts. Extbase’s Domain Model, Repository, and Fluid templating stack are incompatible with Laravel’s Eloquent ORM, Blade, and Service Container. You’d need to rewrite core components or isolate extbase in a microservice.
- What’s the best way to migrate a TYPO3 + Extbase backend to Laravel?
- Extract business logic (Domain Models, Services) into Laravel-compatible classes first. Replace Extbase Controllers/Repositories with Laravel equivalents, then gradually deprecate the legacy layer. Use Eloquent for database interactions instead of Extbase’s persistence layer.
- Does Extbase support Laravel’s dependency injection (DI) container?
- Extbase uses its own ObjectManager, which can be bridged to Laravel’s container via `bind()`, but this adds complexity and reduces performance. For new projects, avoid Extbase’s DI system entirely and rewrite dependencies as Laravel services.
- How do I handle TYPO3’s database schema (tt_content, sys_*) in Laravel?
- You’ll need custom Eloquent models or database views to reconcile TYPO3’s schema with Laravel’s conventions. Avoid direct queries to TYPO3 tables in Laravel; instead, abstract them into service layers or use a separate database schema for legacy data.
- Is Extbase’s validation system compatible with Laravel’s Validator?
- Extbase’s validators can be extended into Laravel’s Validator, but you’ll need custom rules or facade wrappers. For simplicity, rewrite validation logic using Laravel’s built-in rules or third-party packages like `laravel-validator`.
- Can I use Extbase for backend modules while building a Laravel frontend?
- This is possible but introduces dual-stack complexity. Extbase backend modules would need to communicate with Laravel via APIs or shared services, adding latency and coupling. Consider a full rewrite if long-term maintainability is a priority.
- What Laravel versions does Extbase support, and are there PHP version conflicts?
- Extbase is designed for PHP 7.4–8.1 (TYPO3 CMS 10/11) but relies on legacy patterns like magic methods and global state. Laravel 9+ (PHP 8.1+) will conflict with Extbase’s core classes, requiring polyfills or isolation layers.
- How do I test Extbase components in a Laravel project?
- Test Extbase logic in isolation using PHPUnit, but avoid testing its TYPO3-specific integrations (e.g., Fluid views, BE_USER). Mock Extbase dependencies like the ObjectManager and DatabaseConnection, then rewrite tests for Laravel-compatible code.
- Are there alternatives to Extbase for TYPO3 extensions that work better with Laravel?
- For new projects, avoid Extbase entirely. Use Laravel’s Eloquent, Livewire, or API-first approaches instead. If tied to TYPO3, consider extracting only business logic and replacing Extbase’s MVC layer with Laravel components.
- What are the license implications of using Extbase (GPL-2.0) in a Laravel (MIT) project?
- Extbase’s GPL-2.0 license may force your entire project under GPL if you distribute it. For Laravel (MIT), isolate Extbase in a private module or use it only for internal tools. Consult a lawyer if unsure—GPL compliance risks increase with distribution.
Weaver
How can I help you explore Laravel packages today?