ILLiad Known Issues
143 results found
-
ILLiad print datasource using legacy headers
When printing the PrintAddress.doc template from the client, the PrintAddress.xlsx data source file that is created has the Legacy style headers for both the Legacy queue and the Print queue.
v8.7.2
Bug#37970 votes -
BillingManagerPrintDataPath defaults to C:\illiad\print\ on Client install
The data source for the Billing Manager printing process still defaults to C:\illiad\print\ in the Customization Manager, but newer installations of the ILLiad client don't create this folder. This only occurs for new installations who don't have the print folder from previous installations.
v9.0 & 8.7
Bug#38870 votes -
0 votes
-
System addons that explicitly set FormNames can result in loading the addon multiple times
If a system addon is created but FormNames are also entered, the addon will be loaded for both the system script environment and for each form script environment that is specified. An example where this causes errors is when registering system event handlers which can only be registered to a single addon.
Forms are not relevent in Library, System, or Server addons.0 votes -
0 votes
-
Lender Address form throws an error
FormLenderAddresses will throw an exception when the request tab is opened without the lender being saved first.
0 votes -
0 votes
-
Odyssey Manager creates blank pdfs
Odyssey Manager fails to convert large TIF files of approximately 1 GB to PDF. The log does not indicate a problem but shows the process occurring in just a few seconds. The resulting PDF file is blank.
1 vote -
Unable to modify some ZServer configuration fields in Customization Manager for MARC records
If a Z39.50 server configuration is set to use MARC holdings, the availability fields become read-only. If you need to edit the availability fields, please contact your support representative so they can edit directly in database for you. v8.7 and v9.0
1 vote -
Change Password form does not have correct tab ordering for the ForcePasswordReset checkbox
The Force Password Reset checkbox does not have the focus prior to the Ok button for proper Top->Bottom & Left->Right expectations. v9.0.3
0 votes -
3 of 9 barcode font missing after Version 9 update
Some customers are experiencing issues with the 3 of 9 barcode font being removed during the 9.0 client update. This seems to be dependent on previous install/update scenarios.
Workaround: The issue can be resolved by manually installing the font or re-running the client installer in repair mode.
0 votes -
Z39.50 YazLoader typo & wrong dependency loaded
Repro Steps
The YazLoader class (only used for loading Z39.50 in an addon) has a typo and should be libraryname. Also the YazLoader is not loading the zlib1.dll file despite the log indicating it has. It actually loads libxslt.dll a second time. zlib1.dll is a dependency of libxml2.dll and not a direct dependency of yaz3.dll which has allowed it to not work with bundling the zlib1.dll with addons using this. Currently the LendingAvailabilityAddon for Wisconsin is the only user of this code.[DllImport("kernel32", CharSet = CharSet.Unicode, SetLastError = true)]
private extern static IntPtr LoadLibrary(string librayName);
....
log.Debug("Loading zlib1.dll");
LoadLibrary(System.IO.Path.Combine(path, "libxslt.dll"));1 vote -
ILLiad Reports - Prior NVTGC Remembered if back button used
Repro Steps
ILLiad reports sometimes generate with more sites than were intended.Steps to Reproduce
- Find or set up an ILLiad server that has multiple sites
- Go to <illiad_server>/ILLiad/webreports
- Choose any report and select one of the sites that is not "ALL". Make sure that the selected site is the only site that is selected.
- Generate the report, notice that the
Workaround
If you use the menu links when navigating the WebReports module, this issues does not occur.
1 vote -
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 -
Changing layout of tabbed groups on Main Menu causes owner issue
Repro Steps
When splitting out the Borrowing, Doc Del, and Lending tabbed groups to all show, an error is shown and queues do not load properly when the client is opened.- Customize Layout on main form by right clicking on Borrowing and choosing customize layout. 2, Switch to the Layout Tree View. Choose the Requests tabbed group and right click and select "Ungroup Tabbed Group"
- Save the layout for the user
- Close/Reopen the client.
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 -
The ILLiad DLL does not correctly set more than one cookie at a time.
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 -
Request cloning from the staff client will always set the RequestType to Article
Repro Steps
1. Open a loan request in the staff client
2. Clone the request. The behavior is the same regardless of cloning to same user or different user and if the request is/is not opened after the process is completed.4 votes -
Need to remove ESPUpdate table entry for Received when the error is "Received not allowed here"
If we receive the error we should ensure that the ESPupdate is removed so that it will not attempt to retry since we already know that OCLC will consider it invalid based on it's current state.
1 vote