[OJS 3.2.0.2] CrossRef plugin problem

  • Application Version - e.g., OJS 3.2.0.2
  • There are two problems:
    First: When I search articles to deposit DOIs using plugin search command, whatever you put into the search options I get still all possible articles.
    Second: When I try to deposit articles or save deposition XML, I get empty screen
  • Steps you took leading up to the issue
    upgrade from 3.1.2.4 to 3.2.0.1 further upgrade to 3.2.0.2 haven’t helped
  • What you tried to resolve the issue
    Tried to see PHP logs and got file attached

[Sun Apr 12 11:16:00.531897 2020] [proxy_fcgi:error] [pid 28:tid 140395509942016] [client 46.229.168.150:2760] AH01071: Got error ‘sage: PKP-Database-Logger 1586682960,4173: \n(mysqli): SELECT * FROM author_settings WHERE author_id = ‘1851’ \xc2\xa0 \n\n\nPHP message: PKP-Database-Logger 1586682960,4173: \n(mysqli): SELECT * FROM author_settings WHERE author_id = ‘1852’ \xc2\xa0 \n\n\nPHP message: PKP-Database-Logger 1586682960,4173: \n(mysqli): INSERT INTO controlled_vocabs\n\t\t\t\t(symbolic, assoc_type, assoc_id)\n\t\t\t\tVALUES\n\t\t\t\t(‘submissionKeyword’, 1048588, 395) \xc2\xa0 \n\n\nPHP message: PKP-Database-Logger 1586682960,4173: Query: INSERT INTO controlled_vocabs\n\t\t\t\t(symbolic, assoc_type, assoc_id)\n\t\t\t\tVALUES\n\t\t\t\t(‘submission
Keyword’, 1048588, 395) failed. Duplicate entry ‘submissionKeyword-1048588-395’ for key ‘controlled_vocab_symbolic’\nPHP message: PKP-Database-Logger 1586682960,4173: 1062: Duplicate entry ‘submissionKeyword-1048588-395’ for key ‘controlled_vocab_symbolic’\n’

Hi @TruePepe,

It looks like you have debug enabled in your config.inc.php, which is flooding your log file with SQL queries. Disable that option, retry the process that causes the error, and check your error log again.

Regards,
Alec Smecher
Public Knowledge Project Team

Thank you for the fast answer,
Looks you are right, now i have no relevant errors in log, however both problems are still here
Keep healthy
Pawel

One more problem, after upgrade to 3.2.0.2 no page loads if you are not logged in
Paweł

No, I do not. Rollback from 3.2.0.2 to 3.2.0.1 solved the problem of unregistered access to journal.
Paweł