# 404 Galore - Can I be the only one?

**URL:** <https://community.fibery.io/t/404-galore-can-i-be-the-only-one/5057>\
**Category:** Get Help\
**Created:** [September 1, 2023, 1:04pm UTC](https://community.fibery.io/t/404-galore-can-i-be-the-only-one/5057 "2023-09-01T13:04:15Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Robert\_B](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/robert_b/32/7198_2.png) [@Robert\_B](https://community.fibery.io/u/Robert_B)\
**Post date:** [September 1, 2023, 1:04pm UTC](https://community.fibery.io/t/404-galore-can-i-be-the-only-one/5057/1 "2023-09-01T13:04:15Z")

</div>

Perhaps because I’m the one to choose to migrate our team to Fibery, I am playing many roles: user, tester, architect, developer, evangelist.

One thing I keep running into is 404 pages that result from setting something up one way at one point in time then finding a better way to do it later. So littered through our spaces are scores of missing/deleted entities.

Is there any kind of way to more efficiently address this, kind of like a private .htaccess? I imagine it SHOULD not be such a problem over time. But wondering if there’s something more efficient than hunting them down one-by-one (of course we could scrape the spaces to add some economies of scale in finding what’s broken, but that’s a bit hacky).

Thanks!

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [September 1, 2023, 1:07pm UTC](https://community.fibery.io/t/404-galore-can-i-be-the-only-one/5057/2 "2023-09-01T13:07:25Z")

</div>

Can you give a concrete example. Is it where you have mentioned an entity/document, but the entity has subsequently been deleted?  
If that’s the case, then it would suggest that we need to make it more obvious when deleting an entity/document that there are references that point to it.  
The references field allows users to see when something is being mentioned, but I guess not everyone looks there carefully before deleting.

---

<div class="post-metadata">

**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\
**Post date:** [September 1, 2023, 2:37pm UTC](https://community.fibery.io/t/404-galore-can-i-be-the-only-one/5057/3 "2023-09-01T14:37:38Z")

</div>

> [@Chr1sG](#):
>
> make it more obvious when deleting an entity/document that there are references that point to it.

That is a great idea 😀  
Perhaps the existing “Really Delete?” confirmation could include info like:

> **Really delete?**  
> This entity is referenced in 79 places 😲