Lemmy.world Support

3280 readers

24 users here now

Lemmy.world Support

Welcome to the official Lemmy.world Support community! Post your issues or questions about Lemmy.world here.

This community is for issues related to the Lemmy World instance only. For Lemmy software requests or bug reports, please go to the Lemmy github page.

This community is subject to the rules defined here for lemmy.world.

To open a support ticket

You can also DM https://lemmy.world/u/lwreport or email [email protected] (PGP Supported) if you need to reach our directly to the admin team.

Follow us for server news 🐘

Outages 🔥

https://status.lemmy.world

founded 2 years ago

MODERATORS

Direct comment links seem to have stopped working in some situations (self.support)

submitted 2 years ago by MurdoMaclachlan to c/support

3 comments fedilink hide all child comments

I've noticed very recently (last two days or so) that when I get a direct link to a specific comment, it won't load anything under certain circumstances.

Following the link from the button on the comment, either from the profile or from viewing other comments on the post, will work, but using the link as the URL for a post in a different community, or opening a new tab and pasting the link in, don't.

In the former situation, the UI of the post I gave it as the URL for just freezes until I press the back button, still showing the post. In the latter, Lemmy doesn't load at all.

I'm using Librewolf 116.0, based on Firefox 116.0.

you are viewing a single comment's thread
view the rest of the comments

[–] dx1 1 points 2 years ago* (last edited 2 years ago)

Is that what they said? Often with single page app setups you have unrecognized routes return the main index.html with JS files etc. by default, and then detect the URL path and feed that into the SPA router. From checking in inspector it looked like it was failing to authenticate when loading the route via XHR, like some kind of on-page context was missing that would be required for that request, i.e., it's not redirecting to the index page and is maybe rewriting straight to the API endpoint. Not sure myself though.