Hi, I've been struggling for the past week or so with "Invalid domain" errors when using OAuth-enabled gadgets (see discussion here: http://groups.google.com/group/Google-Gadgets-API/browse_thread/thread/dc9ea7c8ec9453aa?hl=en). I have managed to reproduce this error from the example code at http://code.google.com/apis/gadgets/docs/oauth.html by removing the <Require feature="locked-domain" /> in the <ModulePrefs> element at the top.
You can see an example of this by adding these two gadgets: http://start-test.warwick.ac.uk/portal/gadgets/local/example/google-oauth.xml http://start-test.warwick.ac.uk/portal/gadgets/local/example/google-oauth-nolocked.xml It would appear that this feature is now explicitly required when using OAuth elements. If my understanding is correct, Shindig (which I believe iGoogle runs on?) has a shindig.locked-domain.lock-security- tokens property which will IMPLICITLY enable this feature whenever another feature that requires signed security tokens (such as the OAuth tag) is used. As far as I'm aware, there has been no announcement that this is now the case and this has certainly broken a lot of existing gadgets. During my tests, I also found that adding an XML namespace to the <Module /> element also caused these problems to show up, even if the locked-domain feature is enabled - this would suggest that somewhere in your code your XML parsing is a bit too strict. Hopes this helps some people who are getting the (infuriating!) Invalid Domain error. Mat -- 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.
