Since our server upgraded to R6, we have several problems with Javascript on the web.
-
First database is still R5 and should remain this way. I updated a javascript function (in the header). This update can be found in all new documents, while old documents still have the old function in the source. It appears that the javascript is stored in the document, not on the form. Has anyone experienced the same problem?
-
Second db is R6. I had to update all javascript functions when we went from R5 to R6 (edit and save them again). When I copy this R6 db, I have to update all javascript functions again. If I edit and save them, everything works again. But I cannot imagine that a have to do this everytime I copy a form, javascript library…
All info is much appreciated
Ellen
Subject: R6 Javascript bug
If the old JavaScript is still on the old documents, it can only mean that you are storing the form in the document. Stored forms don’t update when the form design changes.
OH – have you noticed that there are two JS headers – one for the Notes client and one for the web? If you have edited the wrong one, then the old code will still be in the other one, but it will be the same for both new and old documents.
Subject: R6 Javascript bug
I never heard about such things, I updated several servers.
-
Where did you enter the function, must be saved within the document.
-
Didn’t have this problem, where is your javascript coded? In the form, a linked page? I only had a problem with character sets, there is a new option in R6.
Subject: RE: R6 Javascript bug
Hey Guys,Thanks for you quick responses.
-
I indeed have the option “allow use stored forms” selected. It does sound logical that all code is stored in de document then. But when I used to changed something to my form, it was always shown in each document, also the old ones. So I never had any problems with updating a form. Maybe it works differently in R6?
-
Do you guys know where I can find some info about what has changed in R6 concerning Javascript? Does “common javascript” mean that it works for both client and web? Because that is where I put my code. The code I have to edit and save when I make a copy.
Greetings
Ellen
Subject: RE: R6 Javascript bug
-
I think Stan didn’t think of the database option “allow …” but the form option “store form in document”, look for that one.
-
common javascript means that it works for client and browser. I normally don’t use that event, but I haven’t heard about problems using it except that the javascript functionality for client is limited compared to the browser.
But the code for client and browser is always the same when common javascript is selected, so that is not your problem.
Subject: RE: R6 Javascript bug
Except that a database that’s transitioned from R5 to ND6 gets the R5 code in ALL of the JS slots, so the client-specific code may still be there.
Subject: R6 Javascript bug
Aah, that option :-). No, I don’t have the option “store form in document” enabled. Any other ideas?
Thanks!