Weave Code
Doctrine Extensions Bundle Laravel Package
polishsymfonycommunity/doctrine-extensions-bundle
Symfony bundle that integrates Doctrine extensions such as Gedmo Sluggable, Timestampable, Tree, Translatable, and Loggable, with simple configuration and service registration for adding common behavioral features to Doctrine entities.
PSS extensions for Doctrine 2
Frequently asked questions about Doctrine Extensions Bundle
- Can I use polishsymfonycommunity/doctrine-extensions-bundle in a Laravel application?
- Practically, no. It is a Symfony bundle that depends on Symfony bundle registration and its Configuration/Extension classes, none of which execute under Laravel's service container. You could only use it by adding laravel-doctrine/orm and manually rebuilding the bundle's container configuration, which means you are using Gedmo directly rather than leveraging this package. For Laravel, implement audit stamping natively or use a Laravel-specific Doctrine extensions package.
- What does polishsymfonycommunity/doctrine-extensions-bundle do?
- It is a Symfony bundle that integrates Gedmo Doctrine extensions such as Sluggable, Timestampable, Tree, Translatable, Loggable, and Blameable into a Symfony application. Its real value is Symfony DI wiring and configuration around code that lives in gedmo/doctrine-extensions. It is not an Eloquent package and does not provide Laravel model behaviors.
- Is polishsymfonycommunity/doctrine-extensions-bundle still maintained?
- No. The package is archived, has around 11 stars and zero dependents, and has no active maintainer or security response path. That means no downstream validation and no reliable upgrade path. Treat it as abandoned and avoid making it a production dependency.
- Which Laravel versions support polishsymfonycommunity/doctrine-extensions-bundle?
- None officially. This is a Symfony bundle, not a Laravel package, so it has no Laravel version support matrix. Its Composer constraints are from the Doctrine2/Symfony 2 era and are likely to conflict with modern illuminate/* components and current PHP runtimes. Do not expect it to install or run cleanly in a current Laravel application.
- How do I install polishsymfonycommunity/doctrine-extensions-bundle with Composer?
- In a Symfony application it would be installed with composer require polishsymfonycommunity/doctrine-extensions-bundle and registered as a bundle. In Laravel that installation path does not apply, and using --ignore-platform-reqs is dangerous because removed Doctrine\Common\Persistence namespaces can fail at runtime rather than install time. For a Laravel project, do not install it.
- What is a Laravel alternative for created_by and updated_by audit columns?
- Use a native Auditable trait with Model::creating and Model::updating hooks or a single model observer, plus nullable foreign key columns for created_by and updated_by. Resolve the actor with Auth::id() and provide an explicit fallback for console and queue contexts. Test it with actingAs and assertDatabaseHas against the audit columns. If you need full audit history with before/after values, evaluate owen-it/laravel-auditing instead.
- Does polishsymfonycommunity/doctrine-extensions-bundle work with Laravel Doctrine ORM?
- Not as a bundle. Even with laravel-doctrine/orm in the stack, Symfony bundle discovery and Configuration/Extension classes do not execute under Laravel's container, so the bundle's wiring is dead code. The supported route is laravel-doctrine/extensions, which already wraps Gedmo listeners, or registering the Gedmo BlameableListener directly as a Doctrine event subscriber in a service provider.
- What are the production risks of using this archived package?
- The risk is high and effectively unquantifiable: the package is archived, has no maintainer, no security response path, and no downstream dependents providing validation. It targets Doctrine2-era APIs, including Doctrine\Common\Persistence namespaces that were removed, so failures may appear at runtime after an apparently successful install. Composer conflicts with modern Laravel and PHP versions are also likely.
- How do I resolve the current user for blameable columns in queue workers and scheduled commands?
- You need an explicit actor resolver because Auth::id() is usually null outside HTTP requests. The Symfony bundle's token-storage-based resolver has no Laravel equivalent, so that integration must be written anyway. Implement an AuditableResolver interface, set the actor from Auth in HTTP contexts, and pass or set the actor ID explicitly in jobs and commands.
- What should I use instead of polishsymfonycommunity/doctrine-extensions-bundle?
- For Symfony with Doctrine, use stof/doctrine-extensions-bundle with gedmo/doctrine-extensions rather than this archived fork. For Laravel with Doctrine, use laravel-doctrine/extensions and register Gedmo listeners directly. For standard Laravel with Eloquent, implement audit stamping natively or use owen-it/laravel-auditing when you need full audit history.
Weaver
How can I help you explore Laravel packages today?