The Church of Jesus Christ of Latter-day Saints

Looking at the waning messages you get when you download the .csv though, almost everybody that does it is going to be doing it for church use. Granted, they might be doing it for a personal/church reason, but if it's related to the church, then they are probably going to bypass the warning as they ...

Hmmm...well, I guess I'll take what I can get.

Thanks, RC

Hey guys, Maybe I have missed it in the training videos and such that I have watched, but myself (clerk) and the bishopric all have no idea how to delete some of the "Other-" accounts that we have listed on our ward budget within MLS. Some other-accounts have been set up in the past that did have a ...

The restrictions on how versitile and organized you can really make the ward websites is one of the main reasons why I rarely (< 5%) use the ward sites for anything other than the calendar to be honest.

There is some definite potential there once we get some enhancements going, though.

Any chance we can see a snapshot of the menu as it stands today? It would be nice to have a look at what the church considers appropriate in each of menu categories. This is very interesting. When I read your description I realized we could use something like this where I work. We all informally kn...

I really like the idea about the short biographies, I think I might have to borrow that idea. Thanks for mentioning that, pmouritsen!

Yeah, having the talks broken down individually is very nice. I had to work through the last few General Conference sessions, so being able to pull them back up and watch/listen/read them is really great.

The church recently sent the stake clerks and/or stake web admins to all of the wards in our stake to reimage the hard drives and to set up a password on them all as well. They told me that it was something being done church-wide. Your ward clerk should have this password, as I am the clerk for my w...

tomw wrote:Some type of ical exporter would be cool.

Tom

Definitely.

mkmurray wrote:
method()
{
...
}

That's how I've always done it.

I've seen a number of ways used as the "standard", but this is the one that I prefer myself.