Issues with Fresh Installation of CollectiveAccess 2.0

spellboundsama

Hello all and happy new year!

I am testing a fresh installation of CollectiveAccess 2.0 on a new Ubuntu 24.04 LTS system and I am running into some issues I did not have with the previous release on the same operating system. Here are the steps I have taken so far:

sudo apt update
Install and enable Apache2
Install PHP 8.4 and its necessary extensions
Edit /etc/php/8.4/apache2/php.ini to increase memory_limit, upload_max_size, and post_max_size
Install, enable, and start MySQL server
sudo apt install -y ghostscript libgraphicsmagick1-dev graphicsmagick php8.4-gmagick libpoppler-dev poppler-utils dcraw redis-server ffmpeg libimage-exiftool-perl libreoffice mediainfo
Install git
Clone providence.git into /var/www/html/ca
Copy ca/setup.php-dist to ca/setup.php
Clone pawtucket2.git into /var/www/html/ca/pawtucket
Copy ca/pawtucket/setup.php-dist to ca/pawtucket/setup.php
Create symlink for ca/media in ca/pawtucket
sudo chown -R www-data /var/www/html/ca && sudo chmod -R 755 /var/www/html/ca
Create database, user, and grant privileges to the user in MySQL
Edit ca/setup.php and ca/pawtucket/setup.php to reflect MySQL database configuration
Start Apache2

After these steps, when I navigate to localhost/ca in my browser, I receive the error "Your installation is missing required vendor libraries. This is normal if you have just installed from a Git branch." This error also appears on the Pawtucket landing page. Fortunately I was able to click the link to auto install the vendors. However, since I cloned CollectiveAccess 2.0 from main, I figured I should flag this as an issue to be resolved.

So far, after installing my chosen profile (DublinCore 2018), I have noticed that neither Library of Congress Subject Headings, nor Media uploads work:

In the previous release of CollectiveAccess, I would type in a key word for the subject heading, and options would load after a second or two. In 2.0 that does not happen. If I type in a key word and save, the page refreshes with no change reflected. Similarly with media uploads, the images don't appear to be selected for uploading, and no change is reflected if I select one and save.

I haven't added more than a couple of objects so far so I will report more issues as I discover them. Thank you for any help in advance.

seth

Did you pull this code from Github master? If so it's normal that the vendor libraries are not included. The releases on GitHub available for download do include the vendor libraries; we have some GitHub Actions automation to do this as part of the release packaging process.

Not sure why media uploads do not work – they were definitely tested and do work on our test systems, including on PHP 8.4. I do see a problem with LCSH on PHP 8.4, which we've missed. We will resolve this and push a 2.0.1 release shortly.

spellboundsama

seth Okay yes it is from the master. I just never got that error using git clone https://github.com/collectiveaccess/providence.git /var/www/html/ca when 1.7.17 was the master so I thought it might be worth mentioning. I'll poke around again and see if I can figure out why my media uploads aren't working. Thanks for looking into the LCSH issue!

Update: Computer restart fixed the media uploads

seth

There's a new 2.0.1 release that addresses the broken LCSH lookups.

spellboundsama

seth Perfect, thank you!! I just reinstalled with PHP 8.4 and can confirm that issue is resolved.

I am now having issues saving relationships in the Collection editor. When I add related objects to a collection and save, the page goes blank (white with no error messages). When I refresh the page, it remains blank. When I reload Providence and navigate back to that collection's Relationships screen, the relationships are not there, so they don't appear to be saving.

Edit: I also tried adding a relationship to the collection from the Object editor, but it does the same thing with the page going blank and the relationship not being saved. I have been able to add relationships between events/occurrences x collections, and entities x collections so far, so at the moment the issue seems to just be between objects x collections.

seth

https://github.com/collectiveaccess/providence/releases

monica

spellboundsama try turning on stack trace in setup.php so you can see the error instead of a blank screen. Or look in the log file inside app/log

spellboundsama

I've added Related Object Representations to the collection, entity, and event editor UIs and noticed that they don't work the same as the Media representations do in the standard Object editor: There is no way to set the Representation identifier or Access for the media until after it is saved. Even then, it's only by going into the "Full record" for it, as "Edit" does not display those fields

monica

spellboundsama you need to list which object representation fields should be editable in the UI settings of that bundle. https://manual.collectiveaccess.org/providence/user/reference/settings/userInterfaceSettings.html
If you copy the setting from the object UI then you’ll have it looking the same.

spellboundsama

When creating galleries in Providence > Manage > My sets > Create public presentation with objects: The dropdown when searching for objects to add displays img src html tags rather than the object names

monica

spellboundsama a screen shot might help here

spellboundsama

monica Stack trace is on, but the screen is still blank. App log displays the following warnings:
2025-01-04 13:50:53 - WARN --> Undefined variable $i [/var/www/html/ca/app/lib/Plugins/SearchEngine/SqlSearch2.php:613] 2025-01-04 13:51:12 - WARN --> Undefined variable $v [/var/www/html/ca/app/lib/IDNumbering/MultipartIDNumber.php:241] 2025-01-04 13:51:12 - WARN --> Undefined variable $v [/var/www/html/ca/app/lib/IDNumbering/MultipartIDNumber.php:242]

spellboundsama

monica

seth

spellboundsama Make sure display_errors is turned on in your system's php.ini file. Or put this code in your setup.php file:

ini_set('display_errors', 'On');

My first guess would be that you're hitting a memory limit. PHP sets a cap on how much memory a request can consume, and if the cap is exceeded the process is killed. We can't catch that error - things just stop.

You might also want to try setting the php.ini memory_limit setting high and see if that helps. This can be done in php.ini or by adding this line to your setup.php:

ini_set('memory_limit', '384m');

384m is a good number to try. Unless you're uploading very very large images that is a limit that you'll never hit.

spellboundsama

seth I had adjusted the original memory limit from 128M to 256M as suggested by this documentation, and adjusted it again now to 384M.

Turned on display errors and restarted apache2. Saving object relationships to collections results in this error message:

Fatal error: Uncaught Error: Call to a member function tableNum() on string in /var/www/html/ca/app/models/ca_acl.php:1003 Stack trace: #0 /var/www/html/ca/app/lib/BaseRelationshipModel.php(63): ca_acl::applyACLInheritanceToRelatedRowFromRow() #1 /var/www/html/ca/app/lib/BaseModel.php(9587): BaseRelationshipModel->insert() #2 /var/www/html/ca/app/lib/BundlableLabelableBaseModelWithAttributes.php(8398): BaseModel->addRelationship() #3 /var/www/html/ca/app/lib/BundlableLabelableBaseModelWithAttributes.php(6168): BundlableLabelableBaseModelWithAttributes->addRelationship() #4 /var/www/html/ca/app/lib/BundlableLabelableBaseModelWithAttributes.php(4989): BundlableLabelableBaseModelWithAttributes->_processRelated() #5 /var/www/html/ca/app/lib/BaseEditorController.php(339): BundlableLabelableBaseModelWithAttributes->saveBundlesForScreen() #6 /var/www/html/ca/app/lib/Controller/RequestDispatcher.php(289): BaseEditorController->Save() #7 /var/www/html/ca/app/lib/Controller/AppController.php(108): RequestDispatcher->dispatch() #8 /var/www/html/ca/index.php(137): AppController->dispatch() #9 {main} thrown in /var/www/html/ca/app/models/ca_acl.php on line 1003

seth

Hmm, that's interesting. Will investigate. What profile are you using again?

spellboundsama

seth I'm using dublincore_qualif_2018.xml. Thanks!

seth

Hi. I see the problem. The fix will be in 2.0.2 soon.

seth

2.0.2 is up with a fix for this.