Weave Code
Slugger Bundle Laravel Package
gibilogic/slugger-bundle
gibilogic/slugger-bundle is a PHP bundle for generating clean, URL-friendly slugs from titles and text. It provides reusable slugging utilities and configurable behavior for Symfony-style applications, helping keep routes and content identifiers consistent.
A slugger service for Symfony 2
Frequently asked questions about Slugger Bundle
- Can I use gibilogic/slugger-bundle in a Laravel application?
- No, gibilogic/slugger-bundle is a Symfony 2 bundle, not a Laravel package. Laravel has no bundle registration, no AppKernel, and no auto-discovery path that will pick it up. Using it inside Laravel means manually reconstructing the Symfony service container wiring by hand, at which point you are consuming a class file rather than a package. For normal Laravel slug generation, use Str::slug or a Laravel-native sluggable package.
- Does gibilogic/slugger-bundle support Laravel 10 or Laravel 11?
- No. Symfony 2-era bundles typically constrain PHP to ^5.3|^7.0 and symfony/* to ^2.x, so on PHP 8.1+ with a modern Laravel skeleton this will either fail Composer resolution or require --ignore-platform-reqs. That flag is not an acceptable default for a production dependency. The package was last released in October 2018 and has no Laravel support path.
- What is the difference between gibilogic/slugger-bundle and Laravel's Str::slug()?
- Laravel's Str::slug() is built into Illuminate\Support\Str and is maintained with the framework. gibilogic/slugger-bundle is a Symfony bundle that almost certainly delegates transliteration to an underlying library such as cocur/slugify and adds Symfony-flavored configuration around it. In Laravel you get the same core slug behavior natively without the abandoned Symfony integration layer.
- How do I install gibilogic/slugger-bundle with Composer?
- For a Symfony 2 application you would run composer require gibilogic/slugger-bundle and register the bundle in AppKernel. There is no Laravel installation path because Laravel does not use Symfony bundles or an AppKernel. If Composer refuses to resolve on modern PHP, do not force it with --ignore-platform-reqs for production.
- Is gibilogic/slugger-bundle still maintained?
- No. The last release was October 2018, it has zero stars and zero dependents, and Symfony 2 reached end of life in November 2018. There is no security patch path, no maintainer responsiveness signal, and no downstream community that would surface breakage before you do. The bus factor is effectively one, with no visible activity in seven years.
- What Laravel package should I use instead of gibilogic/slugger-bundle?
- Use Laravel's native Str::slug() for simple string slugging. For Eloquent model slugs, use actively maintained Laravel-native packages such as spatie/laravel-sluggable or cviebrock/eloquent-sluggable. If you need unique, stable, locale-aware slugs with redirect history, treat that as a first-party design problem rather than something this bundle solves.
- Does gibilogic/slugger-bundle handle transliteration and unique slugs?
- The bundle advertises transliteration of Unicode characters into ASCII equivalents and collision handling for unique slugs across records. In practice it is probably a thin wrapper over cocur/slugify plus Symfony configuration, so the real behavior lives in the underlying library. Check whether tests document separators, lowercasing, uniqueness suffixes, and Unicode handling before relying on any of it. For Laravel, Str::slug covers transliteration and Laravel-native sluggable packages cover uniqueness.
- Is gibilogic/slugger-bundle compatible with PHP 8?
- Very likely not without workarounds. Symfony 2-era bundles typically constrain PHP to ^5.3|^7.0, and this package has been unmaintained since 2018. On PHP 8.1+ Composer will probably fail to resolve or require --ignore-platform-reqs. Forcing resolution does not make the code PHP 8-safe.
- Can I extract the slugging logic from gibilogic/slugger-bundle into a Laravel service provider?
- Only if the bundle contains custom business rules beyond a thin wrapper, such as locale tables, domain-specific transliteration, or a uniqueness strategy you would otherwise write. If so, port the service class into app/Support/ or a small first-party package, wrap it in a SlugServiceProvider, and bind a Slugger contract in the container. Discard the Symfony bundle shell, including Extension, Configuration, and Resources/config. Confirm the license permits extraction and re-hosting before you copy any code.
- What are the alternatives to gibilogic/slugger-bundle for unique, locale-aware slugs in Laravel?
- Laravel-native tools handle the common case: Str::slug for strings and spatie/laravel-sluggable or cviebrock/eloquent-sluggable for model-backed unique slugs. Locale-aware slugs with redirect history are a larger design problem involving persistence, routing, and redirect tables, and this bundle will not solve that. Start with a first-party Slugger service and a config/slugger.php file rather than adopting an abandoned Symfony 2 bundle.
Weaver
How can I help you explore Laravel packages today?