Javascript Error in a basic include

[Kaelon]

I do have Sun's "real" Java installed. (JRE 2 Series) IE is returning Javascript Errors, which are typically different from "Java" errors, as I understand it.

[Dream]

right click on the page that give errors, view the source and paste it here, along with the javascript errors, then someone might be able to help

[Cloudrunner]

Originally Posted by Dream

right click on the page that give errors, view the source and paste it here, along with the javascript errors, then someone might be able to help

Also remember, that Firefox suppresses javascript errors so that they do not bug the users of the browser.

If you are doing coding work and using FF as a debugger then you'll need to extend it with something so that you can see the javascript errors if they happen. I use the extension Web Developer 0.9.3 in my FF. It gives a better idea of the javascript errors, and still suppresses the error pops, but notifies you in your toolbar via a red 'X' instead of a green checkmark. It has come in handy.

Another alternative that I have found is designed specifically for javascript debugging called Venkman, Mozilla's answer to the Javascript debugger that IE comes with. Can be found here: http://www.hacksrus.com/~ginda/venkman/

I just installed that extension, and am testing it now....

[Andreas]

Erm ... you don't need an Extension on FF to view JS Errors, just click Extras/JavaScript-Console

[Zachery]

FYI, don't forget the $headinclude template, very very important... (has all that js code that the browser is probally looking for).

[Cloudrunner]

Originally Posted by KirbyDE

Erm ... you don't need an Extension on FF to view JS Errors, just click Extras/JavaScript-Console

really?

I didn't realize that as..thanks!

[Kaelon]

Well, I found the problem. Apparently, it's looking for js files located at /root/clientscript/filename.js (when these files are actually located at /root/forums/clientscript/filename.js). Without writing my own $headinclude, is there any way I can correct this?

Thanks!

[Andreas]

Symlinks

[Kaelon]

Kirby - What do you mean by Symlinks?

I did fix the problem. Basically, I edited $headinclude to use absolute paths, rather than relative paths, to the javascript files. No more javascript errors.

[Andreas]

Well, changing the Paths is also an Option. However, you must redo the changes if you must revert the Template.
Therefore Symlinks (Symbolic Links, eg. /foo/bar/file1.js pointing to /foo/bar/anotherdir/anotherfile.js at OS level) might be a better alternative