- Is tadcka/sitemap-bundle a Laravel package?
- No. Despite the Composer name, tadcka/sitemap-bundle is a Symfony bundle, not a Laravel package. It does not ship a Laravel service provider, facades, config publishing, Artisan commands, or Blade views. Treat it as Symfony 2/3-era code rather than something you can drop into a Laravel app.
- Can I install tadcka/sitemap-bundle in Laravel 10, 11, or 12?
- Practically, no. The bundle was last released in 2017 and targets the Symfony 2.7/3.0 era with old PHP constraints, while modern Laravel runs PHP 8.1+ and Symfony 6/7 components. Composer will likely refuse the install or resolve a degraded dependency tree. There is no maintained Laravel integration surface to wire it into the container.
- What PHP and Symfony versions does tadcka/sitemap-bundle target?
- The bundle belongs to the PHP 5.5/5.6/7.0 and Symfony 2.7/3.0 generation. Its last release date was 2017-02-19, well before modern PHP 8 strictness and Symfony Flex conventions. It is not designed for PHP 8.1+ or Symfony 6/7, so modern Laravel and Symfony applications should not expect compatibility.
- What does tadcka/sitemap-bundle actually do?
- The author describes it as a simple web page list manager. It is an admin-oriented Symfony bundle for maintaining a list of pages, URLs, and metadata rather than a modern sitemap.xml generator. If your goal is SEO sitemap generation, the package’s purpose and architecture may not match the problem you are solving.
- Is tadcka/sitemap-bundle maintained or safe for production?
- There is no evidence of active maintenance: the project has one star, zero dependents, and a single release cadence that ended eight years ago. Abandoned PHP 5/7-era code raises risks around unpatched transitive Symfony 2.x dependencies, PHP 8 incompatibilities, and missing security advisory coverage. Treat it as unsupported third-party code requiring full source ownership, not as a production dependency.
- What should I use instead of tadcka/sitemap-bundle in Laravel?
- For Laravel sitemap generation, use a maintained Laravel-native package such as spatie/laravel-sitemap. It is PHP 8 compatible and supports crawler- and query-builder-based sitemap generation with lastmod, changefreq, and priority. If you also need an editorial page list, model that metadata in your own application rather than adopting an abandoned Symfony bundle.
- Can I use tadcka/sitemap-bundle with Symfony 6 or Symfony 7?
- No, not realistically. The bundle predates Symfony Flex, modern autowiring defaults, and the current recipe system, so it does not fit current Symfony application conventions. In a modern Symfony project, evaluate maintained options such as presta/sitemap-bundle or routing-based sitemap generation instead.
- How do I generate sitemap.xml in Laravel without this package?
- Use spatie/laravel-sitemap, or write a small scheduled job that emits XML from your routes or database queries. Include the URLs plus optional lastmod, changefreq, and priority values, then test the generated XML response. This keeps the capability in-house with a maintained dependency instead of vendoring old Symfony code.
- Does tadcka/sitemap-bundle provide Artisan commands, migrations, or Blade views?
- No. Those are Laravel package conventions, and this project follows Symfony bundle conventions instead. It expects Symfony kernel registration, DI extension classes, and Symfony routing/config patterns. Hand-porting the handful of useful classes would leave little more than a data model idea, not a real package integration.
- Why not just hand-port the useful classes from tadcka/sitemap-bundle?
- Because the bundle contributes almost nothing beyond an idea for managing a page list. Porting abandoned code still leaves you owning unsupported logic, old dependency assumptions, and security review work. Reframe the task as a small in-house capability backed by a maintained package such as spatie/laravel-sitemap, and reject the old bundle as an integration candidate.