Skip to content

Aeon Known Issues

← Atlas Systems

Search known issues

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

89 results found

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

    v5.0
    Bug# 7246

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Web Interface  ·  Admin →

  2. The Aeon DLL does not correctly set more than one cookie at a time.

    The AeonSessionID cookie is not being cleared when the user logged out. SetCookie should be modified to properly append cookies.

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    released  ·  0 comments  ·  Web Interface  ·  Admin →

  3. Empty status div in Include_header_request.html

    There is an empty status div in the Includeheaderrequest.html page left over from the <#STATUS> tag being moved on request forms. The div currently isn't serving a purpose.

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    released  ·  0 comments  ·  Web Interface  ·  Admin →

  4. The EditEADRequest.html form doesn't work with web validation in the default web pages.

    Submit an EAD request, or update an existing non-photoduplication request's WebRequestForm field to EADRequest.
    Add a validation rule for the AeonForm specified in EditEADRequest.html, which should be EditGenericRequestEAD.
    Edit the request and submit values that will fail web validation.

    You will get a 'File not found' error, because it's trying to return you to the from 'EditGenericRequestEAD.html' which does not exist. Changing the AeonForm field to EditEADRequest does not work either; in that case you will simply get a blank page instead of the file-not-found error.

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  5. Logging in to the web will fail if the password contains certain characters, such as a plus sign.

    This was introduced in version 3.9.1 of the Aeon DLL.

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  6. If the LDAP server times out when logging in, the web DLL incorrectly reports that the username is not in the database

    This occurs when using two-step LDAP binding. If the LDAP server times out when attempting to authenticate the user, the SLUsernameNotInDatabase status line is erroneously shown.

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  7. Requests can be created in the web without web validation being applied.

    The DLL is allowing the creation of a new transaction from a GET request. Creating a new record (transaction/user/etc) should only be allowed with POST actions.

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  8. Submitting photoduplication requests from an EAD does not send the user to the View Order Estimates page

    Submitting photoduplication requests from an EAD does not send the user to the View Order Estimates page even when not configured to skip order estimates.

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  9. The Aeon web DLL does not properly read UTF-8 files that have been stored by the Atlas Auth Portal

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  10. Aeon FAQ uses Virginia Tech ILL email address

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  11. Past appointments and future appointments with start dates exceeding the Min Lead Days for the reading room are not viewable on web

    Users cannot view appointment details on the web interface for appointments with start dates in the past or with start dates exceeding the Minimum Lead Days setting for the reading room. Clicking on an affected appointment will display the SLAppointmentAssociationError status line to the user (default text: "Error: You cannot view an appointment you are not associated with.").

    Aeon 5.2

    Bug# 22857

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  12. Aeon 5.1 Scheduled Date date picker calendar does not properly color disabled dates

    Disabled dates are not colored correctly in the date picker tool used with the ScheduledDate field in the Aeon 5.1 web pages.

    Bug# 22802

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  13. JavaScript console error may occur when using the appointment scheduling web interface

    After typing a date manually into the Appointment Date text field on a web request form, pressing the TAB key or clicking the mouse to move focus elsewhere will return a JavaScript console error in the web browser.

    Bug# 19926

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  14. Search box on ViewSearchResults.html has poor contrast in some browsers

    The border used for the search box on ViewSearchResults.html does not meet color contrast requirements in some browsers, including Safari.

    Bug# 19937

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  15. Using the Enter key on the Saved Requests page selects all requests without announcing selection to screen readers

    Pressing Enter on the ScheduledDate field on the Saved Requests page (ViewUserReviewRequest.html) will checkmark select all requests on the page, without this change being announced to screen readers.

    Bug# 19801

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  16. MinimumLeadDays behavior functions differently for appointments vs requests

    The MinimumLeadDays value for a reading room configured in the Aeon Customization Manager will consider not only the current date, but also the current time when calculating whether a request can still be submitted for an appointment, but will not consider the current time when making the same calculation for whether an appointment can still be scheduled in the room.

    This means that it is possible for an appointment to be scheduled for the room that would then not allow any requests to be associated with it.

    Bug# 19633

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  17. ItemSubTitle (Series) field on EditEADRequest.html contains an incorrect 'required' attribute

    The ItemSubTitle (Series) field on EditEADRequest.html contains a 'required' attribute even though that field is not intended to be required by default.

    Bug# 18920

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  18. Transaction menu button text is not fully visible on certain display sizes

    The text content of the transaction menu buttons does not fully display on small screen sizes or high zoom levels and requires horizontal scrolling to view. In some cases, horizontal scrolling is not enough to read the full button text.

    Bug# 18917

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  19. Actions dropdown options are not fully visible on certain display sizes

    The Actions dropdown options do not fully display on small screen sizes or high zoom levels and require horizontal scrolling to view.

    Bug# 18915

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  20. ReadingRoomID field label contains incorrect 'for' attribute value on ViewAppointments.html

    The ReadingRoomID field label in the ViewAppointments.html file contains an incorrect value in its 'for' attribute and is not read by screen readers.

    This value should match the 'id' value for the field ("ReadingRoomID").

    Bug# 18913

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →
← Previous 1 3 4 5

Aeon Known Issues

Categories

Feedback and Knowledge Base

(thinking…)