It works but doesn't autocomplete. Yes, we know about this and it's being addressed.Did anybody not notice the @ function no longer works ?
It works but doesn't autocomplete. Yes, we know about this and it's being addressed.Did anybody not notice the @ function no longer works ?
Is the upgrade also causing issues with remaining logged in? I’m having to login pretty much everytime I try and view the forums. I obviously have selected keep logged in as well as safari, chrome and Firefox (all on iPhone/iOS) and closing the tab means I have to log on again as well as it timing out.
Is the upgrade also causing issues with remaining logged in? I’m having to login pretty much everytime I try and view the forums. I obviously have selected keep logged in as well as safari, chrome and Firefox (all on iPhone/iOS) and closing the tab means I have to log on again as well as it timing out.
Same issue with firefox/PC. Lost track of the amount of times I've deleted cookies trying to see if I can fix things. However I can stay logged in fine when using my phone/chrome.
Same issue with firefox/PC. Lost track of the amount of times I've deleted cookies trying to see if I can fix things. However I can stay logged in fine when using my phone/chrome.
Might have a solution for not remaining logged in. Check the bookmark/address you’re using for the new forum address. Make sure it’s https and not just http. That seems to keep it logged in.
Might have a solution for not remaining logged in. Check the bookmark/address you’re using for the new forum address. Make sure it’s https and not just http. That seems to keep it logged in.
Browser: Microsoft Edge Chromium 85.0.564.44 (Official build) (64-bit)
This SSL/HTTPS issue is annoying, not 100% sure what would be causing this, however;
Browse to https://www.overclockers.co.uk/forums (Not secure) message appears.
Browse to https://overclockers.co.uk/forums (Not secure) message appears. (As a test)
I then log in > sign in fine, I get;
After checking dev tools in the browser I can't see what would be causing this, nothing in the dev tools suggestion content been loaded over http but this might mean it's transporting the username and password in plain text to the servers. I haven't tested this theory though.
This seems to be the case. I was adamant the issue only turned up after the forum update but it's now started appearing for other sites. Seems chrome just made their policy stricter, but it's really distracting. Ultimately I'll be ignoring more warnings!It's peoples signatures, some people have http signatures so certain threads show as not secure.
This seems to be the case. I was adamant the issue only turned up after the forum update but it's now started appearing for other sites. Seems chrome just made their policy stricter, but it's really distracting. Ultimately I'll be ignoring more warnings!
It's peoples signatures, some people have http signatures so certain threads show as not secure.
Not in this case it isn't though surely as if it was signatures then it would show in dev tools with the link as the page is loaded surely?
I mean in this instance I'm not even logged in, cache was cleared to test and I have tested in private window just in case.
I found something that it may be related...