Problem with forums after updating to v47.0.2631.71
-
operafanuk last edited by
Possible bug found?
OS Win7 Pro 32-bit in Dev stream (from which I post this). Also happens on Win10 Home v1703 64-bit.
Please note my last post.
Soon as I logged out, I got the error message as first described, instantly. Then had trouble navigating again.
Action taken:
Stopped trying to navigate and logged back in.
Result: - Navigation okay and operating as normal.
Conclusion: Could this be something to do with login, remembering we recently had a redirection issue? Hope this helps.
-
leocg Moderator Volunteer last edited by
Problem still happening for me on all up to date versions on every stream.
I don't think it has been fixed yet.
Today I saw it happening on latest Developer build and also in Chrome for Android.
Seems settled on dev at this time [while logged in] which I guess is what you're finding at this moment?
It happens here even when I don't login or if I'm already logged in.
-
operafanuk last edited by
Hi Leo and Sgun, thanks for that info. This time came onto forums using Win10 (1703) Home 64-bit, v47.0.2631.71 Stable stream, and got the error at once.
So as above, I stopped trying to navigate and logged in, at which point it became more 'stable'.
Pleased you guys able to see the issue as this provides good info for the devs after their [hopefully relaxing] weekend.
-
operafanuk last edited by
Once you're successfully logged in it doesn't happen again.
Like Leo, I'm finding it doesn't matter whether or not logged in.
It does however appear to raise the error much less when logged in.
Also behaves more 'stable' when logged in (at this time).
The error doesn't appear time dependent with me.
-
operafanuk last edited by
Hi amatczak, same happening from IE browser (from which I post this for testing).
Perhaps the login/logout/redirection forums process? as every time you logout, the error (as above) instantly appears. Happens at blogs as well.
Many thanks.
-
operafanuk last edited by
Hi amaczak, confirmed all working smoothly once again, thank you.
Regarding Blogs, as mentioned in my first post, when trying to read changelogs at blogs, the exact same error appeared. Have just checked and now appears okay after the fix.
Thanks to all the team and Devs.