Various Javascript errors in console

Bug #491546 reported by Joe Atzberger
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Evergreen
Won't Fix
Low
Unassigned

Bug Description

There are a large number of js errors reported in console. I don't have time to ferret out fixes to them all right now, so this ticket will serve a list of those encountered. All these can be experienced between login, F4 (patron search) and retrieve patron.

Versions:
Evergreen: 1.6.00.0099 trunk
Xulrunner: 1.9.0.13

Error: _l is not defined
Source File: chrome://open_ils_staff_client/content/OpenILS/util/org_utils.js
Line: 117

"Error: not well-formed" is given for the first line of each these files, relative to the C:/Users/atz/Documents/current-client-build/vm7_build/chrome/ directory (in order):
   locale/en-US/offline.properties
   locale/en-US/auth.properties
   content/util/error.js
   content/util/sound.js
   content/util/window.js
   content/auth/controller.js
   content/OpenILS/data.js
   content/util/network.js
   content/util/file.js
   content/util/controller.js
   content/auth/session.js
   content/util/widgets.js
   content/util/mozilla.js

That is confusing because some of those files aren't even javascript!

Minor Warning: Deprecated property window.title used. Please use document.title instead.

[Exception... "Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIXMLHttpRequest.statusText]" nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)" location: "JS frame :: chrome://open_ils_staff_client/content/main/JSAN.js :: anonymous :: line 520" data: no]

On many pages, including patron search and patron search results:
     Warning: Empty string passed to getElementById().
This appears to be common, probably harmless (but sloppy).

Error: obj.summary_window.g is undefined
Source File: http://dev-vm7.lan.hq.esilibrary.com/xul/2009-12-01T16:45:26/server/patron/display.js
Line: 655

Error: uncaught exception: [Exception... "Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch2.getIntPref]" nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)" location: "JS frame :: chrome://global/content/bindings/findbar.xml :: :: line 371" data: no]

Revision history for this message
Chris Sharp (chrissharp123) wrote :

I am receiving a JavaScript error like these when exporting transactions from the staff client and attempting the "auto purge" feature:

[Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIFile.moveTo]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://open_ils_staff_client/content/main/main.js :: anonymous :: line 227" data: no]

My steps:

1. Create offline transactions.

2. Export Transactions (from login screen)

3. Select Yes that I would like to purge transactions from the staff client.

4. The above error appears and transactions are not purged.

Current workaround is to manually delete the pending_xacts file from the chrome directory.

Revision history for this message
Chris Sharp (chrissharp123) wrote :

Forgot to mention... This occurs in 1.4.0.X and 1.6.0.X staff clients.

Revision history for this message
Mike Rylander (mrylander) wrote :

Chris, yours is a different bug. To avoid it getting lost, please report it separately.

Revision history for this message
Chris Sharp (chrissharp123) wrote :

Thanks, Mike - will do.

James Fournie (jfournie)
Changed in evergreen:
importance: Undecided → Low
status: New → Triaged
Revision history for this message
Jason Stephenson (jstephenson) wrote :

Lots of JavaScript errors appear in the console still with the 2.0 b4 client. This doesn't seem to be a high priority, though, as they do not appear to affect functionality.

Revision history for this message
Jason Stephenson (jstephenson) wrote :

Haven't done anything about it by now, we probably never will.

Changed in evergreen:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.