Skip to content
Translate Ideas and Comments
Choose language:
There was an error during translation

Aeon Known Issues

  • Hot issues
  • Top issues
  • New issues
  • My feedback

8 results found

  1. ShowAutoRowFilter Null Reference Exception

    Invalid data row displays when "Show Auto Filter Row" option is turned on

    0 votes
  2. The Aeon installer does not support non-standard database user installations

    A default database user and password are hard-coded into the installer defaults. When the DB update scripts try to grant permissions on new or updates tables, it will always try to grant them to 'aeon'. Need a way to configure the database user/password on install if different from hard-coded 'aeon'.

    0 votes
    under review  ·  0 comments  ·  Admin Tools  ·  Admin →
  3. Password Reset link not converting when emailed from client

    The password reset email template should be hidden in client email template options.

    0 votes
  4. Routing a request to another site changes the request status to Request In Processing regardless of previous state

    When routing a request to another site (that is still visible by the existing view), the request will remain open.

    The code for barSubItemRouteToSite_ItemClicked is routing to RequestInProcessing regardless of it the originalStatusRequestProcessing variable is -1 or something else. The route to RequestInProcessing in the else (i.e. when the request is still visible) should only happen if the originalStatusRequestProcessing is not equal to -1.

    1 vote
  5. The Aeon web DLL may crash the app pool if it doesn't have permissions to the log file location.

    This was discovered in a very particular situation but is still good to account for.

    1 vote
  6. Entering <#STATUS> in Status Line crashes the Aeon Server.

    Go to Aeon Customization Manager.
    Edit the SLMainMenu customization key.
    Change the value to <#STATUS>.
    Log on to Aeon Web.

    1 vote
  7. The Aeon DLL does not URL decode POST parameter names

    n InitializePostData, the DLL loops through the name/value pairs from the request content and decodes their values. However, it does not decode the field names. This isn't often a problem, but the Georgia Tech XSLT submits field names with a + character, which are getting encoded. When the EAD Request function tries to find field names using the identifier, they don't match because the + is still encoded in the field name. (We've since updated GT's XSLT to work around this).

    1 vote
  8. 1 vote

Feedback and Knowledge Base