Trouble editing a member's personal data in LCR?

[jgoggan]

Anyone else having trouble editing a member's data in LCR? This has been going on for months now for us.

Basically, I go to a member's Individual info page in LCR and click the Edit icon. It reloads in edit mode, but the page is almost completely hung. I can sometimes do things in slow motion (like editing a phone number, for example) and eventually my browser will pop up and warn me that the page is running slowly and I can Wait or kill the tab. I'm getting this in both Chrome and a fresh/empty install of Firefox. And I'm getting it across multiple PCs.

Some edits (like a phone number), I can do if I wait long enough. Others (like trying to fix a name problem where there are multiple steps), I can't get through -- it just grinds that tab to a halt until I kill it.

Anyone else seeing this behavior?

[rmrichesjr]

I'm a ward assistant clerk, membership, so I edit member profiles fairly often. I have never seen the LCR pages be unreasonably slow. Here are a couple of possibilities:

From other discussions in the forum, it appears there's a performance problem on Sundays that affects a lot of LCR users. I'm not clear whether it's just finance or both finance and membership that this problem affects. I have gathered from the other discussions that it's a known problem but is not fixable by simply adding server capacity, so a fix won't be happening soon. Waiting until later on Sunday or using LCR another day of the week is likely (but not guaranteed) to help.

The cookie buildup problem can manifest itself with many strange symptoms. The test for whether symptoms are caused by the cookie buildup problem is to try the same operations in private or incognito mode. If that makes the problems go away, clearing your browser's cache and deleting cookies from Church domains will make the problem go away for a while--rinse and repeat.

[jgoggan]

Thanks for the response. I should have clarified some more things that I have tried:

1. Other days besides Sundays. It doesn't matter. And, to be clear, this is not the normal "the website is slow today" thing. It's actually running something that is causing my browser to hang. It's like something never loads and it just waits forever burning CPU cycles.

2. I've tried it on a fresh install of Firefox -- and also in Incognito mode -- so no existing cookies at all would exist.

Thanks anyway though.

[russellhltn]

What computer is this on? Have you tried a different one? I'm wondering if either the machine is ill, or if some security software is getting involved where it shouldn't be.

[rmrichesjr]

Both Chrome and Firefox (and probably other browsers, as well) have a 'web console' that can show things about what is happening with the Javascript being executed on a page. Often, a little sleuthing can help find the root cause of problems. In some cases when necessary, the Inspector can allow you to modify attributes of problematic page elements to get them out of the way.

[BrianEdwards]

You may also want to have another Bishopric member with edit permissions try the same actions on his laptop. If he's successful with no issues, then have him log out of his church account, and using the exact same web browser session, then you can log into your church account and try editing data. If this works for him but does not for you, then have him log back into his church account using the same browser session. If it works again for him, then I'd definitely think a call to GSD is in order as that would indicate something related to your church account.

[jgoggan]

What computer is this on? Have you tried a different one? I'm wondering if either the machine is ill, or if some security software is getting involved where it shouldn't be.

Yes, as I said, I have tried multiple computers and browsers.

[jgoggan]

Both Chrome and Firefox (and probably other browsers, as well) have a 'web console' that can show things about what is happening with the Javascript being executed on a page. Often, a little sleuthing can help find the root cause of problems. In some cases when necessary, the Inspector can allow you to modify attributes of problematic page elements to get them out of the way.

Yes, I've actually checked that also. It dumps out "RangeError: Maximum call stack size exceeded" from angular.js. But even with normal pages, their JS dumps out quite a few errors. So I can't tell if that is the real problem or just every day for the site.

EDIT: Interestingly, if you search for this error in angular -- the general response is that it means there is bad code causing an infinite loop. Which exactly seems to line up to the problem I am experience with it locking up the browser. It feels like it is just in a tight loop burning CPU.

[jgoggan]

You may also want to have another Bishopric member with edit permissions try the same actions on his laptop. If he's successful with no issues, then have him log out of his church account, and using the exact same web browser session, then you can log into your church account and try editing data. If this works for him but does not for you, then have him log back into his church account using the same browser session. If it works again for him, then I'd definitely think a call to GSD is in order as that would indicate something related to your church account.

This is my next step. I've tried everything I can think of on my own. I just need to have someone else give it a try on various devices and see if it follows them or my account only. Hopefully on Tuesday I'll do more testing with this.

[garystroble]

Yes, I have seen this also, although not real recently. It is definitely a headquarters issue, as have seen it on multiple platforms and browsers. It might have something to do with massive changes they are working on and perhaps testing live or rolling out in increments. Sometimes one has to outguess the software, which is not fun as it eats up a lot of time.

And I just noticed that when trying to send a family to the Spanish Branch in our building (their address did not change) that the software wiped the address even though I asked it to use the same address. Fortunately I noticed it before the final step and cancelled and had to start over and enter their address manually. Our software is like a box of chocolates, you never know what you're going to get.