Ok, I found the answer to my question. On this page "Gadgets for Google Sites" http://code.google.com/apis/sites/gadgets/site_gadgets.html
This paragraph answers it: "Further, in containers like iGoogle where the viewer and editor are the same, gadget authors can extended configuration as part of the standard view. In Sites, the viewer is not always the editor, so the gadget author can't guarantee the viewing user has access to update preferences. Social containers such as Sites cannot allow any user to modify the preferences, only the author." The way to ensure that the viewer IS the author, is to disallow editing of preference in the standard view. The solution is to add some logic to the configuration page, Just as they do on that site_gadgets.html page in the news.xml example. This will work great for my purposes. -- You received this message because you are subscribed to the Google Groups "OpenSocial Application Development" 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/opensocial-api?hl=en.
