swigginton wrote:I called the FH department in SLC. They walked me through many of the steps I've already done. Of course, since it works fine for them (being on the church network), their focus was on browser config, etc. Once we got past that, they felt it should be discussed with the global services support. I called them, and went through pretty much the same steps before they seemed to give up and said they didn't know what to do. I'm pursuing a couple of parallel paths to raise awareness/urgency of the issue, including trying to reach someone at HQ who oversees the Family History Days events, since they would have an interest in seeing this fixed. We'll see what happens.
Try not to drive yourself crazy working through the insanity. The Church is just NOT setup to work with a member rather than an employee.
I experienced all these same things when the Kansas City Temple Open House reservation went live without the church turning it on for external access. Everything you described here was my experience (it works for me, etc...) - i asked them to page out their network team, but they said the only thing they could do was log a point. I couldn't understand how much the team seemed NOT to care that thousands of members of the church were being impacted by something that eventually took about 5 minutes work for the network team. (there ended up also being a leap-year problem in the logic which also took a bit to fix also). Multiple Stake Presidents were unable to get it escalated either.
It's not really their fault either, it is just how they are organized.
“A long habit of not thinking a thing wrong, gives it a superficial appearance of being right, and raises at first a formidable outcry in defense of custom.”
― Thomas Paine, Common Sense
