ILLiad Known Issues
47 results found
Format field value (e.g., DVD, CASSETT, etc.) on the Multimedia form does not save to database
Bug# 58520 votes
Some unicode characters are not properly encoded on OpenURL submissions if the user must log in first.
This seems to be a new issues introduced in ILLiad 8.7 when we switched to Delphi XE 8. To reproduce, submit an OpenURL request using the included URL both with and without a session. When you're already logged in, the cyrillic characters are rendered correctly in the author field and a ligature is used in the title. If you don't have an active session and are sent through the logon2 page, those fields will be rendered as ?s or boxes, indicating a problem with the form state encoding. I confirmed this URL worked correctly on ILLiad 8.6.x and earlier.2 votes
UTF-8 characters are not decoded properly in some cases
For OpenURL requests, if the patron already has an active websession and do not have to log in the characters are correctly translated.2 votes
Tracking entries on the ILLiad web pages may display in the incorrect timezone
Tracking entries for requests on the ILLiad web pages are not converted to the local timezone and may display at a different time than what is shown in the ILLiad Client.
Bug# 207390 votes
Label elements are incorrectly formatted on certain Lending web pages
The label elements for the LibraryName and BorrowingDeptEmail fields are missing or improperly configured on the LendingNewUserRegistration.html and LendingUpdateAddressInformation.html default Lending web pages, which causes accessibility issues.
Bug# 204050 votes
Notification preferences not set for users created from UserValidation with LDAP
Notification preferences will not be set for new users created via the UserValidation table if LDAP authentication is being used.
Bug# 203090 votes
SearchType toggle switch does not properly filter search results
The SearchType toggle switch on the search web pages (ViewSearchResults.html and LendingViewSearchResults.html) that is unused and commented out in the HTML by default will not correctly filter search results to include active requests only if enabled.
Bug# 199700 votes
Small notes are not automatically read by screen readers for certain form fields
Small notes used for certain form fields on the default web pages will not be read automatically by screen readers. This includes:
-The Password1 field on NewPassword.html, ChangePassword.html, NewUserRegistration.html, LendingChangePassword.html, LendingNewPassword.html, LendingNewUserRegistration.html
-The Username field on LendingNewUserRegistration.html
Additionally, the CurrentPassword field on ChangePassword.html and LendingChangePassword.html contains an unlinked aria-describedby attribute that may be flagged by accessibility checkers.
Bug# 199350 votes
Lending DLL is not configured as an application in IIS by default
When the SAML module is configured for ILLiad, the Lending web pages may direct the user to the identity provider (IdP) login page since the Lending folder within the ILLiad web folder is not configured as an IIS application by default in ILLiad installs.
Bug# 198240 votes
Buttons that are disabled can still be used with keyboard controls
In both the Actions menu dropdown and the Transaction menu, some actions that are completely disabled for mouse users can still be fully used by keyboard users without being blocked and with no error message.
Bug# 189190 votes
Transaction menu button text is not fully visible on certain display sizes
The text content of the transaction menu buttons does not fully display on small screen sizes or high zoom levels and requires horizontal scrolling to view. In some cases, horizontal scrolling is not enough to read the full button text.
Bug# 189180 votes
Actions dropdown options are not fully visible on certain display sizes
The Actions menu dropdown options do not fully display on small screen sizes or high zoom levels and require horizontal scrolling to view.
Bug# 189160 votes
The color used for web alert titles does not pass color contrast requirements
The default color used to display titles for web alerts does not have sufficient color contrast against the default background color in the web pages.
Bug# 187740 votes
Modal dialog for web alerts contains broken 'aria-labelledby' attribute
The 'aria-labelledby' attribute used on the modal dialog for web alerts is broken and causes an accessibility issue.
Bug# 187750 votes
The label color for fields that fail server validation does not pass color contrast requirements
When a field fails server validation, the web pages set the color of the field label to a red color that does not pass contrast requirements with the default form section color.
Bug# 187670 votes
Hyperlinks added to the cookie consent banner will fail color contrast requirements
If a hyperlink is added to the cookie consent banner, the default hyperlink color will not provide sufficient contrast against the banner's background color.
Note: Hyperlinks are not present in the banner by default.
Bug# 184850 votes
Processed requests can be resubmitted if edit form is left open in the web
If a request is left open in the edit form by the user on the web interface and staff proceeds to process that request to a status where editing is not allowed (e.g., Request Sent), the user will still be allowed to submit the request from the edit screen, which will return it to a prior processing status.
Bug# 183950 votes
LendingWebPath customization key is referenced in the DLL but missing from the Customization Manager
A LendingWebPath customization key to specify the path of the Lending web directory is referenced in the DLL but missing from the ILLiad Customization Manager.
Bug# 180130 votes
Default FAQ web page contains inaccurate information about cookies
The default FAQ web page contains information about cookies stating that "the technology that we use sends a Session ID to be stored on your machine. You can refuse this cookie and still be able to use ILLiad without any problems."
This information is inaccurate as the Session ID cookie is essential for the ILLiad web interface.
Bug# 182650 votes
An error status message is not displayed by the Lending DLL when the web page can't be found
If the Lending DLL can't find a web page, the user is sent to the Error.html page but a status line is not displayed explaining the error.
Bug# 180910 votes