We upgraded our server to 6.5 from 5.0.11 last week. Afterwards, there were a couple of problems with our web-based application, which I’ve since been able to fix, but I thought I would share them in case it is useful to anyone. Feel free to add any thoughts/additional suggestions to this:
-
JavaScript routines did not work, which caused forms to load incorrectly. The HTML declarations to include the .js page libraries did not work. The solution was to use the new R6 feature of creating JS script libraries, copy in the info. from the pages, and then on every form which uses it, insert resource into the top of the JSHeader. Also, removed the HTML lines which include the JS pages, from the $$HTMLHead field.
-
The LCConnection.Call statement for stored procedures on the AS400 did not work. There is documentation on this forum as to how to get this to work (by first defining certain lcconnection properties such as ownername) but I still was not able to do it. The workaround solution was to change the LCConnection.Call(parmfieldlist, recordindex, destfieldlist) to a LCConnection.Execute(statement, destfieldlist), and embedding the “Call library.storedprocedurename(parameters)” in the first parameter of the Execute statement. As we had calls to several stored proc.'s, I had to standardize writing the stored proc. parameters into a string, and putting single quotes around the text values.
-
See my response 3 postings down for one more problem discovered.
Subject: FYI: 6.5 upgrade - application problems and fixes, workarounds
RE: issue #1 – setting the page “Treat as” to “Other: text/javascript” would have solved the problem. Domino 6+ is not ambiguous about served content type, and the accept-type in the HTTP request for the javascript “file” (assuming the calling page is declared as HTML 4.01 transitional) would specify that the browser would only accept text/javascript files. (That, by the way, was one of the nastier tricks used in a recent “hack this site” game on the web. The username and password were in clear text in the linked JavaScript file, but if you created a link to download and examine the JS you got a different file. Getting the real JS file from the browser cache was the key.) Not only did the file have the wrong MIME type, it may have included an HTML 4.01 doctype declaration.
Subject: FYI: 6.5 upgrade - application problems and fixes, workarounds
Thanks, Stan Rogers, for your input!
I discovered one more problem in our application as a result of our upgrade. One of our forms had its JSHeader javascript code in the wrong “Run” setting: it had been set to “Client Javascript”, when it should have been “Client CommonJavascript”. Apparently it did not matter in R5, but after the upgrade this caused the form to load up blank, because the script wasn’t executing. After I changed it to “CommonJavascript” it worked. This was the only form in the database that had its JSHeader on this setting, for some reason, and it drove me crazy all day trying to figure out what was wrong. Just something to watch for.