Re: [IUG] New Webpac with little bugs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
We just went live with Millennium and Webpac and have a couple bugs for you Webpac gurus to ponder.


1.) In IE, we get an error in lower left corner on Author, title, subject and number pages. We did discover ie_styles.css is missing from /screens directory, because it didn't come with 2007 example set, but don't think that's the issue.

Line: 33
Char: 1
Error: document.forms.0.elements.1 is null or not an object
Code: 0

You have javascript in your BODY tag that tries to put the cursor in the first input field of the catalog search
<body onload="document.forms[0].elements[1].focus();">

But the first form (forms[0]) on these pages is your quicklinks popup menu.

Give your catalog search form and ID tag, and the input field another ID tag, then change your body tag to
<body onload="document.SearchFormID.InputTagID.focus()">
Then it will work regardless of the other forms on these pages.

2.) Once we invoke secure My library account page, you get the annoying IE warning: "page contains non-secure and secure content, do you want to display?" We know how to enable mixed content in Tools/Options/Security/Custom/Miscellaneous, but wonder if it can be controlled by our server.

It appears everything on the page is being served securely. The Live HTTP Headers add-on for Firefox is your friend here. View: Web Page Privacy Policy in IE would also show items served from a non-secure server.


3.) Content café sometimes displays placeholder: "Book cover", mainly on LPs, microforms and periodicals which have custom bibliographic material types, but not exclusively and usually there's no placeholder at all if no image.

This is the alt text displaying because CC is not responding fast enough to the 50 image requests. We see the same thing with Syndetics since switching from 12 to 50 results on a keyword search page.

4.) How do you add the scope limiter to the Advanced Keyword page, in addition to bib location, material type, language etc.?

<!--{scope}--> should work, but we just manually add the code for the popup (select) menu.
--
Robert Sebek
Webmaster, University Libraries, Virginia Tech
http://www.lib.vt.edu
(540) 231-1849