topic Re: Supposed to be permanently signed in in Community Site Feedback

Supposed to be permanently signed in

Luzern — Sat, 02 Nov 2019 15:28:24 GMT

It isn't working for me, as I have numerous times had to sign in. The box I ticked has become unticked.

Why is this happening, I would like to know, with advice how to solve the nuisance,☹️

Re: Supposed to be permanently signed in

VileReynard — Sat, 02 Nov 2019 21:28:50 GMT

I think its a cookie thing.

Perhaps you used a different computer - which causes it to be unset on the first computer....

Re: Supposed to be permanently signed in

Luzern — Sat, 02 Nov 2019 22:50:23 GMT

@VileReynard I've only the one. but as it now seems to be happening on a different site it must be something like that.

Re: Supposed to be permanently signed in

HarryB — Sun, 03 Nov 2019 00:55:05 GMT

If I remember right, this was brought up back when we launched and I think we were told that it's also connected to the IP you're on. So you'd need to log back in if connecting from a different IP despite being on the same device.

EDIT: I'm assuming you're referring to the community forums?

Re: Supposed to be permanently signed in

Mav — Sun, 03 Nov 2019 01:14:43 GMT

Moderator's note(s):

Thread moved from Plusnet Feedback to Community Site Feedback.

Re: Supposed to be permanently signed in

Luzern — Sun, 03 Nov 2019 10:58:45 GMT

@HarryB Unless I am misunderstanding you, that would mean the majority, who don't have a fixed IP address will suffer.

Re: Supposed to be permanently signed in

Baldrick1 — Sun, 03 Nov 2019 12:38:49 GMT

@Luzern

I think that you only risk picking up a new IP address if the DSL link between the router and BT infrastructure drops for any reason.

You haven't got clear cookies on exit set on your browser or an Internet cleaner?

Re: Supposed to be permanently signed in

HarryB — Sun, 03 Nov 2019 20:10:28 GMT

@Luzern wrote:

@HarryB Unless I am misunderstanding you, that would mean the majority, who don't have a fixed IP address will suffer.

Just to confirm, are we both referring to the community forums here? As Anoush pointed out to me that theres a member centre tag on your initial post, which I missed when I responded regarding the community forums.

If we are both talking about the community forums, this isn't a choice we made, rather what Lithium advised us is by design.

Re: Supposed to be permanently signed in

Luzern — Sun, 03 Nov 2019 20:12:53 GMT

@Baldrick1 wrote:

@Luzern

I think that you only risk picking up a new IP address if the DSL link between the router and BT infrastructure drops for any reason.

You haven't got clear cookies on exit set on your browser or an Internet cleaner?

If you mean something like CCleaner, that could be it. Thanks

Re: Supposed to be permanently signed in

Luzern — Sun, 03 Nov 2019 20:16:17 GMT

@HarryB TBH I couldn't make out the label choices, and couldn't post without using one, so took a guess.

Sorry, it was the community (this).

Re: Supposed to be permanently signed in

Baldrick1 — Sun, 03 Nov 2019 21:20:19 GMT

@Luzern

The internet cleaner in Ccleaner would definitely do it.

Re: Supposed to be permanently signed in

198kHz — Sun, 03 Nov 2019 22:16:54 GMT

@HarryB wrote:

If I remember right, this was brought up back when we launched and I think we were told that it's also connected to the IP you're on. So you'd need to log back in if connecting from a different IP despite being on the same device.

Just dropped the DSL and re-connected with a different IP address - still logged in to Community.

Re: Supposed to be permanently signed in

HarryB — Mon, 04 Nov 2019 01:48:29 GMT

@HarryB wrote:
If I remember right, this was brought up back when we launched and I think we were told

@198kHz I've just done a bit of searching through some old posts and it looks like I had in fact, not remembered correctly.

This may have been what I was remembering, which wasn't even an official response from Lithium.

Apologies for any confusion I caused with the previous post(s).

What @Baldrick1 said regarding cookies sounds more likely to be the correct answer.

Re: Supposed to be permanently signed in

Townman — Tue, 05 Nov 2019 10:51:53 GMT

@HarryB

I do not think it is your posts which are confusing, but the system sure is.

I use the forum from home on both phone and laptop connected over WiFi with keep me signed in set.

The laptop (Edge) NEVER requires logging in even between reboots (no cookie cleaning).

The phone (Safari) requires logging in again at least once each 24 hours and always if I change to mobile data. The latter I can accept could be related to a change in IP address ... but such seems to be refuted by the report I a lost above.

This could be browser specific behaviour ... nothing odd around this product surprises me any more - they seem incapable of delivering anything to a professional standard - especially change control.

Re: Supposed to be permanently signed in

Baldrick1 — Tue, 05 Nov 2019 12:29:28 GMT

It certainly can be browser specific. Firefox on my PC always resets the 'keep me signed in' flag. That's because it's set to clear all cookies on exit. My Ipad never resets it unless the 'clear cookies and history' function is used, when the flag is reset.

This convinces me that this function is controlled by a cookie. Keep the cookie and all is well, delete it and you have to save the 'keep me signed in' cookie again.

Re: Supposed to be permanently signed in

VileReynard — Tue, 05 Nov 2019 14:17:48 GMT

I suspect it must also depend on a server side setting - wiping a cookie on one device wipes the cookie on all devices?

Re: Supposed to be permanently signed in

Baldrick1 — Tue, 05 Nov 2019 16:15:20 GMT

@VileReynard

I’ve tried this with two IPads. They definitely work independently with no cross coupling. I’m convinced that the way that it works is that a cookie is placed on each particular device used to log on. Keep that cookie and all is well regardless of the state of other devices also logged in.

You would have thought that any competent outfit would store this choice in your account, but apparently not in this instance.