Get working with staff client

[GoogleCodeExporter]

x

Original issue reported on code.google.com by steven3...@gmail.com on 10 Jun 2014 at 8:38

[GoogleCodeExporter]

Original comment by steven3...@gmail.com on 8 Jul 2014 at 5:33

• Added labels: Priority-High
• Removed labels: Priority-Critical

[GoogleCodeExporter]

Not working in staff client. It seems none of the new javascript files have 
been pulled in from cdnjs.org. Either requirejs is not pulled in from the start 
or if it has, then it does not pull in the subsequent files.

Original comment by steven3...@gmail.com on 8 Jul 2014 at 7:20

[GoogleCodeExporter]

It's necessary to use a definite protocol, eg, 'https://' instead of '//', to 
refer to cdnjs file names. Now, cdnjs files are pulled in and can be seen 
within staff client using Venkman.

Another problem: json.parse(window.name) gets an error if window.name contains 
a simple text string.

Original comment by steven3...@gmail.com on 10 Jul 2014 at 8:24

[GoogleCodeExporter]

The json.parse problem is due to it parsing a plain text string which yields a 
Javascript syntax error, because the output is expected to be sensible 
Javascript. The fix is to execute json.parse inside a try/catch clause. The 
syntax error will be caught and can be sensibly handled.

Next problem: requests to the Overdrive API does not seem to be effective, ie, 
the reverse proxy mechanism doesn't seem to be working.

Original comment by steven3...@gmail.com on 11 Jul 2014 at 8:26

• Changed state: Started

[GoogleCodeExporter]

There is nothing wrong with the reverse proxy mechanism. But requests for 
metadata and availability don't return normally from the od_api layer, although 
we seem to get proper responses from the OD server.

Another problem: whenever the opac is running inside the staff client, which is 
indicated by the presence of boolean window.IAMXUL set to true, the user is 
already logged in, despite not going through the opac login sequence.

Original comment by steven3...@gmail.com on 16 Jul 2014 at 6:03