The Church of Jesus Christ of Latter-day Saints

You can also ask your SP if you can be given the calling of Assistant Technology Specialist. That way, you would be able to see the list of names yourself on post events. The list is currently NOT in an easy downloadable format. Each name must be clicked on to see the viewing time and other info. Th...

According to a email I got from mht: A Meraki AP will not be able to connect to the internet if the Switch Port is still configured as "Public" in TM. This will also provide a bad, hard to troubleshoot wireless experience. Now that you mention it, I recall reading that. Before I move it t...

On this page https://www.churchofjesuschrist.org/study/church-historians-press/jsp-revelations/map-js-residences?lang=eng The link to the enlarged image is not correct: https://bit.ly/3la0fXc Might have been down for a while, but I Just tried with Chrome & Firefox and the link appears to be wor...

I learned from personal experience this process can take 2 weeks or more, so if you're looking for a tax benefit for this year, you might want to start the process soon.

lajackson wrote:They will have to know the event code which does not appear on the webcast page.

Ahh, that part I didn't know until I just now tried it. That makes it acceptable for a stake conference.

Amazing what I learn in this forum that the documentation doesn't quite cover.

Sadly, no. If it helps any, this has been requested quite a bit, so hopefully it will make it into some future update.

It used to hide them. Now it shows, but indicates a church account is required to view it. I noticed that too and I personally think it's a big step backwards. I don't necessarily want all my test events visible to the stake. Also, when the time comes that we go back to doing simple building-to-bui...

It's still strange, because https has been working on mywebcast for a couple of months now that they fixed their certificate error.

I haven't heard of anyone having a problem like that in our stake. Probably because we only give out the viewing link provided on the Meetinghouse Webcast Dashboard, which is currently http://, not https://. If/when the church changes that, we'll also change what we instruct our members to use.

According to a email I got from mht: A Meraki AP will not be able to connect to the internet if the Switch Port is still configured as "Public" in TM. This will also provide a bad, hard to troubleshoot wireless experience. Now that you mention it, I recall reading that. Before I move it t...