Via URL such as http://server/directory/dbname.nsf/viewname/?ReadViewEntriesI am able to view XML as expected. (IE5.5)
However, as soon as one or more of the documents in the view contains a readers field, the XML is still viewable through browser, but the file type according to IE5 changes from “XML Document” to “Not Available”, and the XML page will not save to disk.
Also the file size / created / modified are “Not Available”.
Please help, I’ve been looking at this for several days !!!
Subject: XML load of document with readers fields failing
Is this a authenticated session and is the username authenticated in the readers field? If the answer to either of those is no then that could be your problem. Readers fields control access at the document level. In notes they don’t appear at all if you do not have access, not even in document count in database properties. It is troubling to hear that you can access data, though you can’t save. Is this what is happening?
Subject: RE: XML load of document with readers fields failing
Yes, the session is authenticated both by SSL certificate, and via usual Notes userid/password ACL authentication. The value of the readers field should and does exclude the user from access as expected.
So for example with 3 docs in the view, one with a readers fields on , I see two docs… OK
Problem I’m getting is that when I then try to save this page from the IE browser using ‘File’, 'Save as '. It won’t save.
When I then remove the readers field from the one document, I now see 3 docs in the view , and I can save the page.
I think it’s a Notes HTTP server problem, it’s almost as if the HTTP server is not writing the page properly whenever there are documents missing due to readers fields. Having no file size in the file properties on the browser would seem to be the reason why the page won’t save, but the big question is why doesn’t it have a file size ?
Subject: RE: XML load of document with readers fields failing
So readers fields are working as expected. I would investigate the file save problem in an IE forum. It could be Domino causing it, but you need to know that cause before you can know the cure. Once you know what triggers IE to behave this way, then you can work a solution. I have seen this before on pages that hide source code. Can you see the source code of this page?