TECHZEN Zenoss User Community ARCHIVE  

Troubleshoot .js files?

Subject: Troubleshoot .js files?
Author: [Not Specified]
Posted: 2015-09-01 04:04

Hello,

surely a lame question but how/where do I see the possible JavaScript exceptions
Is it somewhere in Jetty's config Or
Thanks,



Subject: The only way I've found to do
Author: Jim R
Posted: 2015-09-02 11:21

The only way I've found to do this is by using the java script console in my browser's UI



Subject: Thanks, I couldn't find
Author: [Not Specified]
Posted: 2015-09-02 23:53

Thanks, I couldn't find anything else myself as well.



Subject: we highly suggest using
Author: Andrew Kirch
Posted: 2015-09-03 10:29

we highly suggest using Firebug, or similar (Chrome's Inspect Element should help as well)

Andrew Kirch

akirch@gvit.com

Need Zenoss support, consulting or custom development Look no further. Email or PM me!

Ready for Distributed Topology (collectors) for Zenoss 5 Coming May 1st from GoVanguard



Subject: Well the actually rootcause
Author: [Not Specified]
Posted: 2015-09-03 23:15

Well the actually rootcause of the issue (Site error/resource not found) was handled via checking the
Z2.log to see that ZenOss was trying to open a fileName.pt resource instead of simply opening fileName,
so after that I could figure out that the "action" attribute of the form in the .pt file was wrong (it contained the template/id uneededly)



Subject: +1 for Firebug, it is
Author: [Not Specified]
Posted: 2015-09-08 08:14

+1 for Firebug, it is absolutely essential to help learn about the inner core of Zenoss - I use it to watch the JSON go back and forth from the API.



< Previous
Display latest rrd point in device overview?
  Next
Issue with transforms
>