Omeka-S 3.2.1 Error creation arks

Starting the creation of arks generates the following error:

2022-07-12T14:02:54+00:00 ERR (3): Exception: Noid requires the extension “Database (dbm-style) Abstraction Layer” (dba). in /applis/omekas/home/www/omeka-s/modules/Ark/vendor/daniel-km/noid4php/lib/Noid.php:303

Stack trace:

#0 /applis/omekas/home/www/omeka-s/modules/Ark/vendor/daniel-km/noid4php/lib/Noid.php(1227): Noid::init()

#1 /applis/omekas/home/www/omeka-s/modules/Ark/src/Name/Plugin/Noid.php(209): Noid::dbopen()

#2 /applis/omekas/home/www/omeka-s/modules/Ark/src/Name/Plugin/Noid.php(50): Ark\Name\Plugin\Noid->openDatabase()

#3 /applis/omekas/home/www/omeka-s/modules/Ark/src/ArkManager.php(348): Ark\Name\Plugin\Noid->create()

#4 /applis/omekas/home/www/omeka-s/modules/Ark/src/Job/CreateArks.php(48): Ark\ArkManager->createName()

#5 /applis/omekas/home/www/omeka-s/modules/Ark/src/Job/CreateArks.php(16): Ark\Job\CreateArks->processResources()

#6 /applis/omekas/home/www/omeka-s/application/src/Job/DispatchStrategy/Synchronous.php(34): Ark\Job\CreateArks->perform()

#7 /applis/omekas/home/www/omeka-s/modules/Log/src/Job/Dispatcher.php(32): Omeka\Job\DispatchStrategy\Synchronous->send()

#8 /applis/omekas/home/www/omeka-s/application/data/scripts/perform-job.php(66): Log\Job\Dispatcher->send()

#9 {main} {“userId”:2,“jobId”:246}

We are using Omeka S version 3.2.10, MySQL and the version for the module Ark is V3.5.12.3.

Does anyone have an idea ?

Thank you in advance

The problem seems to come from the PHP 8.1.8 version we just installed.

By forcing Omeka to use a version 7.2.24 for example, the problem disappears.

Maybe you just don’t have the “dba” extension on the new PHP but you do on the old one?

There are issues with PHP 8.1 and current Omeka S versions though, you’d typically see them if you have error display turned on.

Next version of the module will be able to use a standard database (sql or xml), not the old one (dba), that was used for compatibility purpose since the first version of the module.

Thanks for the information.

Does this mean that the future version of the module will continue to use a dedicated database, apart from the one used by Omeka and the other modules ?

And will the update of the module take into account the migration of the database to a SQL database?