# באגים קטנים עם נושאים במעקב ונושאים מפוצלים

**URL:** <https://meta.discourse.org/t/small-bugs-with-tracked-topics-and-split-topics/163624>\
**Category:** Bug\
**Created:** [10 בספטמבר,‏ 2020,‏ 2:31pm UTC](https://meta.discourse.org/t/small-bugs-with-tracked-topics-and-split-topics/163624 "2020-09-10T14:31:05Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![simon](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/simon/32/339122_2.png) [@simon](https://meta.discourse.org/u/simon)\
**Post date:** [10 בספטמבר,‏ 2020,‏ 5:42pm UTC](https://meta.discourse.org/t/small-bugs-with-tracked-topics-and-split-topics/163624/2 "2020-09-10T17:42:29Z")

</div>

I _think_ this is a bug and not a UX issue. The problem is being caused by the lack of a forward slash at the start of the link’s `href`. For example, for my user, the ‘read this topic’ link is set to `u/simon_cossar/preferences/notifications`. Editing the `href` in the console to `/u/simon_cossar/preferences/notifications` fixes the issue for me.

I just ran into a similar issue with a navigation link that was added through the Nav Links theme component. In that case, the `href` was set to `latest?solved=no`. That would take the user to the not-found page if the nav link was clicked from any page other than the site’s homepage. It is my understanding that the link in this form was previously working, but it now needs to be set to `/latest?solved=no`.

Has something changed with the way Discourse handles these links?

---

_[View the full topic](https://meta.discourse.org/t/small-bugs-with-tracked-topics-and-split-topics/163624)._
