Hi,
My Javascript files do not open after I upgraded to the current version. Would anyone know why Javascript files won't open?

Also when i try to open a js file by right clicking and selecting 'Open in Associated Application', I get a Windows Script Host syntax error.

Hi Glenn,
Have you restarted your pc or tried reinstalling the Editor. I've been editing js files in every version and they open fine for me. Your install might be corrupt.

It seems possible that Windows itself is the problem. If so, the following may help.

"Microsoft ® Windows Based Script Host" is Windows default program for opening .js files, and it seems to try to send one to it if, in File Explorer, one right clicks on a .js file.

If The HTML Editor is set as the program for opening .js files, it should do so on double-clicking rather than on right-clicking on the file in File Explorer.

If the above doesn't help, it may be necessary to associate .js files with The HTML Editor. It can also be done by right-clicking in File Explorer on a .js file and choosing
1. Open with
2. Choose another app
3. More apps
4. CoffeeCup HTML Editor > Always use this app to open .js files > OK

The above is the procedure in Windows 11, but is probably much the same in Windows 10

Frank

I have 2 PCs with the editor installed. One with the previous version and the other with the latest (17.0 build 882). The latter started to produce this problem of not opening .js files form the left side pane 'my websites'. Though using 'open with' from File Explorer and choosing the Coffeecup editor works. On both PCs the file association for .js are the same, i.e. Windows Script Host.
As a workaround I've added *.js to: Tools>Preferences>Files>Server Files. Probably better to add it to Text Files, which also works, as .js files are not server files.

Louis

Javascript has some issues that sometimes require some familiarity. If there is an error in a file between and, that file often fails silently. This is usually true even if the block contains individual functions. You need to debug this to see where the problem occurs.

1 - The browser you are using may have a built in debugger (FireFox does).
2 - you need to debug it via "divide and conquer"

The latter is done by commenting out large blocks of the javascript (BUT STILL LEAVING USABLE CODE). If what's left works, look at what's still commented. If it doesn't work, further comment out code until it does and your previous commenting-out block contains the error. Do this as much as is necessary for you to locate the error.


Regards,
J wick