-
@mariner4life yes. Wrong fucking thread, of course
I keep having this issue where, unless I refresh the entire forum, anything I do gets "Forbidden" notifications. This time I reloaded and went to the wrong thread
-
@nta said in Aussie Rugby:
@mariner4life yes. Wrong fucking thread, of course
I keep having this issue where, unless I refresh the entire forum, anything I do gets "Forbidden" notifications. This time I reloaded and went to the wrong thread
I get that also
-
@nta said in Aussie Rugby:
@mariner4life yes. Wrong fucking thread, of course
I keep having this issue where, unless I refresh the entire forum, anything I do gets "Forbidden" notifications. This time I reloaded and went to the wrong thread
take the hint...
-
If you're seeing a bug post about it in the 'Tech Help' forum otherwise it's likely I won't see it
It seems to be the same/similar as this one:
csrf error if user goes to 404 first · Issue #9287 · NodeBB/NodeBB
Go to https://community.nodeb.org/doesnotexist Ajaxify to /recent and try to post a topic Forbidden error due to invalid csrf_token
That is fixed in the next release
I can force it by going to an incorrect TSF url, getting a 404 error and then continuing to use the forum without refreshing.
If it's happening often I would assume it's because you are hitting a 404 error often. Maybe the url you use to navigate to the forum is incorrect? Maybe you often click on something that doesn't exist?
-
@nta said in 'Forbidden' error:
@mariner4life yes. Wrong fucking thread, of course
I keep having this issue where, unless I refresh the entire forum, anything I do gets "Forbidden" notifications. This time I reloaded and went to the wrong thread
I only get it on my phone and if I close the reply box, refresh the page and click reply again it works...
-
@taniwharugby said in 'Forbidden' error:
I only get it on my phone and if I close the reply box, refresh the page and click reply again it works...
That's logged on thier github page too. They suggest trying the same fix.
I'll try it after the weekend
-
@taniwharugby said in 'Forbidden' error:
@nta said in 'Forbidden' error:
@mariner4life yes. Wrong fucking thread, of course
I keep having this issue where, unless I refresh the entire forum, anything I do gets "Forbidden" notifications. This time I reloaded and went to the wrong thread
I only get it on my phone and if I close the reply box, refresh the page and click reply again it works...
Same, a refresh always works, that's why I didn't raise an issue troubling our codemaster
-
@duluth said in 'Forbidden' error:
@taniwharugby said in 'Forbidden' error:
I only get it on my phone and if I close the reply box, refresh the page and click reply again it works...
That's logged on thier github page too. They suggest trying the same fix.
I'll try it after the weekend
Ha! Tried to like your post and:
-
I've just applied the small code fix mentioned above. Maybe it helps, maybe it doesn't.
This was the fix for the incorrect url bug. Which seems to be a different bug than you guys had (it might be the same symptom but a different cause.. we'll see)
-
FYI . I do a refresh a few times and I win. whether its a soft or hard refresh who knows I just go in and out a bit shut a few boxes hope for the best!?!
I don't have the right priviledges apparently, that too, had that one trying to post YouTube linkI'm not complaining though
-
@duluth said in 'Forbidden' error:
@nta thanks
Ok so went to the Hawt thread via the notification list - bones had quoted my post and replied with "toot toot".
Tried to upvote and got the Forbidden pop-up so tried again for same result.
Refreshed page via pull-down swipe and could run the upvote no issues
-
@nta said in 'Forbidden' error:
Ok so went to the Hawt thread via the notification list - bones had quoted my post and replied with "toot toot".
Tried to upvote and got the Forbidden pop-up so tried again for same result.
Refreshed page via pull-down swipe and could run the upvote no issues
I can't force it so I can't troubleshoot it
Reading elsewhere it appears one or two other forums have this bug but most don't. I suspect it'll be a version of nodejs or another component.
When I have time get everything onto the latest recommended versions
'Forbidden' error
