LotusScript WebQuerySave agents no longer have access to any CGI variables on the document. For example, I have a Field on the form with the name “Path_Info”. In my WebQuerySave agent, I have the following:
set doc = s.DocumentContext
Print {Path_Info=“} & doc.Path_Info(0) & {”}
In 6.0, this returns the following:
Path_Info=“http://mydomain.com/db.nsf/formname?createdocument”
In 6.0.1 it returns:
Path_Info=“”
– i.e. NOTHING.
This is true of ALL the CGI variables that I have tried, and it doesn’t matter whether they are fields on the form or not.
I do NOT have “Generate HTML for all Fields” checked on the form in either case. If I do check this attribute, the Agent DOES see (only) the variables that I have defined on the form. Unfortunately, doing this breaks my applications for other reasons, so I can’t use it as a workaround.
I REALLY hope that Lotus releases a 6.0.1a soon with a fix for this included. It would really suck for me to stay on 6.0 for another four months until 6.0.2 is released.
Subject: Serious 6.0.1 Web Server Regression Bug
It sounds like it’s working correctly to me. If you’ve got a hidden field on the Notes form, it will be null when the user does a post command from the web. If you look at the HTML given to the browser, that field isn’t found. It makes sense that it wouldn’t get posted back to the server.
Subject: RE: Serious 6.0.1 Web Server Regression Bug
While you are correct that hidden fields do not get posted back to the server, when you access the back-end document in a WebQuerySave agent (via session.DocumentContext), the hidden fields do exist with their default (for editable fields) or computed (for computed fields) values.
As it turns out, the problem is not related to CGI variables at all. The problem is that fields in subforms are no longer accessible to WebQuerySave agents. It just happened that I had all my CGI variables defined in a subform. I’m going to post another main topic for this problem.
Subject: RE: Serious 6.0.1 Web Server Regression Bug
There is a new setting on subforms called “Available to Public Access Users”. See if checking this makes a difference.
Subject: Serious 6.0.1 Web Server Regression Bug
This is very timely, I had a situation today, where a person in our company used an R6 client (they weren’t supposed to) to edit a document on a R5 database. The document they editied would no longed return the CGI variables, like Remote_addr, Path_info etc.
I had to recreate the document with the R5 client.
Subject: Serious 6.0.1 Web Server Regression Bug
works OK for me on 6.01 !