Weave Code
Front Desk Bundle Laravel Package
openclassrooms/front-desk-bundle
A Symfony bundle that adds a lightweight front desk to your app, letting users submit support requests while staff review and respond from a dedicated interface. It wires up routes, controllers, and templates so you can integrate a simple ticketing workflow quickly.
Front Desk Symfony2 Bundle
Frequently asked questions about Front Desk Bundle
- Can I install openclassrooms/front-desk-bundle in a Laravel application?
- No. This is a Symfony 2 bundle that ships a Bundle class, a DependencyInjection extension, and YAML/XML service definitions, none of which Laravel's service container or package discovery can consume. There is no bridge, adapter, or shim available, and building one would effectively mean a full rewrite. The practical effort to port it exceeds the effort to implement an equivalent ticketing workflow natively in Laravel.
- What does the Front Desk bundle actually do?
- It adds a lightweight front desk to a Symfony application, letting end users submit support requests while staff review and respond from a dedicated interface. It wires up routes, controllers, and Twig templates so a simple ticketing workflow can be integrated quickly. The value is in the pre-built request-and-reply flow rather than in any reusable domain library.
- Which Symfony and PHP versions does this bundle support?
- It targets Symfony 2.x and the PHP 5.3 to 5.6 era. Symfony 2 reached end of life in November 2018, and those PHP versions are long unsupported. It cannot be installed on Symfony 5, 6, or 7, nor on any currently supported PHP runtime.
- Is openclassrooms/front-desk-bundle still maintained?
- There is no evidence of maintainer activity, and the package shows no adoption signal such as dependents or community validation. It is effectively an abandoned artifact from the Symfony 2 era. Treat it as unmaintained and assume no security patches will arrive.
- What dependencies does the bundle pull in?
- Its dependency chain is tied to the Symfony 2 security layer and, per the evaluation, an old FOSUserBundle version, all of which are deprecated or abandoned. FOSUserBundle has itself been superseded by native Symfony security components. This dependency chain is one of several disqualifying factors even before considering the framework mismatch.
- What should I use to build a support ticketing system in Laravel instead?
- Implement the workflow natively with Laravel's first-party tools: models and migrations for tickets and replies, policies for staff authorization, notifications for updates, and Blade or Inertia views for the two interfaces. For the user and identity side, Laravel Breeze or Fortify covers registration and authentication out of the box. This gives you a maintained, tested, and secure implementation rather than a port of abandoned code.
- Is there any reason to read the source of this bundle if I never install it?
- The only plausible value is design reference, for example how it models ticket state, staff replies, and routing between the user and staff interfaces. That inspiration is limited, since the code is tightly coupled to Symfony 2 conventions, Twig, sessions, and the framework firewall. Read it as a sketch, not as a foundation.
- I inherited a legacy app that uses this bundle. How do I migrate off it?
- The migration direction is off the bundle, not onto it. Replace the Front Desk registration, authentication, and request flows with your framework's current first-party security components, then delete the bundle and its deprecated dependencies. Do this on the legacy Symfony app while planning a broader move to a supported stack.
- Does the bundle work with Laravel's service container or auto-discovery?
- No. Laravel auto-discovery looks for a service provider class with register and boot methods, while this package exposes a Symfony Bundle class and a DependencyInjection extension. Laravel has no mechanism to register Symfony kernel extensions or load the bundle's YAML/XML service definitions. Composer may resolve the name, but nothing in the package will be wired into the application.
- What is the risk of spending time trying to make this bundle work?
- The risk is high and one-directional: the likely outcome is engineering time spent discovering that it cannot work. Incompatibility exists simultaneously at the framework level, the PHP runtime level, and the dependency chain, and any one of those alone would be disqualifying. Time-box any proof of concept to a single day and expect dependency resolution to fail immediately.
Weaver
How can I help you explore Laravel packages today?