Tech Forum

Sam,

Good news - Since I added your workaround with the -test URL, I got a single e-mail from Google announcing a genuinely new calendar entry!!
It looks like your change to standardize the UID worked. Now if we can get the official LDS.ORG calendar to stop changing the UIDs...

samliddicott wrote:BUGS: Two mostly-similar events will have the same UID. Perhaps if a ward diary and stake diary have the same event with same start time and same summary and same description, then they will be given the same UID.

Considering the possibility of the same event being placed on multiple calendars, your "bug" might be considered a feature.

chrissv wrote:Sam,

Good news - Since I added your workaround with the -test URL, I got a single e-mail from Google announcing a genuinely new calendar entry!!
It looks like your change to standardize the UID worked. Now if we can get the official LDS.ORG calendar to stop changing the UIDs...

Great. I'll move that test calendar script to be the regular calendar script.

I note that the description seems to be emitted after the UID so in fact the description is not contributing to the UID the way I coded things. I suppose it doesn't matter very much. It gives a possibility that at least some part of the event can change and it be detected as a changed event rather than a new event - it would be a new event if the summary changed.

Does anyone still have any problems with this or is it just me left?

I also have tested various of (http|https) and ([url]http://www.|new.|)lds.org[/url] without much success. Havn't tried the workaround at all since I thought the official one worked.

It's not just you, but I think I'm the only one that can get neither the Church link to work, nor Sam's.
D.G.

roger.stegeby wrote:Does anyone still have any problems with this or is it just me left?

I also have tested various of (http|https) and ([url]http://www.|new.|)lds.org[/url] without much success. Havn't tried the workaround at all since I thought the official one worked.

Good news. I am told that even though the problem is on Google's side, that the church office developers have come up with a work around. A new release could come out as early as tomorrow, or early next week.

GrasseDD wrote:It's not just you, but I think I'm the only one that can get neither the Church link to work, nor Sam's.
D.G.

Agreed! Tried every workaround and only Sam's wrapper worked. Be sure to look closely at the URL pasted in from Sam's test page. I had an errant '123456' included that was causing it to fail. Look forward to what anyone has that will have this update correctly and directly. Thanks Sam!

mnorto3 wrote:Agreed! Tried every workaround and only Sam's wrapper worked. Be sure to look closely at the URL pasted in from Sam's test page. I had an errant '123456' included that was causing it to fail. Look forward to what anyone has that will have this update correctly and directly. Thanks Sam!

Yes, Sams wrapper does work for me as well, but looking forward for the official workaround

I tried the https://new.lds.org.... and it didn't work for me. I tried this after attempting to import for about 3 hours. Then I found your thread.

I've tried the following:

just https

https://new.lds.org

https://mail.liddicott.com/ldscalendar.php/

When I tried your version, I received an error, "could not fetch the URL"

Any ideas?

-Neil

steinhnj wrote:I tried the https://new.lds.org.... and it didn't work for me. I tried this after attempting to import for about 3 hours. Then I found your thread.

I've tried the following:

just https

https://new.lds.org

https://mail.liddicott.com/ldscalendar.php/

When I tried your version, I received an error, "could not fetch the URL"

Any ideas?

-Neil

Yes. My web server had stopped with some file-system templating problems. It's being fixed now. Sorry - but don't forget to add your calendar id on to the end of the address, you post didn't make clear that you were doing that.

My server has now been fixed, calendar URLs should be working again.