Unread/Recent/Nav buttons don't work within categories/topics

[Lonkle]

I just use the "recents" tab and intentionally went and ignored all the apps I didn't care about and that achieved a similar result for me. Do you think what you're experiencing is a NodeBB specific bug or Cloudron routing issue?

[robi]

@Lonk it's feeling like a routing issue with this specific 4 part domain.

[Lonkle]

@robi So this is happening on your personal install that has more than one subdomain then?

[Lonkle]

Important to read NGINX logs when testing too. I always forget that they're so easily accessible in the Services tab.

[robi]

@Lonk said in Unread/Recent buttons don't work within categories/topics:

@robi So this is happening on your personal install that has more than one subdomain then?

No, it's a client machine with a dyndns setup.

[Lonkle]

@robi Can you reproduce the error while watching the NGINX log?

[robi]

@Lonk said in Unread/Recent buttons don't work within categories/topics:

@robi Can you reproduce the error while watching the NGINX log?

it's not an nginx issue.

it's a problem with how NodeBB generates the URL for the top buttons like /recent.

I don't know why it would be doing the extra URI paths when all it needs to do is /recent.

[Lonkle]

So this is def a nodebb bug...then?

[robi]

@Lonk said in Unread/Recent buttons don't work within categories/topics:

So this is def a nodebb bug...then?

that would be a rash conclusion at this point.

I did post it here in the NodeBB section with the hopes to find out the actual reason, configuration or bug or otherwise.

[girish]

@robi When I installed a NodeBB plugin, the navigations links did become corrupt once and I had to fix it by going to /admin/settings/navigation and editing all the entries one by one. I reported this on their forum but didn't get any real response.

[Lonkle]

@robi Have you switched to a regular singular sub domain and tested to see if the double sub-domain is the real issue at hand here?

[girish]

@Lonk said in Unread/Recent buttons don't work within categories/topics:

@robi Have you switched to a regular singular sub domain and tested to see if the double sub-domain is the real issue at hand here?

Yeah, this is a good idea to check out as well. Just clone the forum to another place and check if the links are correct.

[robi]

@girish said in Unread/Recent buttons don't work within categories/topics:

@robi When I installed a NodeBB plugin, the navigations links did become corrupt once and I had to fix it by going to /admin/settings/navigation and editing all the entries one by one. I reported this on their forum but didn't get any real response.

This is a good suggestion, but I don't have enough access to do this and I don't see anything wrong with these entries.

[robi]

@girish
If I could, I'd have done this already.
It's a dyndns that only lets you control xxx.sub.domains, and not sub.domains.

Which is also why I asked for anyone with a wildcard domain for repro|comparison.

[girish]

@robi said in Unread/Recent/Nav buttons don't work within categories/topics:

This is a good suggestion, but I don't have enough access to do this and I don't see anything wrong with these entries.

What I meant is the thing on the left side named "Route". Does it say "/categories" for you? In my case, it had become"corrupt" like "/categories#xxx" something.

[robi]

it just says categories without the leading /

[robi]

@girish thank you that was it!

I changed all the routes for all the menu items to start with a / and we're good now.

Like you said, it must have been a plugin that changed the routes

[Lonkle]

@robi said in Unread/Recent/Nav buttons don't work within categories/topics:

@girish thank you that was it!

I changed all the routes for all the menu items to start with a / and we're good now.

Like you said, it must have been a plugin that changed the routes

Niceeeee. Always feels good to fix a weird problems - glad you got it figured out! ️