drcook345 wrote:Yeah, for some reason my google calendar is not getting updates.
How long are you waiting? I'm not sure how often Google scans for updates, but I think it's on the order of a couple of times a day, not every few minutes.
drcook345 wrote:Yeah, for some reason my google calendar is not getting updates.
samliddicott wrote:I'm sorry that didn't work.
So we are just waiting for someone who has never tried before to use the https link first time with google. I've added no-caching and robots.txt for no-search engines onto the wrapper page.
cdoyle wrote:Sam, ok so if I did what you asked correctly, I grabbed the synch URL off the church site, pasted it into the Google calender "Add by URL" field, added the "s" so it said "https://..." and clicked OK.
Error message back from Google - could not fetch the URL.
cdoyle wrote:Sam, ok so if I did what you asked correctly, I grabbed the synch URL off the church site, pasted it into the Google calender "Add by URL" field, added the "s" so it said "https://..." and clicked OK.
Error message back from Google - could not fetch the URL.
Would you like me to try something else or should I just go to using the wrapper?
Chris
I just tried it again, and Google Calendar gave me a quick "Failed to add imported calendar..." message when I did the "Add by URL" option for the pure URL from the Sync page on the lds.org Calendar. So I'm not seeing any change in how it is working (or more accurately, not working).BellMR wrote:So for some reason tonight the pure LDS.org calendar URL starting working for me (don't know how long it will last though). Anyone else see a change from not-working to working?
BellMR wrote:Well that was short lived. Even though I brought in the calendar. It is not getting updates. I made a few event changes days ago, and they aren't reflected on the Google side.
samliddicott wrote:In private messaging I learn that there some people for whom the work-around-wrapper doesn't work and where google makes no request from my server.
I suppose that google does some kind of caching magic which helps it decide not to bother trying again.
A solution which has worked is to make use of the flexibility of the wrapper, for example, if your work-around wrapper was:
https://mail.liddicott.com/ldscalendar.php/987654321
and this is not working, then try:
https://mail.liddicott.com/ldscalendar. ... lendar.ics
You can make up any file name you like on the end, and it will still work.
Such tricks has made the wrapper work in cases where google has otherwise refused to make any requests from my server.
I note that the ics file obtained from the LDS servers is very sparse and doesn't even identify which internal LDS calendar an event came from. If this is improved in a later release then I will be able to add filtering to the wrapper-URL's so that perhaps it may be possible to have URL's like:
https://mail.liddicott.com/ldscalendar. ... lendar.ics
to recieve a subset of calendars on your phone - and of course you could have multiple subset URLs