Error 500 on OAI List Records Request

piotreba · July 26, 2023, 10:08am

Hello,

I am receiving HTTP ERROR 500 upon requesting OAI list records on OAI 2.0 Request Results page. Other options, i.e., Identify | ListSets | ListMetadataFormats | ListIdentifiers show up.

Related error log:
PHP Fatal error: Uncaught TypeError: strip_tags(): Argument #1 ($string) must be of type string, array given in /plugins/metadata/dc11/filter/Dc11SchemaArticleAdapter.inc.php:188\nStack trace:\n#0 /plugins/metadata/dc11/filter/Dc11SchemaArticleAdapter.inc.php(188): strip_tags(Array)\n#1 /lib/pkp/classes/metadata/MetadataDataObjectAdapter.inc.php(266): Dc11SchemaArticleAdapter->extractMetadataFromDataObject(Object(Submission))\n#2 /lib/pkp/classes/filter/Filter.inc.php(449): MetadataDataObjectAdapter->process(Object(Submission))\n#3 /lib/pkp/classes/core/DataObject.inc.php(460): Filter->execute(Object(Submission))\n#4 /lib/pkp/plugins/oaiMetadataFormats/dc/PKPOAIMetadataFormat_DC.inc.php(22): DataObject->extractMetadata(Object(Dc11Sc…', referer:

I am using OJS 3.3.0.14, php 8.2.3.

Thanks.

piotreba · July 31, 2023, 3:08pm

I have further tested this error and switching from php 8.2 to 7.4 helped, the ListRecords type of request shows the items.

KBodarwe · August 1, 2023, 8:52am

Is there another solution apart from downgrading PHP?

I have the same problem after upgrading my server.

piotreba · August 1, 2023, 9:54am

I haven’t been investigating it extensively, but apart from php version I noticed that when I downgraded php the OPcache was causing many problems with proper OJS operation (e.g., plugin settings couldn’t be saved). On the other hand, with php 8.2 (and OPcache enabled or disabled) I couldn’t open settings for many plugins (json error popped up) and had the OAI issue mentioned above, this is why I stayed with lower php for now. So maybe try disabling/enabling OPcache on your server and test on OJS.

asmecher · August 2, 2023, 7:50pm

Hi all,

For cases where you see the following message in your log:

PHP Fatal error: Uncaught TypeError: strip_tags(): Argument #1 ($string) must be of type string, array given in /plugins/metadata/dc11/filter/Dc11SchemaArticleAdapter.inc.php:188

You can patch your installation (or upgrade to 3.3.0-16 or 3.4.0-2 or newer, when those are released) with the patches listed on this issue:

github.com/pkp/pkp-lib

dc:languages OAI data not properly sourced from submission language metadata

opened 07:27PM - 02 Aug 23 UTC

closed 07:49PM - 02 Aug 23 UTC

asmecher

**Describe the bug** The OAI `dc:language` element currently draws from two sou…rces: 1. Galley locales (one `dc:language` element for each, using 3-letter language codes) 2. The submission language metadata form field (multilingual, free-form tag style) The first form is working, but the second is not. Users report PHP errors with recent PHP versions (3.3.0-15 and similar OJS versions): ``` PHP Fatal error: Uncaught TypeError: strip_tags(): Argument #1 ($string) must be of type string, array given in .../plugins/metadata/dc11/filter/Dc11SchemaArticleAdapter.inc.php:188 ``` This is happening because recent PHP versions are strict about input data types for some built-in functions, where previously they didn't care as much. The `addStatement` function is being called as if the language field was not a multilingual field -- but it is. Whether this field should be multilingual and support arbitrary input is dealt with in https://github.com/pkp/pkp-lib/issues/5000. This issue will just treat the fatal error. **To Reproduce** Steps to reproduce the behavior: 1. Enable submission language metadata field in workflow settings 2. Enter a value (or values) in the language field for an article 3. Publish the submission 4. View the submission in the OAI-PMH interface On newer PHPs, a fatal error will appear in the logs. On older PHPs, the `dc:language` metadata will not appear as expected. **What application are you using?** OJS, OMP or OPS version 3.3.0-x

Regards,
Alec Smecher
Public Knowledge Project Team

asmecher · August 14, 2023, 3:00pm

This topic was automatically closed after 11 days. New replies are no longer allowed.