Error in site JavaScript

[FaithWorks]

We copied the required files and folders to our Cloud Server.
When we type in Localhost:88, we get the following messatge:
"Error in site JavaScript"

Help.  What are we doing wrong?

[Bruce]

does the error appear, then disappear, or just appear and stay there?

If it appears and stays there then check your Browser, Developer Tools, Console window for the error.

If it appears and disappears then this is "by design" behaviour that checks for javascript errors. You can disable the test (when deploying) using the template setting on the Performance tab.

cheers
Bruce

[FaithWorks]

If it appears and stays there.
The display of the web-page is also not formatted.

[FaithWorks]

It appears and stays there. 
The display of the web-page is also not formatted the same as on the local machine.

[DonRidley]

Regarding this:

The display of the web-page is also not formatted the same as on the local machine.

Do you have the Settings controls added to your web server? (see attachment)

If you do, make sure the paths for your web folder is correct.  Sometimes that path can be incorrect when copying your files from one machine to another.

Don

[Rene Simons]

Hi,

I have the same problem NT11.13 . See attachment.
(I don't know where the :46 comes from in the bottom line of the error-list.)

The red banner with "Error in site JavaScript" stays visible in the web-page all the time.

The button-clicks are received in the web-server. I can see that in the performance tab of the NTWS-Window. But nothing like e.g. a form appearing, happens.
Also the icons have disappeared from the buttons.

Cheers,
René

[Bruce]

>> If it appears and stays there. The display of the web-page is also not formatted.

If that is the case then open developer tools in the browser, and take a look at the console there for the errors. If the error does not mean much to you then post a screen-shot here like Rene did.

Cheers
Bruce



 

[Bruce]

"nts is not defined"

nts is declared in nt-websockets.js which implies you are using web socket functionality on one or more windows, but either;
a) you have not ticked on support for web sockets on the WebServer procedure, scripts tab or
b) you haven't run gzipall.bat since turning that on or
c) you have not deployedd the new all.js and all.js.gz

Cheers
Bruce

[Rene Simons]

Hi Bruce,

It WAS the sockets-thing that was wrong.
Everything looks and behaves normal again.
Thanks,

René