Weave Code
Faq Bundle Laravel Package
genj/faq-bundle
A Symfony bundle for adding a managed FAQ section to your application. Includes categorized questions, admin controls, and ready-to-use entities, controllers, and templates for quick integration.
A FAQ bundle for Symfony3 (not 4)
Frequently asked questions about Faq Bundle
- Can I use genj/faq-bundle in a Laravel application?
- No. It is a Symfony bundle built around Symfony's kernel, container, routing, Doctrine ORM, and Twig. Laravel has no bundle loader and expects service providers, Eloquent, and Blade instead. Embedding it would mean hosting a second framework inside Laravel.
- How do I install genj/faq-bundle?
- You install it with Composer as genj/faq-bundle and register GenjFaqBundle in a Symfony application's kernel. It expects Symfony 3.2-era dependencies, Doctrine, and Twig. There is no Laravel installation path, service provider, or package discovery support.
- Is genj/faq-bundle compatible with Laravel 10 or 11?
- No. Laravel 10 and 11 require symfony/* ^6 or ^7, while this bundle declares Symfony 3.2 compatibility. Composer resolution will fail or force a whole-application downgrade. The package is not maintained for modern Laravel.
- What Laravel version does genj/faq-bundle support?
- None. The package is a Symfony bundle and does not declare Laravel support or provide a Laravel service provider. Its compatibility ceiling is Symfony 3.2, which reached end of maintenance in January 2018.
- Does genj/faq-bundle provide Eloquent models or Laravel migrations?
- No. It ships Doctrine ORM entities and repositories, not Eloquent models or Laravel migrations. You would need to rewrite the persistence layer for Eloquent and recreate the schema, including v2.0.0 scheduling fields, with Laravel migrations.
- How do I configure publishAt, expiresAt, and isActive scheduling in genj/faq-bundle?
- Version 2.0.0 adds isActive, publishAt, and expiresAt fields, but there are no migration notes or documented semantics. You must decide timezone handling, whether expiry soft-hides or returns a 404, and whether scheduled content is cache-visible. In Laravel you would model this with casts, query scopes, and explicit HTTP behavior.
- How does search work in genj/faq-bundle?
- Version 2.0.0 adds a self-described very simple MySQL search, which likely means LIKE '%term%' scans or an unindexed MATCH without relevance tuning. That does not scale beyond a small FAQ table and is hard to cache because it is shaped by user input. For Laravel, use Laravel Scout with Meilisearch or a proper full-text index instead.
- Is genj/faq-bundle maintained and safe for production?
- It is archived and unmaintained, with zero dependents and no documented CVE response path. Version 2.0.0 adds scheduling, naive search, and search-query reporting without migration notes. Production use carries high technical risk, especially around search performance and PII retention.
- How would I test an FAQ feature if I port genj/faq-bundle to Laravel?
- You cannot test the bundle as a Laravel package because there is no Laravel integration to boot. Instead, write Laravel feature tests for your own Eloquent models, HTTP endpoints, and scheduling scopes. Cover publish and expiry visibility, category filtering, search behavior, and any search-query logging retention rules. Do not rely on the bundle's Symfony test suite.
- What are Laravel alternatives to genj/faq-bundle?
- Build a small FAQ domain with Eloquent models for questions, answers, and categories, then expose it through Blade views and Laravel routes. Use Laravel Scout with Meilisearch or database full-text indexes if search matters. A maintained Laravel CMS or FAQ package is preferable to porting an archived Symfony bundle.
Weaver
How can I help you explore Laravel packages today?