[OJS] ORCID Profile Plugin prevents article publication

[mabere]

After successfully installing fresh ojs 3.2.0 I created future issues, I try to publish one issue but the circle icon keep loading for long time (not stop).

[Edit: One cause for this is the ORCID Profile Plugin as released with OJS 3.2.0/3.2.0-1. It still references PublishedArticleDAO, as noted here: https://github.com//issues/5572#issuecomment-604047918]

[asmecher]

Hi @mabere -- check your PHP error log for details.

[alexxxmendonca]

it must be due to the option to send a notification e-mail.

depending on the number of users you have, this might take a long time,

We've been having some big problems with that, to the point of reaching gmail's daily quota, causing all e-mails to cease sending. We are advising journals to uncheck that box before publishing an issue.

[KarwanJacksi]

Hi,
I now have the same problem, the PHP log file says
ojs2: Unrecognized DAO PublishedArticleDAO!

[asmecher]

@KarwanJacksi, I don't think this is the same issue, but turn on the show_stacktrace option in config.inc.php and try again. The error message should include more information.

[KarwanJacksi]

Hi @asmecher ,
It is already on, but does not show anything, I try to publish an issue but the circle icon keeps loading, and when I check PHP log file it gives me that..

And, I do exactly have this problem, installed a fresh copy of ojs 3.2.0.1, created an issue and wanted to publish it.

[asmecher]

@KarwanJacksi, try disabling the ORCID Profile plugin and see if that helps.

[KarwanJacksi]

OMG!
That was the problem! It is working now and the issue is published!
Many thanks @asmecher :)

[defstat]

@asmecher @NateWr

The PR ports OrcidProfile plugin to v3.2

PR
[orcidPlugin]: pkp/orcidProfile#102

[withanage]

Hi @alexxxmendonca @mabere @KarwanJacksi

This issue is fixed by the orcid plugin release v1.1.2-1 from 30.03.2020

You can update the plugin for ojs 3.2.0 in the plugin gallery

[alexxxmendonca]

Hi @withanage,

thanks!

How can I upgrade it?

[withanage]

Hi @alexxxmendonca ,
I see your version is 3.1.2, The ticket problem refers to 3.2.0+ or did you also have it in 3.1.2 ?

[alexxxmendonca]

@withanage my mistake!

Will wait for when we upgrade to 3.2.0+.

Thanks!

[defstat]

Can we close that issue?

[withanage]

I have tested it in OJS 3.2.0 and OPS 3.2.0
If there are new wishes, we can either re-open or create a new issue.

[asmecher]

Thanks, all!