Cannot remove released person's name in LCR

[RoseKJ]

I have a Welfare and Self-Reliance Specialist who was released. He was one of two that we have in the ward. In LCR, I click on the Release button and then Save but nothing happens. A Window opens asking for a membership record number. Does that mean I can't remove the released individual without replacing him? What if we only need one Welfare and Self-Reliance Specialist?

[russellhltn]

I'd try using incognito mode. Cookie build-up does strange things.

If that doesn't work, I'd call support and have them open a ticket for the developers.

[RoseKJ]

I logged in using incognito mode and it worked! After removing the person and clicking SAVE it actually removed them from the calling.

[rmrichesjr]

I logged in using incognito mode and it worked! After removing the person and clicking SAVE it actually removed them from the calling.

When incognito or private mode solves the odd symptoms, that usually means you can clear your browser's cache and delete Church-related cookies to make the symptoms go away for a good while.

[russellhltn]

Thanks for letting us know that worked!

[ambldsorg]

When incognito or private mode solves the odd symptoms, that usually means you can clear your browser's cache and delete Church-related cookies to make the symptoms go away for a good while.

That usually means there is a bug in LCR. Please submit feedback on the appropriate LCR page and hopefully this will be fixed.

[rmrichesjr]

That usually means there is a bug in LCR. Please submit feedback on the appropriate LCR page and hopefully this will be fixed.

I won't disagree that it's a bug. I won't disagree that it's annoying, and it would be nice if it were fixed.

However, the cookie build-up problem seems to affect everything on the Church website, not just LCR. The basic attributes of the problem are well-known and have been around for quite a number of years. With it being known for so long and affecting so many parts of the site, it's not likely one more report will do much toward getting it fixed. I think there's an explanation somewhere on the forum from a Church employee about resource not having been allocated to fix it, but there are so many other threads where the problem has been mentioned that I was not able to find it.

I have also seen mention of a similar-sounding cookie build-up problem on other sites.

[russellhltn]

I'm guessing the cookie build up problem has something to do with church login. That could be quite a undertaking to update that bit of infrastructure.

I have no idea why the cookies get so big. Currently it's 47MB in my browser.

[ambldsorg]

However, the cookie build-up problem seems to affect everything on the Church website, not just LCR.

Yes, my comment was not intended to deny the existence of the same bug elsewhere within the Church websites. I've seen it manifest itself with many of the tools.

I have also seen mention of a similar-sounding cookie build-up problem on other sites.

If by "other sites" you mean sites that are unaffiliated with the Church, yes, it's quite possible and very likely that this happens because they all use similar "frameworks".

I've noticed a recent change with the Church login that may also contribute to the problem; it seems that now the Church websites "remembers" my login name so it makes it look like I'm logged in, but in fact am not. Then when I try to click to login it just redirects me back to the main page and doesn't actually offer me the option to login. I have to "trick" it by clicking on something that actually needs authentication.

I might experiment with my browser settings to disallow the Church from saving any data in the persistent storage and only permit ephemeral cookies that go away when I close my browser. Sometimes deterministic behavior, even if onerous, is better than the frustration of inconsistent and unpredictable behavior.

[ambldsorg]

I might experiment with my browser settings to disallow the Church from saving any data in the persistent storage and only permit ephemeral cookies that go away when I close my browser.

Doesn't seem to be that flexible. I suppose the most deterministic option is to always use a private window (or incognito mode) for that. This has the added benefit that if one is in the habit of so doing, one will likely improve the security of ones account through that same force of habit.