Creating collection project with invalid date input fails unexpectedly, can produce in-limbo project

Bug Reports
8

seems like the triggering problem if you try to create projected noted in Step 2 of the original post is that “12/31/1999” is an invalid date format. (1999-12-31" would be the expected format.)

it seems like there’s no validation on the screen itself to make sure the date is valid (which is probably a bug that should be fixed), and it fails when the server tries to process the date. so the project gets partially created (the project slug gets registered), but it has no rules. so it seems to get stuck in a limbo state, where you can sort of view the partially-created project from https://www.inaturalist.org/projects/before-2000?collection_preview=true, but you might not be able to edit it from https://www.inaturalist.org/projects/before-2000/edit.

it’s possible to just add another project with the same Project Name (ex. “Before 2000”), but it’ll get an extra encoded string at the end of the project slug (ex. https://www.inaturalist.org/projects/before-2000-a2f998a8-012c-4573-9c5b-2fb1ff4020d3, instead of https://www.inaturalist.org/projects/before-the-year-2000), since the original slug is already reserved.

so the original project in limbo needs to be deleted first. if the edit page is not working from https://www.inaturalist.org/projects/before-2000/edit, then it’s possible to delete the project using a call to the API. in Windows, one way to accomplish that would be:

  1. while signed into iNaturalist, open https://www.inaturalist.org/users/api_token in your web browser.
  2. that should display something like {"api_token":"J.W.T"}, where J.W.T will be some encoded string. copy the J.W.T value.
  3. open your Windows start menu, and run “cmd” to open the command line editor.
  4. at the command prompt, run curl -X DELETE "https://api.inaturalist.org/v1/projects/before-2000" -H "Content-Type: application/json" -H "Accept: application/json" -H "Authorization: %JWT%", making sure you replace %JWT% with the value you copied from step #2 above.

…

one more thought: it might be useful to update the title of the thread to reflect the fundamental issue, as opposed to the case where the issue was encountered.