Fix OrganizationPage slug regeneration on name changes #3002
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
When changing an organization's name in Wagtail CMS (e.g., changing "MIT" to "MIT - Universal AI"), the page slug was being automatically regenerated. This caused several issues:
The root cause was in the
OrganizationPage.save()
method, which unconditionally regenerated the slug on every save:Solution
Changed the slug generation to only occur when the slug is empty (new object) or not set, following the same pattern used by the
Department
model incourses/models.py
:Additionally, removed
promote_panels = []
to expose the slug field in Wagtail admin, allowing administrators to manually edit slugs when needed.Changes
b2b/models.py
: Added conditional check for slug generation and removed promote_panels restrictionb2b/models_test.py
: Added 3 comprehensive tests covering all scenarios:Behavior
Testing
Fixes the slug regeneration issue while maintaining all existing functionality for new organizations.
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.