As it is a biannual journal, after some time without publishing, we gather the articles for a new volume, I click publish and the errors listed below appear.
A new volume is published, but without the authors and articles.
Server Settings:
postgresql13-server-13.4
Apache-2.4.51
php-73
Ojs-3.3.07
How could I fix this error?
Best regards,
Augusto Torres
Webserver Log:
there is no unique or exclusion constraint matching the ON CONFLICT specification in /usr/local/www/data/eprints/lib/pkp/lib/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php:115\nStack
trace:\n#0 /usr/local/www/data/eprints/lib/pkp/lib/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php(115): PDOStatement->execute(NULL)\n#1
/usr/local/www/data/eprints/lib/pkp/lib/vendor/laravel/framework/src/Illuminate/Database/Connection.php(489): Doctrine\DBAL\Driver\PDOStatement->execute()\n#2
/usr/local/www/data/eprints/lib/pkp/lib/vendor/laravel/framework/src/Illuminate/Database/Connection.php(664): Illuminate\Database\Connection->Illuminate\Database\{closure}(âinsert into "cuâŠâ,
Array)\n#3 /usr/local/www/data/eprints/lib/pkp/lib/vendor/laravel/framework/src/Illuminate/Database/Connection.php(631): Illuminate\Database\Connection->runQueryCallback(âinsert into "cuâŠâ,
Array, Object(Closure))\n#4 /usr/local/www/data/eprints/li in /usr/local/www/data/eprints/lib/pkp/lib/vendor/laravel/framework/src/Illuminate/Database/Connection.php on line 671,
referer: https://webserver.br/eprints/index.php/kant-e-prints/manageIssues
Database Server Log:
postgres[37226]: [7-1] 2021-10-14 10:18:45.656 -03 [37226] ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification
postgres[37226]: [7-2] 2021-10-14 10:18:45.656 -03 [37226] STATEMENT: insert into âcustom_issue_ordersâ (âissue_idâ, âjournal_idâ, âseqâ) values ($1, $2, $3) on
conflict (âissue_idâ, âjournal_idâ) do update set âissue_idâ = âexcludedâ.âissue_idâ, âjournal_idâ = âexcludedâ.âjournal_idâ, âseqâ = âexcludedâ.âseqâ
I found this error to be present using the full process, where part of the form entries entered by the editor are lost during the publishing process.
Unfortunately, I have not received any feedback about this error. I partially solved it using the Quick Submit plugin, where these errors do not occur.
Next February, I will have a new large volume to publish and I will have an opportunity to look further at where these errors occur in the system. I believe it happened during some version migration, where the indexes did not happen as expected.
If you have news, post it here.
Happy 2022 to you and the entire PKP.Org team!!!
Augusto Torres
Check box for Send email to all registered users, click Yes
Then it spins in the popup:
The log entries from this attempt:
Stack trace:
#0 /usr/local/hnetojs/lib/pkp/lib/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php(115): PDOStatement->execute(NULL)
#1 /usr/local/hnetojs/lib/pkp/lib/vendor/laravel/framework/src/Illuminate/Database/Connection.php(489): Doctrine\DBAL\Driver\PDOStatement->execute()
#2 /usr/local/hnetojs/lib/pkp/lib/vendor/laravel/framework/src/Illuminate/Database/Connection.php(664): Illuminate\Database\Connection->Illuminate\Database\{closure}('insert into "cu...', Array)
#3 /usr/local/hnetojs/lib/pkp/lib/vendor/laravel/framework/src/Illuminate/Database/Connection.php(631): Illuminate\Database\Connection->runQueryCallback('insert into "cu...', Array, Object(Closure))
#4 /usr/local/hnetojs/lib/pkp/lib/vendor/laravel/framework/src/Illuminate/Data in /usr/local/hnetojs/lib/pkp/lib/vendor/laravel/framework/src/Illuminate/Database/Connection.php on line 671
PHP Fatal error: Uncaught PDOException: SQLSTATE[42P10]: Invalid column reference: 7 ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification in /usr/local/hnetojs/lib/pkp/lib/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php:115
I did a test run, creating a new edit and inserting an article using Quick Submit and no failures were found. Iâm asking the editor to run the tests using the full submission process if this error persists and will post it here shortly.