Hello Rob,

Updates done in the gadget for over 24h are still not reflected in the
gadget
A few examples:
- http://www.ljmsite.com/google/gadgets/worldclocks.xml
- http://www.ljmsite.com/google/gadgets/worldclocks4.xml

If you can force these 2 to be re-fetched ASAP that would be very
helpful as the DST time changes, which are in the gadget itself, are
currently missing for many users.

Cheers,

Jerome

On Oct 26, 2:18 am, Rob Russell <[email protected]> wrote:
> Hi Jerome,
> Can you give the url of the gadget?
>
> iGoogle respects the cache control headers sent with your gadget and should
> update within hours if the gadget spec changes. Currently, if only message
> bundles or supporting files change this may not be detected.
>
> Regards,
> Rob Russell
> Google Developer Relations
>
>
>
>
>
>
>
> On Wed, Oct 13, 2010 at 7:37 AM, Jerome <[email protected]> wrote:
> > I continue receiving several customers reports that the gadget is out
> > of date on a daily basis... Any Googler's input on this issue, and a
> > resolution ETA?
>
> > Cheers,
>
> > Jerome
>
> > On Oct 7, 2:26 am, Jerome <[email protected]> wrote:
> > > The gadget XML specs used to take around a couple of hours to become
> > > live on users' iGoogle page. This has been working great for years.
>
> > > In the past week, I have been receiving loads of problem reports from
> > > users of my gadgets saying they are seeing on their iGoogle page a
> > > gadget that is a few days old to over a week old (my gadget spec is
> > > updated on an infrequent basis). I instructed them to do a Ctrl + F5
> > > while on iGoogle and for most of them it solved the issue. A few users
> > > (on Google Chrome especially) are reporting that the Ctrl + F5 does
> > > not help though.
>
> > > My gadget has 100,000s of users and it is clearly working as expected
> > > for many of them, but there is a Google introduced problem impacting
> > > quite a few. As I can not reproduce the issue on my test systems, I
> > > can not give you more input, but my guess is that someone at Google
> > > has been experimenting with http caching headers in an attempt to save
> > > bandwidth but broke how gadgets have been working for years.
>
> > > Please look into this, and let me know if you need further
> > > informations.
>
> > > Cheers,
>
> > > Jerome
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "iGoogle Developer Forum" group.
> > To post to this group, send email to [email protected].
> > To unsubscribe from this group, send email to
> > [email protected]<Google-Gadgets-API%2Bunsubs 
> > [email protected]>
> > .
> > For more options, visit this group at
> >http://groups.google.com/group/Google-Gadgets-API?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"iGoogle Developer Forum" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/Google-Gadgets-API?hl=en.

Reply via email to