Cannot access main Church website...?

[BrianEdwards]

For about a month I cannot access Church website links from Instagram on my iPhone. So I tried Google search, but pages would not load.
Thanks for figuring out the problem as many more are finding this reporting tech page.

Have you tried working with your ward clerk? You may also have a Technology Specialist called in your ward who can help out. Although quite often issues reside on the Church-side of things, sometimes it is something specific to the member. In those cases, working with somebody local, can often help identify and resolve the underlying issue.

[russellhltn]

For about a month I cannot access Church website links from Instagram on my iPhone. So I tried Google search, but pages would not load.

There are a couple of possible issues. Church pages suffer from "cookie buildup" that causes all kinds of problems. You may need to clear the church cookies out of whatever browser Instagram is using.

The other issue is if your membership records are not in any ward, there will be a number of pages you can no longer access. In that situation, you'll need to contact your ward clerk to make sure your records are in the ward.

[ambldsorg]

There are a couple of possible issues. Church pages suffer from "cookie buildup" that causes all kinds of problems.

In other words, the Church website has some bugs that need to be fixed. Is anyone aware of an open bug for this?

[russellhltn]

Is anyone aware of an open bug for this?

For quite some time.

[ambldsorg]

For quite some time.

Well, I've been aware of the problem for a long time too, but I've never opened an actual official IT support ticket for it. So what I was asking was more about is there an actual open ticket for it that anyone has filed and can share information about? Is it being worked on?

[russellhltn]

Well, I've been aware of the problem for a long time too, but I've never opened an actual official IT support ticket for it. So what I was asking was more about is there an actual open ticket for it that anyone has filed and can share information about? Is it being worked on?

I don't have any details on that. I believe the developers who visit us are aware of it, but I think the issue is the decision makers have higher priority tasks that need to be worked on. I also suspect this is a infrastructure issue, so it would require a high-level fix.

[BrianEdwards]

Well, I've been aware of the problem for a long time too, but I've never opened an actual official IT support ticket for it. So what I was asking was more about is there an actual open ticket for it that anyone has filed and can share information about? Is it being worked on?

I'm a big fan of encouraging everyone affected by any issue, to always submit their own Feedback ticket. It's difficult to analyze from the outside, but I expect that it's reasonable to hope that when an issue has an avalanche of user feedback, it might get bumped up in priority. But if an issue only has one or two Feedback submissions, it might be easier to keep it at the bottom of whatever lists they have.

Although Church development priorities aren't driven by member feedback, there's nothing bad about adding another voice to the fray. We may never know if it makes a difference, but I do enjoy the placebo effect

[mevans]

I'm a big fan of encouraging everyone affected by any issue, to always submit their own Feedback ticket. It's difficult to analyze from the outside, but I expect that it's reasonable to hope that when an issue has an avalanche of user feedback, it might get bumped up in priority. But if an issue only has one or two Feedback submissions, it might be easier to keep it at the bottom of whatever lists they have.

Although Church development priorities aren't driven by member feedback, there's nothing bad about adding another voice to the fray. We may never know if it makes a difference, but I do enjoy the placebo effect

I've given up (for the most part) bothering to submit feedback about problems on the church websites. Considering that the response to almost any problem you submit is a canned response to clear your cookies, it seems like they're well aware of the problem and it's not going to get fixed soon. When there is a problem, you have to get beyond the first-level support people who think clearing your cookies is the answer to every problem (and they tell you to do that even if your problem submission says you've already cleared your cookies). Depending on the problem, there are times I'll put in more effort to convincing support that there's a problem, but I find it's generally too much effort to bother submitting problems. I appreciate there are people there trying to help resolve problems, and I suspect they may be volunteers who are trying to do their best. but I wish the church would take a different approach. What they're doing now doesn't work well.