The resource you are looking for doesn't exist.

[bolelligallevi]

Hi, I'm testing your datacite plugin on a OMP 3.1.2-4 and I'm receiving the "The resource you are looking for doesn't exist." error after clicking on the DOI I want to register.
I checkd prefix, datacite account infos and the submission (this one: https://libri.unimi.it/OLD/index.php/milanoup/catalog/book/487).
Any hint?
Waiting for your answer, best regards
Stefano

[withanage]

Hi Stefano,

Could you let me know the whole error message ? Does it come from the datacite API ?

[bolelligallevi]

Hi Dulip, thanks for your reply.
The error is an OJS message the system shows in top right of the beckoffice in purple background. I’ll try to send a screenshot later

[bolelligallevi]

[bolelligallevi]

I'm looking for logs, I found some serialize issues related to the plugin, I don't know if are relevant...
Best regards
Stefano

[bolelligallevi]

Hi Dulip, our IT found that there was an issue preventing the use of the proxy by the plugin and solved with a workaround. For some reason, the code dedicated to read the OMP config is not working. Please let me know if you have any suggestion n where to look to understand the issue

[withanage]

Hi @bolelligallevi
hmm, do you mean the settings for the plugin or config.inc.php ?

[bolelligallevi]

Hi @withanage,
the part of the code that didn't work for us is in the plugin file DataciteExportPlugin.inc.php, row 230-236:
if ($httpProxyHost = Config::getVar('proxy', 'http_host')) {
curl_setopt($curlCh, CURLOPT_PROXY, $httpProxyHost);
curl_setopt($curlCh, CURLOPT_PROXYPORT, Config::getVar('proxy', 'http_port', '80'));
if ($username = Config::getVar('proxy', 'username')) {
curl_setopt($curlCh, CURLOPT_PROXYUSERPWD, $username . ':' . Config::getVar('proxy', 'password'));
}
}

For some reason, this code doesn't catch our config in config.inc.php, that is:
[...]
;;;;;;;;;;;;;;;;;;
; Proxy Settings ;
;;;;;;;;;;;;;;;;;;
[proxy]
; Note that allow_url_fopen must be set to Off before these proxy settings
; will take effect.
; The HTTP proxy configuration to use
http_host = myproxy.mydomain.it
http_port = 8080
; proxy_username = username
; proxy_password = password
[...]

So, our IT commented row 230-236 and added those to force our proxy config to the plugin:
curl_setopt($curlCh, CURLOPT_PROXY, 'myproxy.mydomain.it');
curl_setopt($curlCh, CURLOPT_PROXYPORT, '8080');

Please let me know if you see the problem in rows 230-236.
Best regards
Stefano

[withanage]

I see, there was a contribution to better handle the token errors (not directly related), but Could you update now from github and let me know, if the problem still exists.

#4

[bolelligallevi]

Hi @withanage, we tried stable stable-3_1_2 and we received the same error

the same patch mentioned here worked.
best regards