Hi Jeremy,
You've won!
Unfortunately, you've won the first confirmed bug report of the 2.5 release. 😬😓
I've reproduced this in my local test environment - it seems it's a regression that snuck in last minute into the 2.5 release. I've filed a bug ticket for this here:
Since this has broken a major module in AtoM, we'll be sure to include a fix for this in our next release.
In the meantime, you can use SQL to manually edit a slug. Start with the existing slug to look up the object_id value:
- SELECT object_id FROM slug WHERE slug='your-slug-here';
This will output a value like the following example:
+-----------+
| object_id |
+-----------+
| 82269 |
+-----------+Now we can use the object_id value to update the current slug in the slug table:
- UPDATE slug SET slug="my-new-slug" WHERE object_id=82269;
Not ideal, but hopefully this will help you make do until we can release a fix!
Cheers,