Prevent certain slugs from being created
|Assignee:||Michelle Curran||% Done:|
|Target version:||Release 2.5.0|
|Google Code Legacy ID:||Tested version:|
Prevent slugs being created with a value of 'api' or 'sword'.
#7 Updated by Steve Breker about 1 month ago
- Assignee changed from Steve Breker to Michelle Curran
Hi Michelle - this change is to prevent a slug from being created with these reserved names when a new description is created in AtoM using the WebUI. In this test scenario you are describing, does a description with a slug of 'sword' already exist in AtoM? It should not have been allowed to be created.
Also, do you have the fix for DIP upload in your AtoM environment (https://projects.artefactual.com/issues/12932)? This fix should be in place before testing the above behaviour.
#8 Updated by Michelle Curran about 1 month ago
In my test scenario last week, I was able to create a description with a slug of 'sword' in AtoM using a hosted deployment (https://atom25.1604.qa.accesstomemory.net), but that could have been an outdated box. I just checked Alfred and it looks as though this box was last updated earlier today so I've re-tested and now, AtoM does not allow me to create a description with a slug of 'sword'. When I try to use either 'api' or 'sword', the slug automatically gets a number increment after I click 'Create' in the web UI. In Archivematica, when I check the error message for the 'Upload DIP' task, I see some unprocessed html in the stderr.
As far as this issue goes, I can say the bug fix has been verified.