Weave Code
Faq Admin Bundle Laravel Package
genj/faq-admin-bundle
Symfony bundle that adds a ready-made admin interface for managing FAQ entries, with CRUD, category organization, ordering, and publish controls so you can maintain help content without building custom backend screens.
At a glance
Frequently asked questions about Faq Admin Bundle
- Is genj/faq-admin-bundle a Laravel package?
- No. Despite being framed as a PHP package, it is a Symfony bundle named GenjFaqAdminBundle, registered through Symfony's bundle system and built on Doctrine ORM entities rather than Eloquent. It contains no Illuminate service provider, no Laravel auto-discovery entry, and none of the config or routes conventions Laravel expects. The only thing portable to Laravel is the domain concept, not the code.
- Can I install genj/faq-admin-bundle with Composer in a Laravel app?
- Composer resolution will most likely fail against modern symfony and doctrine constraints, or force-pin ancient transitive versions that conflict with illuminate packages. Even if it installs, there is no service provider or route registration path, so nothing will wire up. Treat any successful install as a red flag rather than a win.
- What Laravel version does genj/faq-admin-bundle support?
- None. The bundle predates the Laravel package ecosystem conventions entirely and its last release was in June 2017, targeting Symfony 2.8/3.x with Doctrine 2.4-era constraints. It has no declared support for Laravel 10, 11, or 12, and no compatibility shims exist. Running it under PHP 8.1+ would surface removed functions, signature changes, and dynamic property deprecations.
- How do I build a FAQ admin panel in Laravel instead?
- Create a faqs table with id, question, answer, nullable category_id, position for manual ordering, is_published, published_at, and timestamps, plus an optional faq_categories table. Add an Eloquent model with published() and ordered() scopes and a category relation. For the admin surface, use a Filament or Nova resource with reorderable rows, which replaces the bundle's entire reason for existing in less code than porting would take. Expose a public route and Blade view, and cache the rendered list.
- Is genj/faq-admin-bundle maintained or safe to use in production?
- No. The repository is archived, there is no maintainer, it has zero stars and zero dependents, and the last release was 2017-06-10. An abandoned admin bundle is a standing attack surface, since unpatched form handling and rich-text paths are common sources of CVEs and there will be no advisory or patch. It should not be a runtime dependency in any project.
- Does genj/faq-admin-bundle still work on modern Symfony?
- Unlikely. Its Symfony and Doctrine version pins would also fail on Symfony 5, 6, or 7, so the stack fit is marginal even outside Laravel. There is no version of this bundle that runs cleanly on a current framework without a full port. That makes it a design reference at best.
- What features does genj/faq-admin-bundle actually provide?
- It ships CRUD for questions, answers, and categories, sortable listings for controlling display order, a draft and publish state for staged content, Twig templates meant to fit existing admin themes, and configurable routing and entity mapping. Conceptually that maps to a question/answer entity with ordering and publication state. All of it would need to be reimplemented as Laravel controllers, requests, Blade or Filament resources, and Eloquent models.
- What are the alternatives to genj/faq-admin-bundle for FAQ management?
- For the admin side, Filament or Laravel Nova give you reorderable resources with maintained security coverage. For richer content needs, spatie/laravel-translatable handles i18n and Laravel Scout adds full-text search if the corpus grows. If you need public rendering, plain Laravel routes plus Blade with caching is sufficient. All of these are actively maintained and supported on current Laravel releases.
- How much effort is porting genj/faq-admin-bundle to Laravel?
- It is a rewrite, not an integration. You would port Doctrine entities to Eloquent models and migrations, rewrite Symfony controllers and forms into Laravel controllers and FormRequests, replace Twig with Blade or a Filament resource, and drop the Symfony admin layer entirely. Building the FAQ admin natively is roughly one to three developer-days, versus an unbounded porting effort with no upstream to lean on.
- Is genj/faq-admin-bundle's MIT license a reason to fork it?
- The MIT license is the one unambiguous positive, so legally you can fork it. Technically you should not, because you would inherit PHP 5.6/7.0-era code with no maintainer and no security coverage. If the domain model is useful, extract the schema intent and rebuild it natively in Laravel rather than vendoring the original.
Weaver
How can I help you explore Laravel packages today?