Release 2.3.1

From AtoM wiki

Main Page > Releases > Releases/Release announcements > Releases/Release announcements/Release 2.3.1

Release date: February 14th, 2017

Download link: atom-2.3.1.tar.gz

AtoM 2.3.1 is a bug fix release for AtoM 2.3. We've closed a number of important user-reported bug tickets in order to improve some recurring problems with the previous release - you can view more details on each ticket in our issue tracker at the following links:

Visit the Downloads page to download the most recent release, and consult the 2.3 Upgrade and Installation guides for further information. A summary the fixes included in this release can be found below.


Ubuntu 16.04 users: An important note on installation

There is a known issue, with a workaround, during the installation process for Ubuntu 16.04 with the 2.3.1 release. During AtoM install, if the admin restarts the server after installing PHP, but before running the web based AtoM setup, then when the AtoM web installer setup is run it will fail after completing the "Configuring Search" page with the error 'The "i18n" object does not exist in the current context'. The following workaround will resolve the issue:

  • Restart fpm (sudo systemctl restart php7.0-fpm <-- in the case of Ubuntu 16.04)
  • Restart the install (dump and recreate db, delete and set up the atom application folder again)
  • The install will now proceed cleanly.

If the user just tries again without restarting fpm, they will repeatedly run into the same error during install. This issue will be resolved in the 2.4 release. For more information, see the following issue ticket:

Bug fixes

  • #10256 - Treeview does not appear when using certain cultures
  • #10276 - Global setting for reference code separator affects new user slug generation
  • #10417 - sfAPCuCache is broken
  • #10418 - Header fix for ArchivesCanada theme - include Clipboard link
  • #10426 - Results pagination not working in term index pages
  • #10633 - Investigate potential Ubuntu 16.04 compatibility issues with CSV import
  • #10602 - CSV import fails when using the accessionNumber column to link new descriptions to existing accession records
  • #10675 - PDF derivatives not generating correctly on Ubuntu 16.04
  • #10716 - Acquisition date in accession record behaving oddly

For a list of all issue tickets included in the 2.3.1 release, see:


For 2.3.0 users who have encountered errors when trying to use a period or other characters as the reference code separator:

This issue has been identified in #10276. If you have tried to use a period as a reference code separator and are experiencing issues, the 2.3.1 release will include a fix for this issue going forward. To resolve the current issues in your AtoM instance, we have prepared a script that can be run from the command-line. The script is available at:

Instructions on how to run the script locally

  1. Follow the link above and download the script. Place it somewhere accessible from the root directory of your AtoM installation.
  2. From AtoM's root directory, use the tools:run command to execute the script, like so:

php symfony tools:run path/to/location/of/10276-separator-fix.php

The script will replace any periods used with the default dash separator in the database, which should resolve page load errors.