Home → Troubleshooting in Evergreen → Known Issues → Known Issues with Evergreen 3.1
1.1. Known Issues with Evergreen 3.1
Below is a list of known issues with Evergreen 3.1. These are generally issues that are being addressed in the continued development of Evergreen. If there are bugs associated with the issue, you can learn more information about the bug and expected fix timeline by following the bug link to Launchpad. Add heat to the bugs you would like to see fixed quickly. Just create an Ubuntu account (if you don't have one already), click on the little yellow circle,
and choose "Yes, it affects me".
You may also be interested Sitka's Known Issues page at: https://bc.libraries.coop/support/sitka/evergreen-upgrade/
Web Client Issues
Resolving Firewall Issues Which Caused the "White Screen of Death"
A library system reported issues accessing the 3.1 test environment, using any workstation or device connected to their internet.
This appeared to be the known "White Screen of Death" where the top green bar shows, but the screen below it was blank. Our first step in troubleshooting was to work through some documentation created by Mobius and Geiorgia Pines on how to address the issue.
http://libraries.missourievergreen.org/content/white-screen-death-hatchchrome
https://pines.georgialibraries.org/dokuwiki/doku.php?id=admin:workstations:troubleshooting
We learned that an older version of Internet Explorer or Microsoft Edge were the only web browsers that would sometimes allow brief access to the 3.1 test environment. (Chrome is the recommended browser.)
We confirmed that both Firefox and Chrome were updated and using the most recent versions. We confirmed that Hatch was installed and enabled. We confirmed that the Java Runtime Environment was up to date.
We went through the steps in Georgia Pines documentations and cleared the cache and cookies, refreshing the screens (Ctrl + Shift + R) and restarting web browsers. Still no success.
Next, we opened the Chrome browser console (F12) to see if we could find any error messages that would point us in the right direction of the issue. We saw several error messages about access to next.nccardinal.org:7682 (which indicates port 7682) After looking at the firewall configuration we were able to conclude that although port 7682 had been opened on their firewall, the Intrusion Protection System thought that the traffic on port 7682 was a security threat. The Library System was able to determine that the issues was tied to Application Control in the Sonicwall, specifically under the Proxy Access category Encrypted Key Exchange. Once they were able to point the category to exclude the Content Filter Allowed Domains list, the issue was resolved.
Try doing a hard refresh by clicking on the F12 button which brings up developer tools on the right side of the screen (ignore that). Right click on the refresh button next to the little home icon on the upper left of the browser window and select Empty Cache and Hard Reload.
Archived Penalties/Messages Does Not Respect Date Range
https://bugs.launchpad.net/evergreen/+bug/1775940
Some Columns Are Not Sortable in the Web Client
https://bugs.launchpad.net/evergreen/+bug/1437104
Keyboard shortcuts work differently depending on which screen - OPAC or staff client side -
Listing of Family Patron Groups
https://bugs.launchpad.net/evergreen/+bug/1642036
The listing of family patron groups requires a screen refresh to populate. A line item has to be checked in order to see any Action menu options. The Balance Owed column does not have the expected dollar sign.
Merging Patrons in Collections
https://bugs.launchpad.net/evergreen/+bug/1810854
Cannot merge two patron accounts (assigned to the same person at the same library system) when one of the accounts is in collections.
Printing the Pull List
https://bugs.launchpad.net/evergreen/+bug/1749502
Configurations made to columns within the Pull List are not reflected on the printed Pull List when using the "Print Full List" option located in the top left corner of the Holds Pull screen. To appropriately print the Pull List displaying all configurations, you must use the "Print Full Grid" found after selecting the drop down arrow in the top right corner of the Holds Pull List screen. However, the Print Full Grid does not respect the order selections made in the Local Administration>Copy Location Order list. Recommend printing the Pull List from the XUL staff client to get full functionality.
Editing Call Numbers from Item Status (Edit Volume Screen is blocked out)
https://bugs.launchpad.net/evergreen/+bug/1795478
https://bugs.launchpad.net/evergreen/+bug/1746536
When attempting to edit call numbers using the item attribute area in the XUL client or in the volumes area of the web client, the actual edit volume screen does not display.
Identifying Library Branch Locations for Holds and Transits Using 3.1 Web Client
To identify your library, register your workstation by selecting your location from the drop down. For example, the image below displays a workstation that is registered for "Perry_Main"
Selecting and Sorting the Holds Shelf Information Has Limitations
https://bugs.launchpad.net/evergreen/+bug/1712854
Columns found in the Holds Shelf list of 3.1 are not sortable or quickly resized. Also, popular columns used in 2.12, such as "Cancel Cause" or "Circulating Library" are not available within 3.1. If printing, you can export an Excel spreadsheet to sort alphabetically by patron name or use the XUL staff client for full functionality until the bug is fixed.
Parent/Guardian Field Has Been Renamed on Patron Registration Form
https://bugs.launchpad.net/evergreen/+bug/1762480
The Parent/Guardian field found on the Patron Registration form within 2.12 is not present in the 3.1 web client. The field has been renamed to "Secondary Identification" and after testing, seems to operate the same as Parent/Guardian in 2.12
Clearing Cache Also Clears Workstation Information and Column Configuration
Clearing cache to resolve certain issues in the 3.1 web client, such as the "White Screen of Death", also clears registered workstations and returns column configurations to original settings.
Labels For Several Functions Have Changed
The former "Actions for this record" label for the dropdown menu has been shortened to "Actions". The word "attributes" is no longer used for editing the item record, however you can select Edit>Items from the Actions dropdown menu. If you are used to editing multiple items using the "Manage Copy Bucket" option in 2.12, now by clicking on Cataloging>Copy Buckets, you will be directed to the copy bucket "manager" screen, although the word "manager" is no longer used.
Copy Alerts Transferred to Web Client and No Longer in XUL Staff Client
In 3.1, the code for copy alerts was completely revamped. As part of our upgrade process to 3.1.6, the existing alert messages were converted from the old code in 2.12 to the Webby code in 3.1, creating these "new" alert messages in the web client. So, the existing alerts that were in 2.12 at the time of the upgrade are now visible and editable only in the web client. MOBIUS has reported that 438,000 alerts were converted as both checkin and checkout messages.
This is the wishlist "bug" for the new feature: https://bugs.launchpad.net/evergreen/+bug/1676608
These are the permissions that Circulators, Circ Supers, Catalogers, and Cat Supers now have:
CREATE_COPY_ALERT – Consortium
VIEW_COPY_ALERT – Consortium
UPDATE_COPY_ALERT – Consortium
DELETE_COPY_ALERT – System (I found a bug reported for 3.0, so we may need to adjust this to Consortium after testing: https://bugs.launchpad.net/evergreen/+bug/1783421)
Copy Alert Types and Copy Alert Suppression are under Local Admin in the web client, but not in the staff client, so only option is to administer from the web client. These permissions are granted to Local Admin & System Admin at System level:
ADMIN_COPY_ALERT_TYPE
CREATE_COPY_ALERT_TYPE
UPDATE_COPY_ALERT_TYPE
DELETE_COPY_ALERT_TYPE
ADMIN_COPY_ALERT_SUPPRESS
CREATE_COPY_ALERT_SUPPRESS
UPDATE_COPY_ALERT_SUPPRESS
DELETE_COPY_ALERT_SUPPRESS
ADMIN_COPY_ALERT
We can adjust these as needed, if we find that they are not working as anticipated in all use cases.
When editing a copy, you should see the Manage button in the Edit Items interface.
You can also see the Manage button for copy alerts in the Item Status screen.
https://evergreen-ils.org/documentation/release/RELEASE_NOTES_3_1.html
It appears that the documentation team has not caught up with this feature, but Equinox has posted some information here:
http://esilibrary.com/copy-alerts/#sthash.u4BCxsUg.dpbs
Limited/Incorrect MARC Information Display in Catalog Search Results
We have learned that the new code in 3.1 that created search highlighting seems to be interfering with the expected display of the MARC information in the catalog search results in the web client. There are several bugs reporting this issue with regard to subject headings:
https://bugs.launchpad.net/evergreen/+bug/1770454
https://bugs.launchpad.net/evergreen/+bug/1791662
But, these may not capture the full picture. Thanks to several intrepid catalogers who have reported these issues.
Special thanks to Melisa Gomb from Henderson for providing this list of issues with screenshots in the attached Search Results pdf:
- 6XX Subject heading tags do not break into their separate subfields in the OPAC view, therefore clicking on one only searches the narrowest term.
- Series information from the 8XXs field disappears, showing only the 490 field’s information. The 8XX’s field is the more important of the two as it is an authorized heading.
- The Physical Description 300 tag changes. The cataloger view displays correctly but the OPAC view breaks into 2+ lines and also adds additional unneeded information. We have determined it duplicates the 245 subfield h General Material Designator when present, but we have not determined where it is getting the additional information. (Possibly the 007, 008, or one of the 3XXs?)
- The 520 Summary tag loses its subfield c Assigning Source.
- Multiple fields are being repeated in several different places.
- 526 Study Program Information Note is repeated under General Note
- 546 Language Note is repeated under General Note
-
511 Participant or Performer Note is repeated below the 245 Title/Author and 700 Added Authors, and it is turned into one search string hyperlink if selected. This appears in both views.
-
The 245 Title field’s subfields are reorganized in search results.
-
The 505 Formatted Contents Notes are not displaying when there is more than one entry in the MARC.
-
Periodically the 600s are being alphabetized.
We are discussing options that we might be able to employ as a consortium to mitigate the situation until bug fixes are implemented, but it is unlikely be a quick or easy solution.
Receiving "Blank Screen" When Using Catalog Searching Features
https://bugs.launchpad.net/evergreen/+bug/1797923
In the Web Client, when using both the “Search Catalog” located on the Home Screen and the “Search the Catalog” feature found in the “Search” tab located in the top green menu bar, staff receive a blank screen, with no error message. Staff have also reported that the Home screen will sometimes reload, instead of providing search results. We have had reports that refreshing the screen in the browser can sometimes resolve the problem.
Receiving Green Screen When Attempting To Place Holds
https://bugs.launchpad.net/evergreen/+bug/1737808
Staff receive a “green screen”( large green box) when placing holds using the web client
Inconsistent Search Results for E-books
https://bugs.launchpad.net.evergreen/+bug/1798910
Staff have reported receiving incorrect search results when using catalog search features in both the XUL and web clients of 3.1.6. When using the same isbn for catalog searches, results should be the same. Instead, each search provides results that differ dramatically. For example, staff have reported receiving different results when using the same isbn to conduct a search limited to a specific library systems, a search including the entire NC Cardinal consortium, and when conducting searches using z39.50.
Updating User Permission Groups
https://bugs.launchpad.net/evergreen/+bug/979922
When changing a new user account to a full privileged account using the 3.1.6 web client, if the patron has two items checked out at the time of the change, staff will receive the “Max Threshold” penalty message when attempting to check out more books to the patron’ account. This message remains even after manually refreshing your web browser or logging out and logging back into the web client.
To resolve this issue, staff must manually remove the max threshold penalty message by opening the patron account and clicking on “message.” The applied penalty should display there, giving staff the option to remove it.
Receiving "Unhandled Error" Update Alert in XUL Staff Client
Cataloging Staff have reported receiving an update alert entitled “Unhandled Error” when attempting to update MARC records using the XUL client since migrating to 3.1.
This message has been identified by MOBIUS as a indicator to when invalid changes have been made to a MARC record. This message is cryptic and does not identify which field(s) are in error.
To identify invalid fields, one method of troubleshooting would be to open the record and make no changes, and save it. Then make one small change and save the record again. Continue making small changes and saving after each change until all needed changes have been made. If you receive an error message while attempting to save one of the changes, then the issue is the change that you made directly before you saved. Evaluate your changes and see if you can correct any ill formatted MARC.
Remaining Renewals Decrease When Manual Refresh Is Needed to Complete a Renewal Transaction
https://bugs.launchpad.net/evergreen/+bug/1803753
When a renewal transaction requires the screen to be refreshed in the 3.1.6 web client, it decreases the number of remaining renewals inaccurately. For Example, a patron with 2 renewals checked out an item with a original due date of 10/15 . On 10/27, staff renewed the item for the patron, which should have left the patron with 1 renewal remaining. However, while attempting to renew the item, the screen freezes and a refresh is needed to continue the renewal action. After refreshing the screen, staff are able to continue with the renewal process but notice that another renewal was used while the screen refreshed, leaving the patron with 0 renewal, instead of the expected 1 renewal.
Unable To Hide the “Credits Available” Field in the 3.1.6 Web Client
https://bugs.launchpad.net/evergreen/+bug/1803765
When using the 3.1.6 web client, staff are unable to hide the “credits available” field found within patron accounts, under the “Bill” tab. In the 2.12 staff client, staff had the option of hiding the “credits available” field if the credits functionality was not utilized by the library. Is it possible to add the feature of “ hiding” the Credits Available field to the 3.1.6 web client for those libraries that do not offer patron credits?
A Long List of Billing Ids Display in Void Billing Confirmation Message
https://bugs.launchpad.net/evergreen/+bug/1698865
When voiding a bill, the confirmation message displays the entire list of billing id numbers for the money.billing rows in the database.
Unable to Delete Pending Patrons Using the Web Client
https://bugs.launchpad.net/evergreen/+bug/1737800
The 3.1 Web Client does not offer a manual deletion option for pending patrons. To delete pending patrons, the web client relies on the library setting — OPAC: Patron Self-Reg. Expire Interval. This setting allows each library to set the amount of time after which pending patron accounts should be deleted.
Placing Multiple Holds in My List Leads to Error
https://bugs.launchpad.net/evergreen/+bug/1687319
When placing multiple holds from “My List” using the OPAC, the hold is placed successfully, but selecting “continue” at the bottom of the screen returns a 404 Error Message.
Problems cloning & running reports in web client with templates created in XUL
Bug 1642344 documents the original issues for which a fix was released in version 3.1.6 (our version). However, these problems are still outstanding in bug 1796945.
Cloning process seems fine. Without updating anything the template can be saved.
When running reports from the cloned templates, there were errors complaining either lacking field in Group By or missing From clause.
When cloning the templates, removing then putting back the complained fields solved the issue.
It seems the issue is related to how the tables are joined. See the screenshot. Nearly all our templates starting from Item table leading to Call Number > Bib > Simple Record Exact are affected.
From Item table to Shelving Location or Copy Status tables sometimes have the issue, too.
https://bugs.launchpad.net/evergreen/+bug/1642344
https://bugs.launchpad.net/evergreen/+bug/1796945
For now, we recommend using XUL to clone and run templates originally created in XUL. We will need to evaluate the status of this bug at the time of our upgrade to a new version, as the proposed fix release is version 3.4.