# New Custom HomePage, Back to Forum URL

**URL:** <https://meta.discourse.org/t/new-custom-homepage-back-to-forum-url/329863>\
**Category:** Development\
**Created:** [October 8, 2024, 12:39pm UTC](https://meta.discourse.org/t/new-custom-homepage-back-to-forum-url/329863 "2024-10-08T12:39:57Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![paulswithers](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/paulswithers/32/309235_2.png) [@paulswithers](https://meta.discourse.org/u/paulswithers)\
**Post date:** [October 8, 2024, 12:39pm UTC](https://meta.discourse.org/t/new-custom-homepage-back-to-forum-url/329863/1 "2024-10-08T12:39:57Z")

</div>

I came across the new [custom homepage](https://github.com/discourse/discourse/pull/26291) and it works great for adding a new page. But the “Back to Forum” link from the Admin page adds “/custom” onto the end of the URL. Presumably because this is not added to the Rails router, refreshing the page returns the dreaded " Oops! That page doesn’t exist or is private." message.

Is there any way round this?

We also plan on using the Doc Categories plugin, as used on this site for the Documentation category. That means a lot of users will also have the “Back to Forum” button.

Worst case scenario, I can probably re-write the “Back to Forum” URL in a theme component, the class name looks unique. But I’m wondering if there’s a better approach or maybe this is an edge case not previously identified, and needs a more robust fix adding to Discourse.

---

_[View the full topic](https://meta.discourse.org/t/new-custom-homepage-back-to-forum-url/329863)._