- Can I install psliwa/pdf-bundle in a Laravel application?
- No. psliwa/pdf-bundle is a Symfony2 bundle, not a Laravel package, and it expects Symfony's kernel, dependency-injection container, and bundle configuration. Laravel's service container, package discovery, config publishing, and facades do not map to it. The only potentially reusable layer is the underlying psliwa/PHPPdf library, which would need a custom Laravel adapter.
- Does psliwa/pdf-bundle support Laravel 10 or Laravel 11?
- There is no official support for Laravel 10, Laravel 11, or any modern Laravel version. The bundle targets end-of-life Symfony2 and its Composer constraints are likely to conflict with current PHP and Laravel dependencies. Run a disposable compatibility spike before assuming it can be used in any form.
- How do I install psliwa/pdf-bundle?
- It is installed with Composer into a Symfony2 application and registered through the Symfony kernel and bundle configuration. It is not designed for Laravel installation or Laravel package discovery. If you only need the rendering engine, evaluate psliwa/PHPPdf directly instead of installing the Symfony bundle.
- What PHP versions does psliwa/pdf-bundle require?
- Symfony2-era bundles typically assume PHP 5.x and old Symfony components, so modern PHP 8.1+ support is unlikely without patching. You should verify Composer requirements against your target runtime before any design work. Expect deprecated APIs, dependency conflicts, and possible fatal errors on current PHP versions.
- What is the difference between psliwa/pdf-bundle and psliwa/PHPPdf?
- psliwa/pdf-bundle is the Symfony2 integration layer, while psliwa/PHPPdf is the underlying XML-markup-driven PDF generation library. The bundle adds Symfony configuration and container wiring that Laravel cannot use. A Laravel team could only consider wrapping PHPPdf directly behind a PdfGenerator interface after a proof of concept.
- Is psliwa/pdf-bundle maintained and safe for production?
- It has low community validation, zero dependents, and targets end-of-life Symfony2, which signals high technical risk. PHPPdf appears legacy and may pull in unsupported or unpatched dependencies. Do not recommend this bundle for new production Laravel work without a security review and a clear maintenance plan.
- What are good Laravel alternatives to psliwa/pdf-bundle for generating PDFs?
- Laravel-friendly options include Dompdf, mPDF, Snappy with wkhtmltopdf, and Browsershot, depending on your HTML and CSS fidelity requirements. These are generally maintained and easier to integrate through Laravel service providers and queues. Choose based on output quality, performance, font support, and long-term maintenance needs.
- Can I reuse PHPPdf XML templates from Symfony in Laravel?
- PHPPdf uses XML-based templates, so reuse is technically possible only if you consume psliwa/PHPPdf directly rather than the Symfony bundle. You would need a Laravel adapter and golden-file regression tests to confirm output compatibility. Preserve existing templates only after a bounded proof of concept proves the library runs on your target PHP version.
- How should I test a PHPPdf integration in Laravel?
- Start with a time-boxed proof of concept in a CLI command or queued job, not through the Symfony bundle. Generate one representative invoice or report, then compare output against expected documents with golden-file regression tests. If successful, isolate the renderer behind an interface and add contract tests before production use.
- Is psliwa/pdf-bundle a good choice for invoices and reports in Laravel?
- No, it is not recommended for new Laravel work because it is a Symfony2 bundle built around a legacy PHPPdf rendering stack. Use a maintained Laravel-compatible PDF package unless PHPPdf output compatibility is mandatory. Even then, treat it as an isolated adapter project after proving the underlying library works on PHP 8.1+.