ILLiad Known Issues

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  2 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  4. Radio button controls on ViewSearchResults.html are improperly formatted

    The width: 100% property in the default CSS for label elements results in improper formatting/alignment for the radio buttons on ViewSearchResults.html.

    Bug# 13557

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  5. DLL incorrectly displays detailed error information to users

    When an error is encountered, the ILLiad DLL is displaying detailed error information that should not be visible to end-users.

    Bug# 12291

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  6. Status-specific include pages do not work on SiteMap.html

    When using a status-specific include page to display content on SiteMap.html, the default include page and associated links are displayed instead due to an error in the DLL.

    Bug# 11764

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  7. Unencoded ampersands in ILLiad 9.1 Default Web Pages

    A number of href attributes for <a> tags in the ILLiad default web pages improperly contain unencoded ampersands.

    Bug# 11203

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  8. Duplicate request submission when refreshing after expired web session

    After submitting a request, a duplicate request will be submitted if the web session expires and the user logs back in after refreshing the page.

    Bug# 11148

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  9. Item Author appears twice in include_detailedTransactionInformation.html

    In the include_detailedTransactionInformation.html default 9.1 web page, Item Author appears twice:

    Item Author <#TRANSACTION field='PhotoItemAuthor'>
    Item Place <#TRANSACTION field='PhotoItemPlace'>
    Item Publisher <#TRANSACTION field='PhotoItemPublisher'>
    Item Author <#TRANSACTION field='PhotoItemAuthor'>
    Item Edition <#TRANSACTION field='PhotoItemEdition'>

    Bug# 10618

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  10. hangeUser Button Alignment

    The alignment for the buttons at the bottom of ChangeUserInformationare set to be right-aligned by default. For consistency, these need to be left-aligned like in the NewRegistration page.

    Bug# 7683

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  11. Duplicate form submission does not work under remote authentication

    Remote auth validation does not load the user's reported session id, duplicate form submissions aren't being prevented.

    Bug# 9013

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  12. DLL shows incorrect date/time on transaction notes

    The date shows up correctly in the client and the database but not in the transaction notes.

    v9.1
    Bug# 7847

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  13. Adding new lines to the web alerts breaks the alert

    When adding carriage returns, it breaks the JSON parse.

    Workaround: Use a <br> tag before starting a new line to ensure the alert will display properly.

    v9.1
    Bug# 7172

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  14. Extra closing div tags in ILLiad 9.1 Default Web Pages

    The web pages with extra div tags include:

    EditArticleRequest
    EditBookChapterRequest
    EditConferencePaperRequest
    EditGenericRequestTesting

    Bug# 6022

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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# 5893

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  16. Routing in Scripting can be overwritten by SaveDataSource

    In an ILLiad addon:

    When you make changes to transaction fields, route the transaction and then SaveDataSource it will undo the Route action.

    Workaround: This can be avoided by saving before routing.

    Bug# 4681

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  17. Web validation rules for required fields don't account for 'NULL' special value

    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# 4602

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  18. 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# 4601

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  19. 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# 4571

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  20. 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.

    Bug#4444

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1

Feedback and Knowledge Base