ILLiad Known Issues
54 results found
-
Editing a request in lending pages creates duplicate request
Editing a request in the lending web pages creates a duplicate request with the changes made instead of saving the changes to the original request.
v9.1
Bug# 59690 votesFixed in 9.1 Web Page Release on 4-9-2020
-
Web alerts not appearing for Status and Delivery Location
Web alerts for Status and DeliveryLocation don't appear on the web pages for users to when generated through the use of the AJAX (https://support.atlas-sys.com/hc/en-us/articles/360039292194-Performing-an-AJAX-Request-to-View-Customize-Web-Alerts).
v9.1
Bug# 58930 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in ILLiad 9.2
-
0 votes
Released in ILLiad 9.1.1
-
LDAP users are being sent to the Main Menu instead of the Request page
LDAP users who attempted to create a new user after coming in through an OpenURL link are being sent to the Main Menu instead of the Request Page after registration.
v9.1
Bug# 50180 votesReleased in ILLiad 9.1.2
-
Not all fields are displaying at the correct width in the default web pages
In the 9.1 default web pages, some fields are not displaying at the correct width within the default web pages.
v9.1
Bug# 50620 votesReleased in ILLiad 9.1.2
-
Errors on NewUser/NewAuthRegistration
The wrong ID (CurrentPassword) is being assigned to the Username field on NewUserRegistration form.
v9.0
Bug# 50660 votesReleased in ILLiad 9.1.2.
-
Color consistency - The button for the include_nav_search
The search button on the Navbar is green instead of utilizing the default blue for consistency. In addition, the size of the nav_search button needs to be adjusted for consistency.
v9.1
Bug# 50710 votesReleased in ILLiad 9.1.2.
-
Menu options do not properly display in the patron web pages
Custom statuses set in the DisplayStatus table (e.g., using "Ready for Pickup or Checked Out" as a display status for "Checked Out to Customer") would not display certain menu options (e.g., renew, clone, etc.) in the patron web pages because the <#MENU> tag would not read the custom statuses as a valid status.
v9.1
Bug# 50500 votesReleased in ILLiad 9.1.2
-
UserNotificationPreferences are not initialized for new users created through Automatic User Creation
v9.1
Bug# 48080 votes -
HTTP Headers
The HTTP headers could potentially pose a risk of cross-frame scripting (XFS) in the ILLiad web pages.
v9.1
Bug# 48480 votesReleased in ILLiad version 9.1.1.
-
Document Type Tags
Document type tag can be a potential risk of cross-site scripting (XSS) in the ILLiad web pages.
v9.1
Bug# 47660 votesReleased in ILLiad version 9.1.1.
-
Change Password submission does not display status line for passwords successfully changed
When staff force a password is forced reset from the client for a web user, pressing the submit button successfully changes the password, BUT it reloads the change password page with blank values and without a status message stating the password has been successfully changed.
v9.1
Bug# 47950 votesReleased in ILLiad 9.1.2
-
ILLiad users are not prompted for password change after 9.0 update
When a user who has an ILLiad login and an AuthType of Default tries to log in to the ILLiad web pages when WebAuthType=RemoteAuth, they are able to log in without being prompted to change their password (when trying to log in for the first time after the upgrade).
v9.0
Bug#42140 votesReleased in ILLiad 9.1
-
External Request Controller is checking for the Aeon status even if ExternalId is null
The ILLiad ExternalRequestController is attempting to retrieve statuses for external requests that had never been created in Aeon. The check is parsing the ExternalID as an integer but when null, fails.
This error occurs with Aeon and ILLiad integrations.
v8.7.2
Bug# 38290 votesReleased in ILLiad 9.1