OK. Will open a bug. But there seems to be a further issue. If you
make a spreadsheet editable by everyone and then use a browser whose
cache has been cleared, cookies deleted etc. to access the URL - it
prompts for a login. Random behavior it seems. Cases I saw:

Start: Spreadsheet made editable by all.
Case 1: From an iphone browser - always asks for login - Broken
Case 2: IE, Chrome, Firefox with cache cleared - Broken
Case 3: IE, Chrome, Firefox - If the browser has never authenticated
using a google id but has browsed several google sites e.g. google
news etc. ie. has some google cookies - Works 90%.
Case 4: Safari on Mac - not asked for login yet. Seems to work but it
has a google search toolbar. Maybe that's getting some google cookies
asynchronously.

Is there some rationale behind all this and I'm missing something or
is this a bug?


On Mar 25, 2:18 pm, Eric Bidelman <[email protected]> wrote:
> Hi,
> I was able to POST or PUT an 'everyone' acl entry for docs:
>
> <gAcl:role value="reader"/> <gAcl:scope type="user" value="everyone"/>
>
> The same doesn't work for spreadsheets. The entry gets
> created, but the role value is 'none':
> <gAcl:role value="none"/> <gAcl:scope type="user" value="everyone"/>
>
> Please open a 
> bug:http://code.google.com/p/gdata-issues/issues/entry?template=Documents...)
>
> Eric
>
> On Wed, Mar 25, 2009 at 8:58 AM, AN <[email protected]> wrote:
>
> > Is it possible to make a spreadsheet editable by everyone using an API
> > call?
>
> > I tried giving full access to the 'everyone' user by setting the ACL
> > but that didn't work. Any help appreciated.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Docs Data APIs" 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-Docs-Data-APIs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to