Sylius Location Bundle Laravel Package

Getting Started

This is an initial assessment for the v0.4.1 line. The release is small and targeted: it circumvents an issue when using Sylius Resource Bundle with the Gedmo Sluggable listener on an extended entity, and it is published as part of the Sylius v1.0.0-beta.1 release cycle.

Start by checking:

1. composer.json for Sylius, Doctrine, Gedmo, and PHP version constraints.
2. The package README and tests for the Sylius Resource Bundle integration path.
3. Sylius Resource Bundle docs for resource/entity configuration.
4. Gedmo Sluggable docs for listener registration and slug field configuration.
5. The v0.4.1 diff/tests around extended entities, since that is the only behavior called out in the release notes.

Minimal first use case: define or extend a Sylius resource entity, add a slug field managed by Gedmo Sluggable, register the Gedmo listener, and confirm that creating/updating the extended entity through Sylius Resource Bundle produces the expected slug without the previous conflict.

If you are in a Laravel-only application, verify that the package actually exposes Laravel integration before adopting it. The release notes are Sylius/Doctrine-centric, so the primary audience is PHP/Symfony/Sylius developers working with Sylius resources and Gedmo behavior.

Implementation Patterns

Use this release when you have an extended Sylius resource entity and want Gedmo Sluggable to generate slugs reliably.

Common patterns:

• Configure the slug field on the extended entity, not only on the base entity, and verify the mapping inheritance is correct.
• Register the Gedmo Sluggable listener in the Doctrine event system according to your Sylius version’s service configuration.
• Create entities through Sylius Resource Bundle factories/controllers so the resource lifecycle is exercised, then assert the slug is generated on persist/update.
• Add an integration test that uses an extended entity, because the v0.4.1 fix is specifically about that combination.
• Keep slug generation behavior in the entity/listener layer rather than duplicating it in controllers or form handlers.
• If you have multiple resource entities, test one simple entity and one extended entity to isolate whether the issue is inheritance-related.
• For existing data, backfill slugs with a controlled migration or command, then rely on the listener for new/updated records.

Integration tips:

• Pin the package version in composer.json while on the 0.4.x line; pre-1.0 releases can move quickly.
• Confirm the Sylius beta constraints are compatible with your application before upgrading.
• Run Doctrine schema validation and cache clearing after changing entity inheritance or listener configuration.
• Exercise both create and update flows; slug listeners can behave differently when the slug source field changes.

Gotchas and Tips

• This is a narrow patch, not a broad feature release. If you do not use Sylius Resource Bundle with Gedmo Sluggable on an extended entity, v0.4.1 likely does not change your day-to-day usage.
• The release is tied to Sylius v1.0.0-beta.1. Treat Sylius beta compatibility as a real constraint and test against the exact Sylius version you deploy.
• Extended entity mapping is the likely failure point. Check inheritance type, mapped superclass configuration, and whether the slug field is declared in the right place.
• Listener ordering matters. If another Doctrine listener modifies the slug source field, confirm Gedmo runs at the expected time.
• Clear Symfony/Sylius caches after changing services, Doctrine mappings, or listener registration. Stale container configuration can make a correct fix appear broken.
• Debug using the Doctrine EventManager and confirm the Gedmo Sluggable listener is attached exactly once. Duplicate registration can cause confusing slug behavior.
• Watch unique constraints on slug columns. The fix addresses listener/resource interaction, but it does not remove the need for collision handling or unique-index errors.
• No breaking changes or deprecations are called out in the v0.4.1 notes. Still review the diff before upgrading if you depend on internal services or listener wiring.
• Treat v0.4.x as pre-1.0: pin versions, read release notes, and keep an integration test around extended-entity slug generation as your main regression guard.