# Avoid using "archived" as a goal's slug

**URL:** <https://forum.beeminder.com/t/avoid-using-archived-as-a-goals-slug/9183>\
**Category:** Bugabee\
**Created:** [April 12, 2021, 8:39am UTC](https://forum.beeminder.com/t/avoid-using-archived-as-a-goals-slug/9183 "2021-04-12T08:39:21Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![zzq](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.beeminder.com/zzq/32/6471_2.png) [@zzq](https://forum.beeminder.com/u/zzq)\
**Post date:** [April 12, 2021, 8:39am UTC](https://forum.beeminder.com/t/avoid-using-archived-as-a-goals-slug/9183/1 "2021-04-12T08:39:21Z")

</div>

It turns out that if you create a goal with the slug `archived` you won’t have any way of accessing the goal page: visiting `/<username>/archived` takes you to your gallery of archived goals, of course.

This is very inconvenient, not the least because it makes it a bit tricky to archive or delete such a goal; the buttons which do so being on the inaccessible goal page.

You _can_ delete the goal, with a bit of cleverness, and a bit of `curl`: there’s nothing actually preventing you from manually sending that `DELETE` request which the deletion form on the goal page would send, if you had access to it.

Nevertheless, this is a rather painful trap to fall into. Ideally, Beeminder would prevent you from using `archived` as a goal’s slug at goal-creation time.
