ILLiad Known Issues
37 results found
-
HTML encoding in OpenURL date fields breaks OpenURLMapping formatting When the date field in an OpenURL string contains HTML encoding, ILLiad will not format the date and imports no values.
Bug# 31435
1 vote -
The cache for WebReports is currently set to not store for only Firefox When the cache isn't cleared in Chrome it can lead to http protocol/security errors, so we should add Chrome and other browsers to that code.
Bug# 31919
1 vote -
Incorrect WebFormNames for lending web pages A lending default web page has an incorrect WebFormName. LendingUpdateAddressInformation
Bug# 30856
1 vote -
ILLiadAuthUserRegistrationEnabled customization key does not work if the WebAuthType key is not set to ILLiadAuth Setting the ILLiadAuthUserRegistrationEnabled customization key to No does not disable ILLiadAuth user registration unless the WebAuthType key is set to ILLiadAuth.
This means that if a site is using LDAP, they cannot prevent ILLiadAuth user accounts from being created by setting the ILLiadAuthUserRegistrationEnabled key to No.Workaround: Remove or rename the FirstTimeUsers.html page so that patrons cannot get there to click to get to the NewUserRegistration.html page. Optionally also rename/remove the NewUserRegistration.html page.
Bug# 25019
1 vote -
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 -
Request data may be lost when a request is submitted after the user's NVTGC is changed If a user's NVTGC is changed while the user is filling out a request on the ILLiad web pages, the request will still be submitted when the user clicks the Submit Request button, but the data the user entered into the request form will not be saved to the request.
Bug# 27212
0 votes -
Ampersand in username causes error in ILLiad web pages when viewing PDFs If a user has an ampersand (&) in their username, they are unable to view PDFs on the ILLiad web interface and receive the following error:
"Error: You may only view transactions that belong to you."
Bug# 27622
0 votes -
The Atlas Authentication Portal is missing the log configuration file The Atlas Authentication Portal has support for logging, but is not currently distributed with the necessary App_Data folder and log.config file to enable logging.
Bug# 26220
0 votes -
Submitting an OpenURL request as new RemoteAuth user can lead to a blank form submission In a Shared Server setup, requests submitted via OpenURL by new RemoteAuth users may be blank after the user creates their account and submits the request form.
Bug# 25395
0 votes -
Timestamps may be inconsistent for actions performed via the ILLiad web interface The date-times used on Transaction and other records to record timestamps for actions performed via the ILLiad web interface (e.g., updating Transaction Status) may be inconsistent in value when the server timezone differs from the database timezone.
Bug# 25157
0 votes -
User notification preferences are not set if user is moved across NVTGC web pages as they register If a user creating a new account on the ILLiad web pages selects a pickup location/NVTGC on the user registration form that is different from the NVTGC associated with the set of web pages being used to register, then notification preferences will not be set when the account is created.
Bug# 21707
0 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# 20309
0 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# 19824
0 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# 18395
0 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# 18013
0 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# 18091
0 votes -
Unused JavaScript file in the ILLiad Lending web pages The userNotificationPreferences.js file located in the default ILLiad Lending web pages is unused in the web interface and unnecessary.
Bug# 18086
0 votes -
Error page is not displayed by the Lending DLL when the DBC file can't be found A "File Not Found" error is displayed instead of the Error.html web page when the Lending DLL is unable to find the DBC file containing logon settings.
Bug# 18004
0 votes -
Lending web directory path is logged incorrectly by the DLL The path to the Lending web directory is incorrectly logged by the Lending web DLL.
Bug# 17999
0 votes