- Is presta/cms-faq-bundle a Laravel package?
- No. Despite being listed among PHP packages, presta/cms-faq-bundle is a Symfony 2 bundle built specifically for PrestaCMS. It ships no Laravel service provider, no facade, no publishable config, and no awareness of the Laravel container. Its FAQ content is modelled as Doctrine entities and managed through SonataAdminBundle, which are Symfony-era components rather than anything from the illuminate stack.
- Can I install presta/cms-faq-bundle in a Laravel application with Composer?
- Realistically, no. Sonata Admin and its Symfony 2 dependencies pin versions of symfony/form, symfony/http-foundation, symfony/event-dispatcher and doctrine packages that conflict with illuminate/* requirements. Even with --ignore-platform-reqs workarounds you would be loading two HTTP kernels, two form components and two event dispatchers into a single process. There is no supported coexistence story between these frameworks.
- Which Symfony and PHP versions does PrestaCMS FAQ Bundle support?
- It targets the Symfony 2 era, with its last release dated 2014-02-26. That means no PHP 7 or PHP 8 compatibility and no modernisation of Doctrine DBAL or ORM. Installing it on a current PHP runtime is not a supported configuration.
- How is FAQ content structured inside this bundle?
- FAQ content is stored as Doctrine entities, with categories containing ordered questions and answers. Editors manage them through SonataAdminBundle CRUD screens, and the content is surfaced on the frontend through PrestaCMS page blocks and Twig templates. The data model itself is simple, which is why reimplementing it natively is usually faster than integrating the bundle.
- What is the best way to add categorized FAQs to a Laravel application?
- Create two migrations, faq_categories and faqs, with a foreign key, a position column for ordering, a published_at column for publication state, and either a locale column or a translations table if you need multiple languages. Add the corresponding Eloquent models and a small admin resource, either with Filament, Nova, Backpack or plain resource controllers. This is a straightforward build that gives you full control over caching, validation and authorisation.
- How do I migrate existing PrestaCMS FAQ content into Laravel?
- Treat it as a data extraction rather than a code integration. Inventory the faq and faq_category tables plus any translation tables and block configuration that references them, then export to JSON or CSV, one file per locale, preserving category and question ordering. Import those files into your native Laravel schema with a seeder or an artisan command. The bundle's code itself does not need to come along.
- Is presta/cms-faq-bundle maintained and safe to run in production?
- It is effectively abandoned, with roughly a decade without maintenance, zero stars and zero dependents. There are no security patches, no PHP 7 or 8 support and no community triaging issues or publishing forks. Any CVE in the frozen Symfony 2, Sonata or Doctrine dependency tree becomes yours to patch in code you did not write.
- Can I reuse the bundle's admin screens or Twig templates in Laravel?
- No. Sonata Admin's 2014-era UI and authentication model would have to be reconciled with your Laravel admin access, or run as a second authenticated surface, and its Twig block pipeline has no equivalent in Blade. The domain logic is small enough that rebuilding the category and question CRUD screens in your existing admin tooling is an afternoon of work. Use the bundle only as a reference for schema shape and field layout if you find it useful.
- How should I handle SEO when replacing old PrestaCMS FAQ pages with Laravel routes?
- Before decommissioning the old site, capture the public FAQ URLs and any category or question slugs, then add 301 redirects to the equivalent new Laravel routes. Preserve heading structure, question wording and answer text where the content is still accurate so rankings carry over. Also keep an XML sitemap entry for the new FAQ index and category pages so search engines recrawl them promptly.
- Are there Laravel alternatives to this Symfony FAQ bundle?
- You generally do not need a package at all: two migrations, two models and a resource controller cover categories, ordering, publication state and multilingual content. If you want ready-made admin tooling, Filament, Laravel Nova or Backpack can generate the CRUD screens from those models in minutes. That approach keeps you on supported dependencies and avoids pulling a second framework into your application.