Skip to content

Commit

Permalink
Update readme; bump version
Browse files Browse the repository at this point in the history
  • Loading branch information
collectiveaccess committed Nov 2, 2021
1 parent 5ac62ac commit 655fd24
Show file tree
Hide file tree
Showing 2 changed files with 10 additions and 11 deletions.
19 changes: 9 additions & 10 deletions README.md
@@ -1,4 +1,4 @@
# README: Providence version 1.7.13
# README: Providence version 1.7.14

[![Build Status](https://secure.travis-ci.org/collectiveaccess/providence.png?branch=master)](http://travis-ci.org/collectiveaccess/providence)

Expand All @@ -8,14 +8,13 @@ CollectiveAccess is a web-based suite of applications providing a framework for

CollectiveAccess is freely available under the open source GNU Public License version 3.

### About CollectiveAccess 1.7.13
### About CollectiveAccess 1.7.14

Version 1.7.13 is a maintenance release with these bug fixes and minor improvements:
* Resolve issue where when importing multiple media onto a single record via the data importer, the last imported media is tagged as primary rather than the first.
* Resolve issue where logging into accounts with numeric login names would fail
* Correct various errors in database schema that would cause errors with recent versions of MariaDB
* Bump version on selected vendor libraries due to advisories
* Improve formatting of summary displays
Version 1.7.14 is a maintenance release with these bug fixes and minor improvements:
* Add checks to prevent potential XSS and CSRF security vulnerabilities
* Handle non-standard ports when generating URL for background search indexing
* Update selected 3rd party libraries for bug fixes
* Improve script path parsing to addresses issues for systems running PHP-FPM proxies where quick search expressions containing spaces (or other URL escaped characters) will throw an invalid controller error when "full results" is selected. This is due to a bug in PHP processing of content for $_SERVER['SCRIPT_NAME'] in several PHP 7.x versions when running as PHP-FPM. See https://bugs.php.net/bug.php?id=74129.

Note that this version is not yet compatible with PHP version 8. Please use versions 7.3 or 7.4.

Expand All @@ -29,9 +28,9 @@ First make sure your server meets all of the [requirements](https://manual.colle

NOTE: The update process is relatively safe and rarely, if ever, causes data loss. That said BACKUP YOUR EXISTING DATABASE AND CONFIGURATION prior to updating. You almost certainly will not need the backup, but if you do you'll be glad it's there.

To update, decompress the CollectiveAccess Providence 1.7.13 tar.gz or zip file and replace the files in your existing installation with those in the update. Take care to preserve your media directory (`media/`), local configuration directory (`app/conf/local/`), any local print templates (`app/printTemplates/`) and your setup.php file.
To update, decompress the CollectiveAccess Providence 1.7.14 tar.gz or zip file and replace the files in your existing installation with those in the update. Take care to preserve your media directory (`media/`), local configuration directory (`app/conf/local/`), any local print templates (`app/printTemplates/`) and your setup.php file.

If you are updating from a version prior to 1.7, you must recreate your existing setup.php as the format has changed. Rename the existing setup.php to `setup.php-old` and copy the version 1.7.13 setup.php template in `setup.php-dist` to `setup.php`. Edit this file with your database login information, system name and other basic settings. You can reuse the settings in your existing setup.php file as-is. Only the format of setup.php has changed. If you are updating from version 1.7.x you do not need to change your setup.php file.
If you are updating from a version prior to 1.7, you must recreate your existing setup.php as the format has changed. Rename the existing setup.php to `setup.php-old` and copy the version 1.7.14 setup.php template in `setup.php-dist` to `setup.php`. Edit this file with your database login information, system name and other basic settings. You can reuse the settings in your existing setup.php file as-is. Only the format of setup.php has changed. If you are updating from version 1.7.x you do not need to change your setup.php file.

Once the updated files are in place navigate in your web browser to the login screen. You will see this message:

Expand Down
2 changes: 1 addition & 1 deletion app/version.php
@@ -1,6 +1,6 @@
<?php
# CollectiveAccess version number; don't change
define('__CollectiveAccess__', '1.7.13');
define('__CollectiveAccess__', '1.7.14');

# Schema revision
define('__CollectiveAccess_Schema_Rev__', 158);
Expand Down

0 comments on commit 655fd24

Please sign in to comment.