Switching to the next page seems to be bugged
-
I am using Chrome. That bein said, when I try to switch to the next page I get thrown back to page one. Example. I am at
https://forums.gta5-mods.com/category/5/general-modding-discussion
and I switch to page 2. For a split second I see
https://forums.gta5-mods.com/category/5/general-modding-discussion?page=2
but then it's back to
https://forums.gta5-mods.com/category/5/general-modding-discussion?page=1
in the address bar.
However, changing manually by replacing the 1 with a 2 in the address bar works.
Note: This only happens if I visited any thread on page 1 before.
-
@Cyron43 I am using Chrome too but I can't reproduce this. Perhaps it's one of your extensions?
-
@Unknown-Modder I just tried to reproduce it but now it works like a charm. Please don't mark this as solved yet. I am looking for a sure fire way to reproduce it.
-
Have this problem as well, but on Android (stock Samsung browser).
-
I've experienced this on Android with Firefox. Only on mobile though, I've never had the problem on desktop.
-
@Jitnaught @Cyron43 @stillhere @Unknown-Modder This seems to be a problem on every type of device. I find this happens on a desktop system too.
Have you tried disabling Wi-Fi VIA your PC's internet settings? Do this, let it sit for 30 max seconds and connect back to the internet, then try scanning the pages again. (<I don't know if this ACTUALLY works but it doesn't hurt to try.)
-
@krashadam I was thinking about it while I was trying to fall asleep last night. It could probably be connected to the internet cache because the odd thing is, once it worked it never failed after that. I'm going to test it with a cleared cache once I have the time for it today. Doing chores...
EDIT: For f***s sake! There must be pixies or something! I disconnected for 30 seconds as you suggested, i cleared the cache but I can't reproduce this error. Seems to be totally random behavior.
-
@Cyron43 Well... well shit. :?
-
@krashadam The only thing I can currently think of is a server side concurrency issue and that's nothing we could test at the client side. @DarthPungz?
I think I rest this case until I get another idea.
