Did something change in the gadget URL pattern? Since a few time, I sometimes get the user preferences at the end of the content URL, in a hash (#) starting with gadgetId and gadgetOwner.
The consequences are that the user preferences are not available anymore in the query string for the server. This breaks the logics of the application.
Could please answer these 3 questions :
- Why did you change the pattern of the URL of URL gadgets?
- Why is this change partial and the pattern is not the same on all
machines and browsers?
- Was this change announced somewhere and I missed it?
As you could guess, this change had a deep impact and should have been
prepared !
On Apr 15, 11:45 am, tintin <efat...@gmail.com> wrote:
> Did something change in the gadget URL pattern? Since a few time, I
> sometimes get the user preferences at the end of the content URL, in a
> hash (#) starting with gadgetId and gadgetOwner.
> The consequences are that the user preferences are not available
> anymore in the query string for the server. This breaks the logics of
> the application.
> Why this change?
-- You received this message because you are subscribed to the Google Groups "iGoogle Developer Forum" group.
To post to this group, send email to Google-Gadgets-API@googlegroups.com.
To unsubscribe from this group, send email to Google-Gadgets-API+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/Google-Gadgets-API?hl=en.
On Fri, Apr 16, 2010 at 12:47 PM, tintin <efat...@gmail.com> wrote:
> Hi Google team,
> Could please answer these 3 questions :
> - Why did you change the pattern of the URL of URL gadgets?
> - Why is this change partial and the pattern is not the same on all
> machines and browsers?
> - Was this change announced somewhere and I missed it?
> As you could guess, this change had a deep impact and should have been
> prepared !
> On Apr 15, 11:45 am, tintin <efat...@gmail.com> wrote:
> > Did something change in the gadget URL pattern? Since a few time, I
> > sometimes get the user preferences at the end of the content URL, in a
> > hash (#) starting with gadgetId and gadgetOwner.
> > The consequences are that the user preferences are not available
> > anymore in the query string for the server. This breaks the logics of
> > the application.
> > Why this change?
> --
> You received this message because you are subscribed to the Google Groups
> "iGoogle Developer Forum" group.
> To post to this group, send email to Google-Gadgets-API@googlegroups.com.
> To unsubscribe from this group, send email to
> Google-Gadgets-API+unsubscribe@googlegroups.com<Google-Gadgets-API%2Bunsubs cribe@googlegroups.com>
> .
> 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 Google-Gadgets-API@googlegroups.com.
To unsubscribe from this group, send email to Google-Gadgets-API+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/Google-Gadgets-API?hl=en.
http://efattal.fr/google/circulation/index2.php?exp_track_js=1&st=c%3... *
#gadgetId=117686598556411394567&gadgetOwner=103717838980366056510&gadgetVie wer=103717838980366056510&rpctoken=1027925751&ifpctok=1027925751&up_pseudo= efattal&up_guid=&up_city=bordeaux&up_lastMsg=20091029&up_ads=
*
As you can see, in the 2nd URL, the user preferences are not in the query
string but in the hash (the italics part). Which means that the server
cannot use them to build the response. I had to completely modify several
gadgets which now behave like inline gadgets: they get the user specific
content with ajax request.
Thanks for helping to understand better what is happening.
> Can you give an example of where you've had this problem? A link to the
> gadget spec would be helpful.
> Rob Russell
> Google Developer Relations
> On Fri, Apr 16, 2010 at 12:47 PM, tintin <efat...@gmail.com> wrote:
>> Hi Google team,
>> Could please answer these 3 questions :
>> - Why did you change the pattern of the URL of URL gadgets?
>> - Why is this change partial and the pattern is not the same on all
>> machines and browsers?
>> - Was this change announced somewhere and I missed it?
>> As you could guess, this change had a deep impact and should have been
>> prepared !
>> On Apr 15, 11:45 am, tintin <efat...@gmail.com> wrote:
>> > Did something change in the gadget URL pattern? Since a few time, I
>> > sometimes get the user preferences at the end of the content URL, in a
>> > hash (#) starting with gadgetId and gadgetOwner.
>> > The consequences are that the user preferences are not available
>> > anymore in the query string for the server. This breaks the logics of
>> > the application.
>> > Why this change?
>> --
>> You received this message because you are subscribed to the Google Groups
>> "iGoogle Developer Forum" group.
>> To post to this group, send email to Google-Gadgets-API@googlegroups.com.
>> To unsubscribe from this group, send email to
>> Google-Gadgets-API+unsubscribe@googlegroups.com<Google-Gadgets-API%2Bunsubs cribe@googlegroups.com>
>> .
>> 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 Google-Gadgets-API@googlegroups.com.
> To unsubscribe from this group, send email to
> Google-Gadgets-API+unsubscribe@googlegroups.com<Google-Gadgets-API%2Bunsubs cribe@googlegroups.com>
> .
> 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 Google-Gadgets-API@googlegroups.com.
To unsubscribe from this group, send email to Google-Gadgets-API+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/Google-Gadgets-API?hl=en.
Hey there, I've got another example of this for you,
My gadget is/was a wrapper of the mailinator mailbox jsp, pass it a
simple 4-argument URL, and get a custom mailbox back. Yesterday, A
user reported that it had stopped working right, and I discovered this
very problem while troubleshooting.
So the hash tag at the end makes the arguments invisible, and to make
it worse, they are all now prefixed with "up_", so even if the hash
goes away, I still won't have arguments.
Is this a deliberate crippling of our simple url-based gadgets?
On Apr 16, 3:00 pm, Edouard Fattal <efat...@gmail.com> wrote:
> Of course:
-- You received this message because you are subscribed to the Google Groups "iGoogle Developer Forum" group.
To post to this group, send email to Google-Gadgets-API@googlegroups.com.
To unsubscribe from this group, send email to Google-Gadgets-API+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/Google-Gadgets-API?hl=en.
I first saw this in server logs on 2010-April-14 at approximately 2 AM
(UTC).
The following two URLs appear in apache approx. 4.5 mins apart,
from the same IP reporting the same useragent string.
The first request behaved normally, whereas the second didn't work
quite so well.
The useragent string for both of these requests was "Mozilla/4.0
(compatible; MSIE 7.0; Windows NT 6.0; GTB0.0; SLCC1; .NET CLR
2.0.50727; Media Center PC 5.0; .NET CLR 3.0.04506; .NET CLR
1.1.4322)".
Any help from google gurus appreciated! Thank you!
Cheers,
Roy
-- You received this message because you are subscribed to the Google Groups "iGoogle Developer Forum" group.
To post to this group, send email to Google-Gadgets-API@googlegroups.com.
To unsubscribe from this group, send email to Google-Gadgets-API+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/Google-Gadgets-API?hl=en.
> I first saw this in server logs on 2010-April-14 at approximately 2 AM
> (UTC).
> The following two URLs appear in apache approx. 4.5 mins apart,
> from the same IP reporting the same useragent string.
> The first request behaved normally, whereas the second didn't work
> quite so well.
> The useragent string for both of these requests was "Mozilla/4.0
> (compatible; MSIE 7.0; Windows NT 6.0; GTB0.0; SLCC1; .NET CLR
> 2.0.50727; Media Center PC 5.0; .NET CLR 3.0.04506; .NET CLR
> 1.1.4322)".
> Any help from google gurus appreciated! Thank you!
> Cheers,
> Roy
> --
> You received this message because you are subscribed to the Google Groups
> "iGoogle Developer Forum" group.
> To post to this group, send email to Google-Gadgets-API@googlegroups.com.
> To unsubscribe from this group, send email to
> Google-Gadgets-API+unsubscribe@googlegroups.com<Google-Gadgets-API%2Bunsubs cribe@googlegroups.com>
> .
> 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 Google-Gadgets-API@googlegroups.com.
To unsubscribe from this group, send email to Google-Gadgets-API+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/Google-Gadgets-API?hl=en.
I have a couple of URL-type gadgets, and approximately 40 to 45 per
cent of requests
to these gadgets deliver no user preferences. So, this is a
significant problem.
Looking at user agents, I don't believe that this problem is exhibited
more
by some useragents. My logs are showing roughly the same proportions
of popular useragent strings in both the "good"- and "bad"-type
requests
to the gadgets.
Hope this helps! (I also hope this problem can be resolved soon!)
Cheers,
Roy
-- You received this message because you are subscribed to the Google Groups "iGoogle Developer Forum" group.
To post to this group, send email to Google-Gadgets-API@googlegroups.com.
To unsubscribe from this group, send email to Google-Gadgets-API+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/Google-Gadgets-API?hl=en.
While debugging this problem yesterday it only appeared to affect IE
6, 7, & 8. Today though it is also doing the same thing on FF &
Chrome. Opera and Safari seem to be unaffected.
WP
On Apr 20, 7:12 am, Roy <mrchut...@gmail.com> wrote:
> I have a couple of URL-type gadgets, and approximately 40 to 45 per
> cent of requests
> to these gadgets deliver no user preferences. So, this is a
> significant problem.
> Looking at user agents, I don't believe that this problem is exhibited
> more
> by some useragents. My logs are showing roughly the same proportions
> of popular useragent strings in both the "good"- and "bad"-type
> requests
> to the gadgets.
> Hope this helps! (I also hope this problem can be resolved soon!)
> Cheers,
> Roy
> --
> You received this message because you are subscribed to the Google Groups "iGoogle Developer Forum" group.
> To post to this group, send email to Google-Gadgets-API@googlegroups.com.
> To unsubscribe from this group, send email to Google-Gadgets-API+unsubscribe@googlegroups.com.
> For more options, visit this group athttp://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 Google-Gadgets-API@googlegroups.com.
To unsubscribe from this group, send email to Google-Gadgets-API+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/Google-Gadgets-API?hl=en.
At least end of March 2 users of my gadget reported this issue, I was
not able to reproduce at that time as my gadget worked without any
issue in my IGoogle page. Today I can see many users are being
affected by this issue.
I think this is to do with Google caching. When IGoogle releases a new
version of their code, not all users get this new version, slowly all
the Google servers are updated with this new code and all users get
this new version.
Please let us know if there is any updates or a due date when this
issue can be resolved.
Thanks,
Mahin
On Apr 20, 7:48 am, WP <solarwi...@gmail.com> wrote:
> While debugging this problem yesterday it only appeared to affect IE
> 6, 7, & 8. Today though it is also doing the same thing on FF &
> Chrome. Opera and Safari seem to be unaffected.
> WP
> On Apr 20, 7:12 am, Roy <mrchut...@gmail.com> wrote:
> > Just a quick follow up to my last post.
> > I have a couple of URL-type gadgets, and approximately 40 to 45 per
> > cent of requests
> > to these gadgets deliver no user preferences. So, this is a
> > significant problem.
> > Looking at user agents, I don't believe that this problem is exhibited
> > more
> > by some useragents. My logs are showing roughly the same proportions
> > of popular useragent strings in both the "good"- and "bad"-type
> > requests
> > to the gadgets.
> > Hope this helps! (I also hope this problem can be resolved soon!)
> > Cheers,
> > Roy
> > --
> > You received this message because you are subscribed to the Google Groups "iGoogle Developer Forum" group.
> > To post to this group, send email to Google-Gadgets-API@googlegroups.com.
> > To unsubscribe from this group, send email to Google-Gadgets-API+unsubscribe@googlegroups.com.
> > For more options, visit this group athttp://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 Google-Gadgets-API@googlegroups.com.
> To unsubscribe from this group, send email to Google-Gadgets-API+unsubscribe@googlegroups.com.
> For more options, visit this group athttp://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 Google-Gadgets-API@googlegroups.com.
To unsubscribe from this group, send email to Google-Gadgets-API+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/Google-Gadgets-API?hl=en.
This is effecting all the browsers for me. It seems more to do with
the fact that the hash sign is in the middle of the URL before the
parameters that are set on the gadget. Here is mine:
These are the only query string parameters getting transmitted to my
server:
exp_rpc_js : 1
exp_track_js : 1
st :
c=ig&e=APu7icrPQ09te6aX7I7sBEpHi722NXXeTinJ0sdx5Qov0tBj1aDb62BeuRoGabaKHuVZ /
Xe6Ja4hjGzApMklNdZkAE8t4ziBlvXgnUEuILsggcRjfA3aC8iiseRnW21Xo
%2BkDzhHz3wcr
container : ig
mid : 23
v : 9017cbe3d0d249a5ffa9bfead68f0fe
lang : en
country : US
view : default,default
parent : http://www.google.com libs : DoXS5gxhejE/lib/liberror_tracker.js,mWuUtp2ZV1Y/lib/
librpc.js,tjNv-0-mtdo/lib/libcore.js
is_signedin : 1
synd : ig
That means everything from the "#" sign onward aren't getting
transmitted, because they aren't part of the actual Request URL as
defined by IEEE standard.
> At least end of March 2 users of my gadget reported this issue, I was
> not able to reproduce at that time as my gadget worked without any
> issue in my IGoogle page. Today I can see many users are being
> affected by this issue.
> I think this is to do with Google caching. When IGoogle releases a new
> version of their code, not all users get this new version, slowly all
> the Google servers are updated with this new code and all users get
> this new version.
> Please let us know if there is any updates or a due date when this
> issue can be resolved.
> Thanks,
> Mahin
> On Apr 20, 7:48 am, WP <solarwi...@gmail.com> wrote:
> > While debugging this problem yesterday it only appeared to affect IE
> > 6, 7, & 8. Today though it is also doing the same thing on FF &
> > Chrome. Opera and Safari seem to be unaffected.
> > WP
> > On Apr 20, 7:12 am, Roy <mrchut...@gmail.com> wrote:
> > > Just a quick follow up to my last post.
> > > I have a couple of URL-type gadgets, and approximately 40 to 45 per
> > > cent of requests
> > > to these gadgets deliver no user preferences. So, this is a
> > > significant problem.
> > > Looking at user agents, I don't believe that this problem is exhibited
> > > more
> > > by some useragents. My logs are showing roughly the same proportions
> > > of popular useragent strings in both the "good"- and "bad"-type
> > > requests
> > > to the gadgets.
> > > Hope this helps! (I also hope this problem can be resolved soon!)
> > > Cheers,
> > > Roy
> > > --
> > > You received this message because you are subscribed to the Google Groups "iGoogle Developer Forum" group.
> > > To post to this group, send email to Google-Gadgets-API@googlegroups.com.
> > > To unsubscribe from this group, send email to Google-Gadgets-API+unsubscribe@googlegroups.com.
> > > For more options, visit this group athttp://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 Google-Gadgets-API@googlegroups.com.
> > To unsubscribe from this group, send email to Google-Gadgets-API+unsubscribe@googlegroups.com.
> > For more options, visit this group athttp://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 Google-Gadgets-API@googlegroups.com.
> To unsubscribe from this group, send email to Google-Gadgets-API+unsubscribe@googlegroups.com.
> For more options, visit this group athttp://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 Google-Gadgets-API@googlegroups.com.
To unsubscribe from this group, send email to Google-Gadgets-API+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/Google-Gadgets-API?hl=en.
I found a temporary solution that will get your stuff around this
Google Bug. Add this to your response if the query strings you are
expecting are not found.
<script type="text/javascript">
if (window.location && window.location.hash) {
var hash = window.location.hash;
window.location.search = "?" + hash.substring(1);
}
</script>
This is a dirty hack and a kitten dies everytime it is used. It was
the quickest way around the problem that I could find.
On Apr 20, 1:23 pm, Mahin <screeperz...@gmail.com> wrote:
> At least end of March 2 users of my gadget reported this issue, I was
> not able to reproduce at that time as my gadget worked without any
> issue in my IGoogle page. Today I can see many users are being
> affected by this issue.
> I think this is to do with Google caching. When IGoogle releases a new
> version of their code, not all users get this new version, slowly all
> the Google servers are updated with this new code and all users get
> this new version.
> Please let us know if there is any updates or a due date when this
> issue can be resolved.
> Thanks,
> Mahin
> On Apr 20, 7:48 am, WP <solarwi...@gmail.com> wrote:
> > While debugging this problem yesterday it only appeared to affect IE
> > 6, 7, & 8. Today though it is also doing the same thing on FF &
> > Chrome. Opera and Safari seem to be unaffected.
> > WP
> > On Apr 20, 7:12 am, Roy <mrchut...@gmail.com> wrote:
> > > Just a quick follow up to my last post.
> > > I have a couple of URL-type gadgets, and approximately 40 to 45 per
> > > cent of requests
> > > to these gadgets deliver no user preferences. So, this is a
> > > significant problem.
> > > Looking at user agents, I don't believe that this problem is exhibited
> > > more
> > > by some useragents. My logs are showing roughly the same proportions
> > > of popular useragent strings in both the "good"- and "bad"-type
> > > requests
> > > to the gadgets.
> > > Hope this helps! (I also hope this problem can be resolved soon!)
> > > Cheers,
> > > Roy
> > > --
> > > You received this message because you are subscribed to the Google Groups "iGoogle Developer Forum" group.
> > > To post to this group, send email to Google-Gadgets-API@googlegroups.com.
> > > To unsubscribe from this group, send email to Google-Gadgets-API+unsubscribe@googlegroups.com.
> > > For more options, visit this group athttp://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 Google-Gadgets-API@googlegroups.com.
> > To unsubscribe from this group, send email to Google-Gadgets-API+unsubscribe@googlegroups.com.
> > For more options, visit this group athttp://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 Google-Gadgets-API@googlegroups.com.
> To unsubscribe from this group, send email to Google-Gadgets-API+unsubscribe@googlegroups.com.
> For more options, visit this group athttp://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 Google-Gadgets-API@googlegroups.com.
To unsubscribe from this group, send email to Google-Gadgets-API+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/Google-Gadgets-API?hl=en.
I've discussed this with the rest of the team and there has been a change in
the way we send parameters to gadgets which use Content type="url". In
short, we started sending the user prefs parameters after a # - the URL
fragment identifier. This change caused problems for developers who rely on
using URL parameters in server side code - since the url fragment isn't sent
to the server.
We didn't intend to break any gadgets and I would normally announce changes
like this on the blog and in this forum earlier. We've talked about ways
that affected gadgets can deal with the new location of the parameters for
type=url gadgets and have some suggested fixes.
First, if your gadget can deal with the user prefs completely in Javascript
without another trip to the server then do so. Use the documented apis for
user prefs -
http://wiki.opensocial.org/index.php?title=Gadgets.Prefs_%28v0.8%29 .
Gadgets that are already using these API functions to retrieve user prefs
are not affected by this iGoogle change.
The other, hopefully less common, case is if you use the parameters in
server side code in a way that slightly alters the delivered content. An
example would be setting up location-dependant data with the user location
stored in their preferences. In this case you can have the gadget read the
parameters from the url in Javascript and send an ajax request to your
server for the data you need to render the relevant sections of your gadget.
Of course your gadget should use the documented userprefs apis as above.
A side-effect of the second fix may be that your gadget's initial render can
happen sooner which can improve user-perceived performance (while taking
roughly the same time to load overall).
We realize this unintended consequence may be difficult to deal with
immediately. So we've figured out a way to exempt specific gadgets for up to
two weeks if you need the time. Just give the url of your gadget in this
thread and we'll add you to the list.
I encourage anyone to post specific questions about fixes for your code in
new threads on this forum. This may not be the best place for help with
server-side code generally but in this case you may find other developers in
similar situations.
On Tue, Apr 20, 2010 at 1:16 PM, Nick <nbera...@gmail.com> wrote:
> I found a temporary solution that will get your stuff around this
> Google Bug. Add this to your response if the query strings you are
> expecting are not found.
> <script type="text/javascript">
> if (window.location && window.location.hash) {
> var hash = window.location.hash;
> window.location.search = "?" + hash.substring(1);
> }
> </script>
> This is a dirty hack and a kitten dies everytime it is used. It was
> the quickest way around the problem that I could find.
> > At least end of March 2 users of my gadget reported this issue, I was
> > not able to reproduce at that time as my gadget worked without any
> > issue in my IGoogle page. Today I can see many users are being
> > affected by this issue.
> > I think this is to do with Google caching. When IGoogle releases a new
> > version of their code, not all users get this new version, slowly all
> > the Google servers are updated with this new code and all users get
> > this new version.
> > Please let us know if there is any updates or a due date when this
> > issue can be resolved.
> > Thanks,
> > Mahin
> > On Apr 20, 7:48 am, WP <solarwi...@gmail.com> wrote:
> > > While debugging this problem yesterday it only appeared to affect IE
> > > 6, 7, & 8. Today though it is also doing the same thing on FF &
> > > Chrome. Opera and Safari seem to be unaffected.
> > > WP
> > > On Apr 20, 7:12 am, Roy <mrchut...@gmail.com> wrote:
> > > > Just a quick follow up to my last post.
> > > > I have a couple of URL-type gadgets, and approximately 40 to 45 per
> > > > cent of requests
> > > > to these gadgets deliver no user preferences. So, this is a
> > > > significant problem.
> > > > Looking at user agents, I don't believe that this problem is
> exhibited
> > > > more
> > > > by some useragents. My logs are showing roughly the same proportions
> > > > of popular useragent strings in both the "good"- and "bad"-type
> > > > requests
> > > > to the gadgets.
> > > > Hope this helps! (I also hope this problem can be resolved soon!)
> > > > Cheers,
> > > > Roy
> > > > --
> > > > You received this message because you are subscribed to the Google
> Groups "iGoogle Developer Forum" group.
> > > > To post to this group, send email to
> Google-Gadgets-API@googlegroups.com.
> > > > To unsubscribe from this group, send email to
> Google-Gadgets-API+unsubscribe@googlegroups.com<Google-Gadgets-API%2Bunsubs cribe@googlegroups.com>
> .
> > > > For more options, visit this group athttp://
> 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
> Google-Gadgets-API@googlegroups.com.
> > > To unsubscribe from this group, send email to
> Google-Gadgets-API+unsubscribe@googlegroups.com<Google-Gadgets-API%2Bunsubs cribe@googlegroups.com>
> .
> > > For more options, visit this group athttp://
> 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 Google-Gadgets-API@googlegroups.com
> .
> > To unsubscribe from this group, send email to
> Google-Gadgets-API+unsubscribe@googlegroups.com<Google-Gadgets-API%2Bunsubs cribe@googlegroups.com>
> .
> > For more options, visit this group athttp://
> 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 Google-Gadgets-API@googlegroups.com.
> To unsubscribe from this group, send email to
> Google-Gadgets-API+unsubscribe@googlegroups.com<Google-Gadgets-API%2Bunsubs cribe@googlegroups.com>
> .
> 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 Google-Gadgets-API@googlegroups.com.
To unsubscribe from this group, send email to Google-Gadgets-API+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/Google-Gadgets-API?hl=en.
This is a bit of a disaster. I use parameters in server-side code
since the content of the gadget is customised for each user by data
from a database. I cannot quite believe you made such a fundamental
change and gave nobody ANY notice, and then provide a two week grace
period.
There is no way I will be able to completely re-engineer my gadgets in
two weeks, with no notice. I do not have the luxury of being able to
drop everything because you decide to make changes that breaks things.
Why can you not change this back and give us some reasonable notice to
be able to completly re-engineer gadgets?
Marko
On Apr 21, 3:55 am, Rob Russell <robruss...@google.com> wrote:
> I've discussed this with the rest of the team and there has been a change in
> the way we send parameters to gadgets which use Content type="url". In
> short, we started sending the user prefs parameters after a # - the URL
> fragment identifier. This change caused problems for developers who rely on
> using URL parameters in server side code - since the url fragment isn't sent
> to the server.
> We didn't intend to break any gadgets and I would normally announce changes
> like this on the blog and in this forum earlier. We've talked about ways
> that affected gadgets can deal with the new location of the parameters for
> type=url gadgets and have some suggested fixes.
> First, if your gadget can deal with the user prefs completely in Javascript
> without another trip to the server then do so. Use the documented apis for
> user prefs -http://wiki.opensocial.org/index.php?title=Gadgets.Prefs_%28v0.8%29.
> Gadgets that are already using these API functions to retrieve user prefs
> are not affected by this iGoogle change.
> The other, hopefully less common, case is if you use the parameters in
> server side code in a way that slightly alters the delivered content. An
> example would be setting up location-dependant data with the user location
> stored in their preferences. In this case you can have the gadget read the
> parameters from the url in Javascript and send an ajax request to your
> server for the data you need to render the relevant sections of your gadget.
> Of course your gadget should use the documented userprefs apis as above.
> A side-effect of the second fix may be that your gadget's initial render can
> happen sooner which can improve user-perceived performance (while taking
> roughly the same time to load overall).
> We realize this unintended consequence may be difficult to deal with
> immediately. So we've figured out a way to exempt specific gadgets for up to
> two weeks if you need the time. Just give the url of your gadget in this
> thread and we'll add you to the list.
> I encourage anyone to post specific questions about fixes for your code in
> new threads on this forum. This may not be the best place for help with
> server-side code generally but in this case you may find other developers in
> similar situations.
> Rob Russell
> Google Developer Relations
> On Tue, Apr 20, 2010 at 1:16 PM, Nick <nbera...@gmail.com> wrote:
> > I found a temporary solution that will get your stuff around this
> > Google Bug. Add this to your response if the query strings you are
> > expecting are not found.
> > > At least end of March 2 users of my gadget reported this issue, I was
> > > not able to reproduce at that time as my gadget worked without any
> > > issue in my IGoogle page. Today I can see many users are being
> > > affected by this issue.
> > > I think this is to do with Google caching. When IGoogle releases a new
> > > version of their code, not all users get this new version, slowly all
> > > the Google servers are updated with this new code and all users get
> > > this new version.
> > > Please let us know if there is any updates or a due date when this
> > > issue can be resolved.
> > > > While debugging this problem yesterday it only appeared to affect IE
> > > > 6, 7, & 8. Today though it is also doing the same thing on FF &
> > > > Chrome. Opera and Safari seem to be unaffected.
> > > > WP
> > > > On Apr 20, 7:12 am, Roy <mrchut...@gmail.com> wrote:
> > > > > Just a quick follow up to my last post.
> > > > > I have a couple of URL-type gadgets, and approximately 40 to 45 per
> > > > > cent of requests
> > > > > to these gadgets deliver no user preferences. So, this is a
> > > > > significant problem.
> > > > > Looking at user agents, I don't believe that this problem is
> > exhibited
> > > > > more
> > > > > by some useragents. My logs are showing roughly the same proportions
> > > > > of popular useragent strings in both the "good"- and "bad"-type
> > > > > requests
> > > > > to the gadgets.
> > > > > Hope this helps! (I also hope this problem can be resolved soon!)
> > > > > Cheers,
> > > > > Roy
> > > > > --
> > > > > You received this message because you are subscribed to the Google
> > Groups "iGoogle Developer Forum" group.
> > > > > To post to this group, send email to
> > Google-Gadgets-API@googlegroups.com.
> > > > > To unsubscribe from this group, send email to
> > Google-Gadgets-API+unsubscribe@googlegroups.com<Google-Gadgets-API%2Bunsubs cribe@googlegroups.com>
> > .
> > > > > For more options, visit this group athttp://
> > 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
> > Google-Gadgets-API@googlegroups.com.
> > > > To unsubscribe from this group, send email to
> > Google-Gadgets-API+unsubscribe@googlegroups.com<Google-Gadgets-API%2Bunsubs cribe@googlegroups.com>
> > .
> > > > For more options, visit this group athttp://
> > 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 Google-Gadgets-API@googlegroups.com
> > .
> > > To unsubscribe from this group, send email to
> > Google-Gadgets-API+unsubscribe@googlegroups.com<Google-Gadgets-API%2Bunsubs cribe@googlegroups.com>
> > .
> > > For more options, visit this group athttp://
> > 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 Google-Gadgets-API@googlegroups.com.
> > To unsubscribe from this group, send email to
> > Google-Gadgets-API+unsubscribe@googlegroups.com<Google-Gadgets-API%2Bunsubs cribe@googlegroups.com>
> > .
> > 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 Google-Gadgets-API@googlegroups.com.
> To unsubscribe from this group, send email to Google-Gadgets-API+unsubscribe@googlegroups.com.
> For more options, visit this group athttp://groups.google.com/group/Google-Gadgets-API?hl=en.- Hide quoted text -
> - Show quoted text -
-- You received this message because you are subscribed to the Google Groups "iGoogle Developer Forum" group.
To post to this group, send email to Google-Gadgets-API@googlegroups.com.
To unsubscribe from this group, send email to Google-Gadgets-API+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/Google-Gadgets-API?hl=en.
In my case, because I could not afford waiting for a solution coming from
Google, I immediately moved all my gadgets to JS/Ajax loading instead of
server-side handling.
I am still surprised by this important change without any notice. How can
the team decide such changes without imagining the consequences for the
gadgets?
All I need now is consistency from the API. Are we sure that this change is
definite?
How will you now distinguish the difference between content and URL gadgets?
They are now very similar because they will both load content that depends
on user prefereces through Ajax , except that content gadgets are cached by
Google servers and that content gadgets have to deal with cross-domain
concerns.
-- You received this message because you are subscribed to the Google Groups "iGoogle Developer Forum" group.
To post to this group, send email to Google-Gadgets-API@googlegroups.com.
To unsubscribe from this group, send email to Google-Gadgets-API+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/Google-Gadgets-API?hl=en.
Hi Edouard,
The change is definite, it doesn't affect the API. The legacy _args() API
and the current gadgets.Prefs() API still work as they always have. It makes
sense that server side code would look at the parameters since there isn't
an API for server side code. As I said earlier, we'd normally announce this
sort of change earlier.
Specific gadgets which are identified by the urls authors give here will be
handled separately so that they continue to receive the older user prefs url
convention until May 4.
Your response to change your gadgets to use JS and Ajax loading sounds like
a good plan. I think (but haven't built code to try this yet) that it should
give a better user experience. The reasoning being that your loader gadget
can be small and cacheable. This way it's served quickly and renders
quickly. The delay while loading content from your server via Ajax shouldn't
be long but it doesn't delay loading the users page.
You may also want to double check any analytics code and stats software
you're using to ensure that any changes to urls and parameters are
reflected.
On Wed, Apr 21, 2010 at 1:00 AM, Edouard Fattal <efat...@gmail.com> wrote:
> Hi Rob,
> In my case, because I could not afford waiting for a solution coming from
> Google, I immediately moved all my gadgets to JS/Ajax loading instead of
> server-side handling.
> I am still surprised by this important change without any notice. How can
> the team decide such changes without imagining the consequences for the
> gadgets?
> All I need now is consistency from the API. Are we sure that this change is
> definite?
> How will you now distinguish the difference between content and URL
> gadgets? They are now very similar because they will both load content that
> depends on user prefereces through Ajax , except that content gadgets are
> cached by Google servers and that content gadgets have to deal with
> cross-domain concerns.
> --
> You received this message because you are subscribed to the Google Groups
> "iGoogle Developer Forum" group.
> To post to this group, send email to Google-Gadgets-API@googlegroups.com.
> To unsubscribe from this group, send email to
> Google-Gadgets-API+unsubscribe@googlegroups.com<Google-Gadgets-API%2Bunsubs cribe@googlegroups.com>
> .
> 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 Google-Gadgets-API@googlegroups.com.
To unsubscribe from this group, send email to Google-Gadgets-API+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/Google-Gadgets-API?hl=en.
Do you guys seriously just break API's for the sake of breaking them.
I was forced to move from the type="html" to type="url", about a year
ago because your proxy server was constantly causing issues when
pulling feeds.
Why is it that you assume every solution can be accomplished with the
Google model of everything JavaScript. Now to implement a large
JavaScript library to handle AJAX requests. The size of this
JavaScript library is going to take a lot longer to download than my
current server-side gadget does. And not to mention I still have to
hit my backend server to get the same information again. So congrats
these "improvements" are actually slowing my gadget down.
That is why I am going to stick with this method for now.
<script type="text/javascript">
if (window.location && window.location.hash) {
var hash = window.location.hash;
window.location.search = "?" + hash.substring(1);
}
</script>
Nick
On Apr 21, 4:26 am, Rob Russell <robruss...@google.com> wrote:
> Hi Edouard,
> The change is definite, it doesn't affect the API. The legacy _args() API
> and the current gadgets.Prefs() API still work as they always have. It makes
> sense that server side code would look at the parameters since there isn't
> an API for server side code. As I said earlier, we'd normally announce this
> sort of change earlier.
> Specific gadgets which are identified by the urls authors give here will be
> handled separately so that they continue to receive the older user prefs url
> convention until May 4.
> Your response to change your gadgets to use JS and Ajax loading sounds like
> a good plan. I think (but haven't built code to try this yet) that it should
> give a better user experience. The reasoning being that your loader gadget
> can be small and cacheable. This way it's served quickly and renders
> quickly. The delay while loading content from your server via Ajax shouldn't
> be long but it doesn't delay loading the users page.
> You may also want to double check any analytics code and stats software
> you're using to ensure that any changes to urls and parameters are
> reflected.
> Regards,
> Rob Russell
> Google Developer Relations
> On Wed, Apr 21, 2010 at 1:00 AM, Edouard Fattal <efat...@gmail.com> wrote:
> > Hi Rob,
> > In my case, because I could not afford waiting for a solution coming from
> > Google, I immediately moved all my gadgets to JS/Ajax loading instead of
> > server-side handling.
> > I am still surprised by this important change without any notice. How can
> > the team decide such changes without imagining the consequences for the
> > gadgets?
> > All I need now is consistency from the API. Are we sure that this change is
> > definite?
> > How will you now distinguish the difference between content and URL
> > gadgets? They are now very similar because they will both load content that
> > depends on user prefereces through Ajax , except that content gadgets are
> > cached by Google servers and that content gadgets have to deal with
> > cross-domain concerns.
> > --
> > You received this message because you are subscribed to the Google Groups
> > "iGoogle Developer Forum" group.
> > To post to this group, send email to Google-Gadgets-API@googlegroups.com.
> > To unsubscribe from this group, send email to
> > Google-Gadgets-API+unsubscribe@googlegroups.com<Google-Gadgets-API%2Bunsubs cribe@googlegroups.com>
> > .
> > 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 Google-Gadgets-API@googlegroups.com.
> To unsubscribe from this group, send email to Google-Gadgets-API+unsubscribe@googlegroups.com.
> For more options, visit this group athttp://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 Google-Gadgets-API@googlegroups.com.
To unsubscribe from this group, send email to Google-Gadgets-API+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/Google-Gadgets-API?hl=en.
> I've discussed this with the rest of the team and there has been a change in
> the way we send parameters to gadgets which use Content type="url". In
> short, we started sending the user prefs parameters after a # - the URL
> fragment identifier. This change caused problems for developers who rely on
> using URL parameters in server side code - since the url fragment isn't sent
> to the server.
> We didn't intend to break any gadgets and I would normally announce changes
> like this on the blog and in this forum earlier. We've talked about ways
> that affected gadgets can deal with the new location of the parameters for
> type=url gadgets and have some suggested fixes.
> First, if your gadget can deal with the user prefs completely in Javascript
> without another trip to the server then do so. Use the documented apis for
> user prefs -http://wiki.opensocial.org/index.php?title=Gadgets.Prefs_%28v0.8%29.
> Gadgets that are already using these API functions to retrieve user prefs
> are not affected by this iGoogle change.
> The other, hopefully less common, case is if you use the parameters in
> server side code in a way that slightly alters the delivered content. An
> example would be setting up location-dependant data with the user location
> stored in their preferences. In this case you can have the gadget read the
> parameters from the url in Javascript and send an ajax request to your
> server for the data you need to render the relevant sections of your gadget.
> Of course your gadget should use the documented userprefs apis as above.
> A side-effect of the second fix may be that your gadget's initial render can
> happen sooner which can improve user-perceived performance (while taking
> roughly the same time to load overall).
> We realize this unintended consequence may be difficult to deal with
> immediately. So we've figured out a way to exempt specific gadgets for up to
> two weeks if you need the time. Just give the url of your gadget in this
> thread and we'll add you to the list.
> I encourage anyone to post specific questions about fixes for your code in
> new threads on this forum. This may not be the best place for help with
> server-side code generally but in this case you may find other developers in
> similar situations.
> Rob Russell
> Google Developer Relations
> On Tue, Apr 20, 2010 at 1:16 PM, Nick <nbera...@gmail.com> wrote:
> > I found a temporary solution that will get your stuff around this
> > Google Bug. Add this to your response if the query strings you are
> > expecting are not found.
> > > At least end of March 2 users of my gadget reported this issue, I was
> > > not able to reproduce at that time as my gadget worked without any
> > > issue in my IGoogle page. Today I can see many users are being
> > > affected by this issue.
> > > I think this is to do with Google caching. When IGoogle releases a new
> > > version of their code, not all users get this new version, slowly all
> > > the Google servers are updated with this new code and all users get
> > > this new version.
> > > Please let us know if there is any updates or a due date when this
> > > issue can be resolved.
> > > > While debugging this problem yesterday it only appeared to affect IE
> > > > 6, 7, & 8. Today though it is also doing the same thing on FF &
> > > > Chrome. Opera and Safari seem to be unaffected.
> > > > WP
> > > > On Apr 20, 7:12 am, Roy <mrchut...@gmail.com> wrote:
> > > > > Just a quick follow up to my last post.
> > > > > I have a couple of URL-type gadgets, and approximately 40 to 45 per
> > > > > cent of requests
> > > > > to these gadgets deliver no user preferences. So, this is a
> > > > > significant problem.
> > > > > Looking at user agents, I don't believe that this problem is
> > exhibited
> > > > > more
> > > > > by some useragents. My logs are showing roughly the same proportions
> > > > > of popular useragent strings in both the "good"- and "bad"-type
> > > > > requests
> > > > > to the gadgets.
> > > > > Hope this helps! (I also hope this problem can be resolved soon!)
> > > > > Cheers,
> > > > > Roy
> > > > > --
> > > > > You received this message because you are subscribed to the Google
> > Groups "iGoogle Developer Forum" group.
> > > > > To post to this group, send email to
> > Google-Gadgets-API@googlegroups.com.
> > > > > To unsubscribe from this group, send email to
> > Google-Gadgets-API+unsubscribe@googlegroups.com<Google-Gadgets-API%2Bunsubs cribe@googlegroups.com>
> > .
> > > > > For more options, visit this group athttp://
> > 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
> > Google-Gadgets-API@googlegroups.com.
> > > > To unsubscribe from this group, send email to
> > Google-Gadgets-API+unsubscribe@googlegroups.com<Google-Gadgets-API%2Bunsubs cribe@googlegroups.com>
> > .
> > > > For more options, visit this group athttp://
> > 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 Google-Gadgets-API@googlegroups.com
> > .
> > > To unsubscribe from this group, send email to
> > Google-Gadgets-API+unsubscribe@googlegroups.com<Google-Gadgets-API%2Bunsubs cribe@googlegroups.com>
> > .
> > > For more options, visit this group athttp://
> > 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 Google-Gadgets-API@googlegroups.com.
> > To unsubscribe from this group, send email to
> > Google-Gadgets-API+unsubscribe@googlegroups.com<Google-Gadgets-API%2Bunsubs cribe@googlegroups.com>
> > .
> > 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 Google-Gadgets-API@googlegroups.com.
> To unsubscribe from this group, send email to Google-Gadgets-API+unsubscribe@googlegroups.com.
> For more options, visit this group athttp://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 Google-Gadgets-API@googlegroups.com.
To unsubscribe from this group, send email to Google-Gadgets-API+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/Google-Gadgets-API?hl=en.
Id ask for an exemption too, b ut since i cannot change the url parameters
that my gadget expects, i would only be prolonging the inevitable.
Why you guys had to take something that "just worked" and mangle it a) with
no warning and b) in a completely broken fashion is beyond me. So much for
"do no evil."
Seriously, if someone on your team honestly thought that this change would
be idempotent, they should be fired on the spot for incompetence.
I am disappointed by this, This is something not even microsoft would do, or
has ever done, to their developer community.
Instead of delaying the inevitable death of my gadget, i would rather that
you spend that time removing my email from my 'about gadget' page, because i
wont be this polite when my users email me and ask why their favorite gadget
is irrevocably broken.
Regards,
-G
On 2010-04-21 7:55 AM, "bill123" <bi...@ssec.wisc.edu> wrote:
Rob,
Please add the SSEC PAW Weather gadget to your list of gadgets to
give a two week exemption. The URL is
On Apr 20, 9:55 pm, Rob Russell <robruss...@google.com> wrote:
> I've discussed this with the rest ...
> On Tue, Apr 20, 2010 at 1:16 PM, Nick <nbera...@gmail.com> wrote:
> > I found a temporary solution...
> > Google-Gadgets-API+unsubscribe@googlegroups.com<Google-Gadgets-API%2Bunsubs cribe@googlegroups.com>
> > .
> > > For more options, visit this group athttp://
> > groups.google.com/group/Google-Gadgets-...
> > Google-Gadgets-API+unsubscribe@googlegroups.com<Google-Gadgets-API%2Bunsubs cribe@googlegroups.com>
-- You received this message because you are subscribed to the Google Groups "iGoogle Developer Forum" group.
To post to this group, send email to Google-Gadgets-API@googlegroups.com.
To unsubscribe from this group, send email to Google-Gadgets-API+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/Google-Gadgets-API?hl=en.
Sorry for double posting, but I just had a chance to read the recent blog
post about this, and had to add a thought;
I know php, but not javascript. If this hashtag is a permanent misfeature,
then I and anyone else like me will be unable to write gadgets anymore,
where once we could.
I was excited when Go was announced, but now I want nothing of it, for fear
that one day, without warning, 3% of the applications will simply fail to
compile.
Good day.
-G
On 2010-04-21 8:27 AM, "Gavin McDonald" <m...@gavitron.com> wrote:
Id ask for an exemption too, b ut since i cannot change the url parameters
that my gadget expects, i would only be prolonging the inevitable.
Why you guys had to take something that "just worked" and mangle it a) with
no warning and b) in a completely broken fashion is beyond me. So much for
"do no evil."
Seriously, if someone on your team honestly thought that this change would
be idempotent, they should be fired on the spot for incompetence.
I am disappointed by this, This is something not even microsoft would do, or
has ever done, to their developer community.
Instead of delaying the inevitable death of my gadget, i would rather that
you spend that time removing my email from my 'about gadget' page, because i
wont be this polite when my users email me and ask why their favorite gadget
is irrevocably broken.
Regards,
-G
> On 2010-04-21 7:55 AM, "bill123" <bi...@ssec.wisc.edu> wrote:
> Rob,
> Please add the SSEC P...
> On Apr 20, 9:55 pm, Rob Russell <robruss...@google.com> wrote:
> I've discussed this with the rest ...
> > On Tue, Apr 20, 2010 at 1:16 PM, Nick <nbera...@gmail.com> wrote:
> > I found a temporary solution...
-- You received this message because you are subscribed to the Google Groups "iGoogle Developer Forum" group.
To post to this group, send email to Google-Gadgets-API@googlegroups.com.
To unsubscribe from this group, send email to Google-Gadgets-API+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/Google-Gadgets-API?hl=en.
On Wed, Apr 21, 2010 at 8:40 AM, Gavin McDonald <m...@gavitron.com> wrote:
> Sorry for double posting, but I just had a chance to read the recent blog
> post about this, and had to add a thought;
> I know php, but not javascript. If this hashtag is a permanent misfeature,
> then I and anyone else like me will be unable to write gadgets anymore,
> where once we could.
> I was excited when Go was announced, but now I want nothing of it, for fear
> that one day, without warning, 3% of the applications will simply fail to
> compile.
> Good day.
> -G
> On 2010-04-21 8:27 AM, "Gavin McDonald" <m...@gavitron.com> wrote:
> Id ask for an exemption too, b ut since i cannot change the url parameters
> that my gadget expects, i would only be prolonging the inevitable.
> Why you guys had to take something that "just worked" and mangle it a) with
> no warning and b) in a completely broken fashion is beyond me. So much for
> "do no evil."
> Seriously, if someone on your team honestly thought that this change would
> be idempotent, they should be fired on the spot for incompetence.
> I am disappointed by this, This is something not even microsoft would do,
> or has ever done, to their developer community.
> Instead of delaying the inevitable death of my gadget, i would rather that
> you spend that time removing my email from my 'about gadget' page, because i
> wont be this polite when my users email me and ask why their favorite gadget
> is irrevocably broken.
> Regards,
> -G
> > On 2010-04-21 7:55 AM, "bill123" <bi...@ssec.wisc.edu> wrote:
> > Rob,
> > Please add the SSEC P...
> > On Apr 20, 9:55 pm, Rob Russell <robruss...@google.com> wrote:
> > I've discussed this with the rest ...
> > > On Tue, Apr 20, 2010 at 1:16 PM, Nick <nbera...@gmail.com> wrote:
> > > I found a temporary solution...
> --
> You received this message because you are subscribed to the Google Groups
> "iGoogle Developer Forum" group.
> To post to this group, send email to Google-Gadgets-API@googlegroups.com.
> To unsubscribe from this group, send email to
> Google-Gadgets-API+unsubscribe@googlegroups.com<Google-Gadgets-API%2Bunsubs cribe@googlegroups.com>
> .
> 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 Google-Gadgets-API@googlegroups.com.
To unsubscribe from this group, send email to Google-Gadgets-API+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/Google-Gadgets-API?hl=en.
Our gadgets are broken right now as well. Could you possibly add these
to your list for extension as it will take a little time for us to
find a working solution for them.
> I update the list again if there are more developers who want this change
> for their gadget.
> Thanks again to everyone for your understanding in this.
> Rob Russell
> Google Developer Relations
> On Wed, Apr 21, 2010 at 8:40 AM, Gavin McDonald <m...@gavitron.com> wrote:
> > Sorry for double posting, but I just had a chance to read the recent blog
> > post about this, and had to add a thought;
> > I know php, but not javascript. If this hashtag is a permanent misfeature,
> > then I and anyone else like me will be unable to write gadgets anymore,
> > where once we could.
> > I was excited when Go was announced, but now I want nothing of it, for fear
> > that one day, without warning, 3% of the applications will simply fail to
> > compile.
> > Good day.
> > -G
> > On 2010-04-21 8:27 AM, "Gavin McDonald" <m...@gavitron.com> wrote:
> > Id ask for an exemption too, b ut since i cannot change the url parameters
> > that my gadget expects, i would only be prolonging the inevitable.
> > Why you guys had to take something that "just worked" and mangle it a) with
> > no warning and b) in a completely broken fashion is beyond me. So much for
> > "do no evil."
> > Seriously, if someone on your team honestly thought that this change would
> > be idempotent, they should be fired on the spot for incompetence.
> > I am disappointed by this, This is something not even microsoft would do,
> > or has ever done, to their developer community.
> > Instead of delaying the inevitable death of my gadget, i would rather that
> > you spend that time removing my email from my 'about gadget' page, because i
> > wont be this polite when my users email me and ask why their favorite gadget
> > is irrevocably broken.
> > Regards,
> > -G
> > > On 2010-04-21 7:55 AM, "bill123" <bi...@ssec.wisc.edu> wrote:
> > > Rob,
> > > Please add the SSEC P...
> > > On Apr 20, 9:55 pm, Rob Russell <robruss...@google.com> wrote:
> > > I've discussed this with the rest ...
> > > > On Tue, Apr 20, 2010 at 1:16 PM, Nick <nbera...@gmail.com> wrote:
> > > > I found a temporary solution...
> > --
> > You received this message because you are subscribed to the Google Groups
> > "iGoogle Developer Forum" group.
> > To post to this group, send email to Google-Gadgets-API@googlegroups.com.
> > To unsubscribe from this group, send email to
> > Google-Gadgets-API+unsubscribe@googlegroups.com<Google-Gadgets-API%2Bunsubs cribe@googlegroups.com>
> > .
> > 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 Google-Gadgets-API@googlegroups.com.
> To unsubscribe from this group, send email to Google-Gadgets-API+unsubscribe@googlegroups.com.
> For more options, visit this group athttp://groups.google.com/group/Google-Gadgets-API?hl=en.- Hide quoted text -
> - Show quoted text -
-- You received this message because you are subscribed to the Google Groups "iGoogle Developer Forum" group.
To post to this group, send email to Google-Gadgets-API@googlegroups.com.
To unsubscribe from this group, send email to Google-Gadgets-API+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/Google-Gadgets-API?hl=en.
On Wed, Apr 21, 2010 at 3:17 PM, Trent <trent.bur...@gmail.com> wrote:
> Hi Rob
> Our gadgets are broken right now as well. Could you possibly add these
> to your list for extension as it will take a little time for us to
> find a working solution for them.
> > I update the list again if there are more developers who want this change
> > for their gadget.
> > Thanks again to everyone for your understanding in this.
> > Rob Russell
> > Google Developer Relations
> > On Wed, Apr 21, 2010 at 8:40 AM, Gavin McDonald <m...@gavitron.com>
> wrote:
> > > Sorry for double posting, but I just had a chance to read the recent
> blog
> > > post about this, and had to add a thought;
> > > I know php, but not javascript. If this hashtag is a permanent
> misfeature,
> > > then I and anyone else like me will be unable to write gadgets anymore,
> > > where once we could.
> > > I was excited when Go was announced, but now I want nothing of it, for
> fear
> > > that one day, without warning, 3% of the applications will simply fail
> to
> > > compile.
> > > Id ask for an exemption too, b ut since i cannot change the url
> parameters
> > > that my gadget expects, i would only be prolonging the inevitable.
> > > Why you guys had to take something that "just worked" and mangle it a)
> with
> > > no warning and b) in a completely broken fashion is beyond me. So much
> for
> > > "do no evil."
> > > Seriously, if someone on your team honestly thought that this change
> would
> > > be idempotent, they should be fired on the spot for incompetence.
> > > I am disappointed by this, This is something not even microsoft would
> do,
> > > or has ever done, to their developer community.
> > > Instead of delaying the inevitable death of my gadget, i would rather
> that
> > > you spend that time removing my email from my 'about gadget' page,
> because i
> > > wont be this polite when my users email me and ask why their favorite
> gadget
> > > is irrevocably broken.
> > > --
> > > You received this message because you are subscribed to the Google
> Groups
> > > "iGoogle Developer Forum" group.
> > > To post to this group, send email to
> Google-Gadgets-API@googlegroups.com.
> > > To unsubscribe from this group, send email to
> > > Google-Gadgets-API+unsubscribe@googlegroups.com<Google-Gadgets-API%2Bunsubs cribe@googlegroups.com>
> <Google-Gadgets-API%2Bunsubscribe@googlegroups.com>
> > > .
> > > 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 Google-Gadgets-API@googlegroups.com
> .
> > To unsubscribe from this group, send email to
> Google-Gadgets-API+unsubscribe@googlegroups.com<Google-Gadgets-API%2Bunsubs cribe@googlegroups.com>
> .
> > For more options, visit this group athttp://
> groups.google.com/group/Google-Gadgets-API?hl=en.- Hide quoted text -
> > - Show quoted text -
> --
> You received this message because you are subscribed to the Google Groups
> "iGoogle Developer Forum" group.
> To post to this group, send email to Google-Gadgets-API@googlegroups.com.
> To unsubscribe from this group, send email to
> Google-Gadgets-API+unsubscribe@googlegroups.com<Google-Gadgets-API%2Bunsubs cribe@googlegroups.com>
> .
> 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 Google-Gadgets-API@googlegroups.com.
To unsubscribe from this group, send email to Google-Gadgets-API+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/Google-Gadgets-API?hl=en.
> Hi Trent,
> I've already committed the first list of urls and those gadgets appear to be
> getting the old style of request parameters.
> I've added yours to the next list. The change probably won't show up before
> tomorrow.
> Thanks,
> Rob Russell
> Google Developer Relations
> On Wed, Apr 21, 2010 at 3:17 PM, Trent <trent.bur...@gmail.com> wrote:
> > Hi Rob
> > Our gadgets are broken right now as well. Could you possibly add these
> > to your list for extension as it will take a little time for us to
> > find a working solution for them.
> > > I update the list again if there are more developers who want this change
> > > for their gadget.
> > > Thanks again to everyone for your understanding in this.
> > > Rob Russell
> > > Google Developer Relations
> > > On Wed, Apr 21, 2010 at 8:40 AM, Gavin McDonald <m...@gavitron.com>
> > wrote:
> > > > Sorry for double posting, but I just had a chance to read the recent
> > blog
> > > > post about this, and had to add a thought;
> > > > I know php, but not javascript. If this hashtag is a permanent
> > misfeature,
> > > > then I and anyone else like me will be unable to write gadgets anymore,
> > > > where once we could.
> > > > I was excited when Go was announced, but now I want nothing of it, for
> > fear
> > > > that one day, without warning, 3% of the applications will simply fail
> > to
> > > > compile.
> > > > Id ask for an exemption too, b ut since i cannot change the url
> > parameters
> > > > that my gadget expects, i would only be prolonging the inevitable.
> > > > Why you guys had to take something that "just worked" and mangle it a)
> > with
> > > > no warning and b) in a completely broken fashion is beyond me. So much
> > for
> > > > "do no evil."
> > > > Seriously, if someone on your team honestly thought that this change
> > would
> > > > be idempotent, they should be fired on the spot for incompetence.
> > > > I am disappointed by this, This is something not even microsoft would
> > do,
> > > > or has ever done, to their developer community.
> > > > Instead of delaying the inevitable death of my gadget, i would rather
> > that
> > > > you spend that time removing my email from my 'about gadget' page,
> > because i
> > > > wont be this polite when my users email me and ask why their favorite
> > gadget
> > > > is irrevocably broken.
> > > > --
> > > > You received this message because you are subscribed to the Google
> > Groups
> > > > "iGoogle Developer Forum" group.
> > > > To post to this group, send email to
> > Google-Gadgets-API@googlegroups.com.
> > > > To unsubscribe from this group, send email to
> > > > Google-Gadgets-API+unsubscribe@googlegroups.com<Google-Gadgets-API%2Bunsubs cribe@googlegroups.com>
> > <Google-Gadgets-API%2Bunsubscribe@googlegroups.com>
> > > > .
> > > > 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 Google-Gadgets-API@googlegroups.com
> > .
> > > To unsubscribe from this group, send email to
> > Google-Gadgets-API+unsubscribe@googlegroups.com<Google-Gadgets-API%2Bunsubs cribe@googlegroups.com>
> > .
> > > For more options, visit this group athttp://
> > groups.google.com/group/Google-Gadgets-API?hl=en.- Hide quoted text -
> > > - Show quoted text -
> > --
> > You received this message because you are subscribed to the Google Groups
> > "iGoogle Developer Forum" group.
> > To post to this group, send email to Google-Gadgets-API@googlegroups.com.
> > To unsubscribe from this group, send email to
> > Google-Gadgets-API+unsubscribe@googlegroups.com<Google-Gadgets-API%2Bunsubs cribe@googlegroups.com>
> > .
> > 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 Google-Gadgets-API@googlegroups.com.
> To unsubscribe from this group, send email to Google-Gadgets-API+unsubscribe@googlegroups.com.
> For more options, visit this group athttp://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 Google-Gadgets-API@googlegroups.com.
To unsubscribe from this group, send email to Google-Gadgets-API+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/Google-Gadgets-API?hl=en.
> On Apr 21, 3:38 pm, Rob Russell <robruss...@google.com> wrote:
> > Hi Trent,
> > I've already committed the first list of urls and those gadgets appear to
> be
> > getting the old style of request parameters.
> > I've added yours to the next list. The change probably won't show up
> before
> > tomorrow.
> > Thanks,
> > Rob Russell
> > Google Developer Relations
> > On Wed, Apr 21, 2010 at 3:17 PM, Trent <trent.bur...@gmail.com> wrote:
> > > Hi Rob
> > > Our gadgets are broken right now as well. Could you possibly add these
> > > to your list for extension as it will take a little time for us to
> > > find a working solution for them.
> > > > I update the list again if there are more developers who want this
> change
> > > > for their gadget.
> > > > Thanks again to everyone for your understanding in this.
> > > > Rob Russell
> > > > Google Developer Relations
> > > > On Wed, Apr 21, 2010 at 8:40 AM, Gavin McDonald <m...@gavitron.com>
> > > wrote:
> > > > > Sorry for double posting, but I just had a chance to read the
> recent
> > > blog
> > > > > post about this, and had to add a thought;
> > > > > I know php, but not javascript. If this hashtag is a permanent
> > > misfeature,
> > > > > then I and anyone else like me will be unable to write gadgets
> anymore,
> > > > > where once we could.
> > > > > I was excited when Go was announced, but now I want nothing of it,
> for
> > > fear
> > > > > that one day, without warning, 3% of the applications will simply
> fail
> > > to
> > > > > compile.
> > > > > Id ask for an exemption too, b ut since i cannot change the url
> > > parameters
> > > > > that my gadget expects, i would only be prolonging the inevitable.
> > > > > Why you guys had to take something that "just worked" and mangle it
> a)
> > > with
> > > > > no warning and b) in a completely broken fashion is beyond me. So
> much
> > > for
> > > > > "do no evil."
> > > > > Seriously, if someone on your team honestly thought that this
> change
> > > would
> > > > > be idempotent, they should be fired on the spot for incompetence.
> > > > > I am disappointed by this, This is something not even microsoft
> would
> > > do,
> > > > > or has ever done, to their developer community.
> > > > > Instead of delaying the inevitable death of my gadget, i would
> rather
> > > that
> > > > > you spend that time removing my email from my 'about gadget' page,
> > > because i
> > > > > wont be this polite when my users email me and ask why their
> favorite
> > > gadget
> > > > > is irrevocably broken.
> > > > > --
> > > > > You received this message because you are subscribed to the Google
> > > Groups
> > > > > "iGoogle Developer Forum" group.
> > > > > To post to this group, send email to
> > > Google-Gadgets-API@googlegroups.com.
> > > > > To unsubscribe from this group, send email to
> > > > > Google-Gadgets-API+unsubscribe@googlegroups.com<Google-Gadgets-API%2Bunsubs cribe@googlegroups.com><Google-Gadgets-API%2Bunsubs
> cribe@googlegroups.com>
> > > <Google-Gadgets-API%2Bunsubscribe@googlegroups.com>
> > > > > .
> > > > > 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
> Google-Gadgets-API@googlegroups.com
> > > .
> > > > To unsubscribe from this group, send email to
> > > Google-Gadgets-API+unsubscribe@googlegroups.com<Google-Gadgets-API%2Bunsubs cribe@googlegroups.com><Google-Gadgets-API%2Bunsubs
> cribe@googlegroups.com>
> > > .
> > > > For more options, visit this group athttp://
> > > groups.google.com/group/Google-Gadgets-API?hl=en.- Hide quoted text -
> > > > - Show quoted text -
> > > --
> > > You received this message because you are subscribed to the Google
> Groups
> > > "iGoogle Developer Forum" group.
> > > To post to this group, send email to
> Google-Gadgets-API@googlegroups.com.
> > > To unsubscribe from this group, send email to
> > > Google-Gadgets-API+unsubscribe@googlegroups.com<Google-Gadgets-API%2Bunsubs cribe@googlegroups.com><Google-Gadgets-API%2Bunsubs
> cribe@googlegroups.com>
> > > .
> > > 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 Google-Gadgets-API@googlegroups.com
> .
> > To unsubscribe from this group, send email to
> Google-Gadgets-API+unsubscribe@googlegroups.com<Google-Gadgets-API%2Bunsubs cribe@googlegroups.com>
> .
> > For more options, visit this group athttp://
> 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 Google-Gadgets-API@googlegroups.com.
> To unsubscribe from this group, send email to
> Google-Gadgets-API+unsubscribe@googlegroups.com<Google-Gadgets-API%2Bunsubs cribe@googlegroups.com>
> .
> 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 Google-Gadgets-API@googlegroups.com.
To unsubscribe from this group, send email to Google-Gadgets-API+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/Google-Gadgets-API?hl=en.
