ILLiad Known Issues

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  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# 4795

    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. The "Cancel - Return to Logon" button on the NewAuthRegistration.html page doesn't return users to the logon menu

    Clicking the "Cancel - Return to Logon" button on the NewAuthRegistration.html page doesn't allow users to stop the request form and return to the logon menu.

    Bug# 12648

    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 →
  3. Duplicate classes on Lending pages

    ILLiad Lending datarowDefaultRequest and includeTransaction menu contain duplicate classes.

    Bug# 10147

    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 →
  4. Empty persist value string

    An empty string would be produced when the persist value drop-down in the atlasUtility.js due to the handling of the double-quotes.

    Bug# 10061

    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. Fields marked as none when they should be hidden

    ​On user pages, delivery methods and "web" fields are set to display 'none' when the correct attribute needs to be:

    <input type=hidden...

    Bug# 8653

    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. Extra undelete icon in Action menus

    There is an extra span in include_TransactionMenu.html and any HTML files with the undelete button in the Templates folder.

    Workaround- change this:

    <a class="btn btn-light <#TRANSACTION field='RequestActionAllowed' name='UndeletePDF' disabledValue='hidden'>"href="<#ACTION action='21' type='11'>&Value=<#TRANSACTION field='TransactionNumber'>" class="menuUndeletePdf">
    <span aria-hidden="true" <span class="fa-stack" style="vertical-align: top;">
    <span class="fas fa-trash-alt fa-stack-1x"></span>
    <span class="fas fa-ban fa-stack-2x text-danger"></span>
    </span> Undelete Item
    </a>

    To this:

    <a class="btn btn-light menuUndeletePdf <#TRANSACTION field='RequestActionAllowed' name='UndeletePDF' disabledValue='hidden'>"href="<#ACTION action='21' type='11'>&Value=<#TRANSACTION field='TransactionNumber'>">
    <span aria-hidden="true" class="fa-stack">
    <span class="fas fa-trash-alt fa-stack-1x"></span>
    <span class="fas fa-ban fa-stack-2x text-danger"></span>
    </span> Undelete Item
    </a>

    Bug# 9309

    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. Blocked user status line styling is inconsistent

    The default blocked user page needs to be updated to consistently look like other pages.

    Bug# 7682

    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. Drop-downs missing options in the web pages

    Some drop-downs in the ILLiad default pages are missing options.

    Workaround - To add these options back into the default pages change this:

    <select id="AcceptAlternateEdition" name="AcceptAlternateEdition" size="1" class="custom-select mr-sm-2">
    <option selected><#PARAM name='AcceptAlternateEdition'></option
    <option>No</option>
    </select>

    To this:

    <select id="AcceptAlternateEdition" name="AcceptAlternateEdition" size="1" class="custom-select mr-sm-2" data-persistedValue="<#PARAM name='AcceptAlternateEdition'>">
    <option>Yes</option>
    <option>No</option>
    </select>

    Bug# 9383

    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. 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. Lending web pages reclassifying article requests as loan requests

    Lending web pages don't have an explicit request type tag/field and when an article request is submitted it's being reclassified as a loan causing the titles do not appear in the main menu.

    v9.1
    Bug# 5935

    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. 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# 5969

    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. 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. 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# 5018

    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. 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# 5062

    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. Errors on NewUser/NewAuthRegistration

    The wrong ID (CurrentPassword) is being assigned to the Username field on NewUserRegistration form.

    v9.0
    Bug# 5066

    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. 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# 5071

    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. 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# 5050

    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. 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

    released  ·  0 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  19. HTTP Headers

    The HTTP headers could potentially pose a risk of cross-frame scripting (XFS) in the ILLiad web pages.

    v9.1
    Bug# 4848

    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. Document Type Tags

    Document type tag can be a potential risk of cross-site scripting (XSS) in the ILLiad web pages.

    v9.1
    Bug# 4766

    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