Newsshow css empty

[skseo]

Hi, i am using the newsshow api and since a while, the css is empty

http://www.google.com/uds/api/elements/1.0/3376eafaba5be418d41605957d5c4d40/newsshow+de.css

that doesn´t look very nice

[Aghilmort]

This may give one idea of a work around -- http://www.reddit.com/tb/h719c/

at least en.css also reported as ticket #582 at
http://code.google.com/p/google-ajax-apis/issues/detail?id=582

On May 12, 2:46 pm, skseo <s.kuebler.sk...@googlemail.com> wrote:
> Hi, i am using the newsshow api and since a while, the css is empty
>

> http://www.google.com/uds/api/elements/1.0/3376eafaba5be418d41605957d...

[skseo]

i don´t use a language to have the auto detect.

i also starred the issue

thanks

On May 12, 10:02 pm, Aghilmort <aghilm...@gmail.com> wrote:
> This may give one idea of a work around --http://www.reddit.com/tb/h719c/
>
> at least en.css also reported as ticket #582 athttp://code.google.com/p/google-ajax-apis/issues/detail?id=582

[Aghilmort]

yeah, was using auto-detect previously -- am specifying language
temporarily until issue fixed. Not perfect, but site looked bad
otherwise. cheers.

[skseo]

i like the way but i use it in differnet countries, so iám lost at the
moment

wrong horse

[Adam Feldman]

Hi everyone,

We're aware of this problem and working on it.  I hope to be able to report an ETA soon.

In the mean time, it's only the en version of the CSS that's messed up, so Aghilmort is correct that if you specify any other language CSS (including en-GB), it will be fine.  Apologies for the need to do this.

Thanks for your patience,

Adam

--
You received this message because you are subscribed to the Google Groups "Google AJAX APIs" group.
To post to this group, send email to google-ajax...@googlegroups.com.
To unsubscribe from this group, send email to google-ajax-searc...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-ajax-search-api?hl=en.

[skseo]

thanks adam,

i count on you

On May 12, 11:14 pm, Adam Feldman <adam.feld...@google.com> wrote:
> Hi everyone,
>
> We're aware of this problem and working on it.  I hope to be able to report
> an ETA soon.
>
> In the mean time, it's only the en version of the CSS that's messed up, so
> Aghilmort is correct that if you specify any other language CSS (including
> en-GB), it will be fine.  Apologies for the need to do this.
>
> Thanks for your patience,
> Adam
>

[Aghilmort]

Thanks, Adam, good to hear & appreciate the response. Best, Chris

On May 12, 4:14 pm, Adam Feldman <adam.feld...@google.com> wrote:
> Hi everyone,
>
> We're aware of this problem and working on it.  I hope to be able to report
> an ETA soon.
>
> In the mean time, it's only the en version of the CSS that's messed up, so
> Aghilmort is correct that if you specify any other language CSS (including
> en-GB), it will be fine.  Apologies for the need to do this.
>
> Thanks for your patience,
> Adam
>

[skseo]

:-) now it is working. was there a workaround or is it random?

at this time i press the like button

On May 12, 11:14 pm, Adam Feldman <adam.feld...@google.com> wrote:
> Hi everyone,
>
> We're aware of this problem and working on it.  I hope to be able to report
> an ETA soon.
>
> In the mean time, it's only the en version of the CSS that's messed up, so
> Aghilmort is correct that if you specify any other language CSS (including
> en-GB), it will be fine.  Apologies for the need to do this.
>
> Thanks for your patience,
> Adam
>

[Adam Feldman]

I believe this should now be fixed (except possibly for a few edge cases involving caches).  Please let us know if you're still experiencing this on your page.

Thanks,
Adam

[Aghilmort]

appears to work @ http://chris-augeri.com/blog/ -- commented out
setting en-GB so reverts to auto-detect, flushed cache, loads ok (&
also tested with "en" which was also failing before setting to "en-
GB".

thanks, Adam. aghilmort out.

On May 13, 10:20 am, Adam Feldman <adam.feld...@google.com> wrote:
> I believe this should now be fixed (except possibly for a few edge cases
> involving caches).  Please let us know if you're still experiencing this on
> your page.
>
> Thanks,
> Adam
>