Hello,
Running:
CollectiveAccess 2.0
PHP 8.3
Server: Dreamhost VPS
Linux vps32058 5.15.0-101-generic #11120.04.1-Ubuntu SMP Mon Mar 11 15:44:43 UTC 2024 x86_64
Was able to update to the new 2.0 from 1.7 without too much trouble using the "caUtils update-from-1.7" script. Seemed to work without errors.
The only big change we made was updating the app.conf to make use of the "Workflow based location tracking". Before, we were using a very primitive solution to track location of deleting the old storage location and replacing it with the current location. Not ideal, and we're thrilled that you've introduced the "Workflow based location tracking" feature.
So the problem:
The error I'm experiencing isn't for all of Providence, it's specifically the "Storage Location Editor" pages. When I try to edit a Storage Location I get the following:
"There are issues with your configuration
General installation instructions can be found here. or more specific information on detected issues review the messages below:
Could not connect to database. Check your database configuration in setup.php: 1054"
When running the "do-configuration-check" script, I got the following response:
"Errors were found:
[1] It looks like the CA_SITE_HOSTNAME setting in your setup.php may be set incorrectly. If you experience any troubles with image display try setting this to "localhost". We came up with this suggestion because this is the hostname you used to access this script. It may only be valid for you (and not for other users of the system) though (e.g. if you use 'localhost' or a feature like /etc/hosts on UNIX-based operating systems) so you have to be very careful when editing this"
I've confirmed the setup.php file is setup correctly by double-checking with dreamhost.com about the hostname address, etc. It also worked smoothly with Providence 1.7.
Ran the "reload-current-values-for-history-tracking-policies", "reload-object-current-location-dates" and the "rebuild-search-index" caUtils. Not sure if it's a different app.conf mistake or something that was introduced in the update from 1.7 to 2.0
Thanks so much for your advice/help,
-Gil