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
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
The ILLiad web DLL will perform special handling for text values equivalent to 'null,' replacing them with an actual null value when it updates the database.
Bug# 46020 votes
In the web, 'null' is a special string that can prevent some valid data from being inserted, specifically as a user last name.
ILLiad does a case-insensitive comparison of the field value and will treat a user record with the LastName of Null as null when it updates the database.
Bug# 46010 votes
The renewal button in the ILLiad web pages may be enabled even if the due date is outside the renewal window
The renewal button doesn't consider the due date and the RenewalWindowDays/RenewalBeforeWindowDays customization keys when determining if the button is visible in the web pages.
Bug# 45710 votes
The BillingInformation table in the Lending Web Pages will not display if BillingActive is set to false
The lending web pages prevent the display of the billing information table when BillingActive is set to false.
Workaround: If BillingActive is set to BillingActiveLending, then the BillingInformation table will always display in the lending web pages.
When a user changes a Lender's password from the ILLiad client, it only changes the password for the NVTGC that the user is logged into the client under, instead of changing it for all NVTGCs. As a result, the lender may be able to log into the client under that particular NVTGC but unable to log into the web.
v9.0 & 8.7
Bug# 44360 votes
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).
This error occurs with Aeon and ILLiad integrations.
The invalid username status line doesn't seem to be triggering the SLLoginFailed customization key on the Forgot Password page. The status line does appear if triggered on the logon pages.
v9.0 & 8.7
The Force Password Reset checkbox does not have the focus prior to the Ok button for proper Top->Bottom & Left->Right expectations. v9.0.30 votes
ILLiad- Statuses do not alert screen readers about the problem on the page (incorrect password, failed validation, etc)
It is very confusing to fail validation while using a screen reader because it isn't apparent that validation failed.
It should likely alert the user on page reload.1 vote
This is not actually a bug yet because the illiad.dll doesn't set more than one cookie at a time. However, if SetCookie() were to be called more than once it would overwrite the cookie custom header.1 vote