OJS3.3.0-6 Back issue operations error

[mapress888]

Please see picture:

here i use edit as an example, but all other function returns same error.

i noticed the link calling is
https://xx.com/xxx/$$$call$$$/grid/issues/back-issue-grid/edit-issue?issueId=1

which ofc returns a null value:
{“status”:false,“content”:“Invalid issue requested!”,“elementId”:“0”,“events”:null}

the issue actual id is 8125
https://xxx.com/xx/$$$call$$$/grid/issues/back-issue-grid/edit-issue?issueId=8125

this gives:

{“status”:true,“content”:"<script type=“text/javascript”>\n\t// Attach the JS file tab handler.\n\t$(function() {\n\t\t$(’#editIssueTabs’).pkpHandler(’$.pkp.controllers.TabHandler’);\n\t});\n</script>\n<div id=“editIssueTabs”>\n\t

\n\t\t
• <a href=“https://xxx.com/xx/$$$call$$$/grid/issues/back-issue-grid/issue-toc?issueId=8125”>Table of Contents</a></li>\n\t\t
• <a href=“https://xxx.com/zt/$$$call$$$/grid/issues/back-issue-grid/edit-issue-data?issueId=8125”>Issue Data</a></li>\n\t\t
• <a href=“https://xxx.com/zt/$$$call$$$/grid/issues/back-issue-grid/issue-galleys?issueId=8125”>Issue Galleys</a></li>\n\t\t\t\t\t<li id=“identifiersTab”><a href=“https://xxx.com/xx/$$$call$$$/grid/issues/back-issue-grid/identifiers?issueId=8125”>Identifiers</a></li>\n\t\t\t\t\t\t\t
• <a href=“https://xxx.com/xx/$$$call$$$/grid/issues/back-issue-grid/access?issueId=8125">Access</a></li>\n\t\t\t</ul>\n</div>\n",“elementId”:“0”,"events”:null}

  So i assume in the UI buttons the issue value did not get correctly past.

  Can anyone advise what i should modify to get it work?

  I have done two modification not sure if they are related to the current error:

  [OJS 3.2.1-4] Please split the Backend "Back issues" table to several pages (Taking half an hour to generate the whole list)

  @asmecher Currently doing test upgrade from 2.4.8 to 3.2.1-4 (3.3.0-6 direct upgrade failed) Other than upgrade issue we want to report that in back end admin panel, not like the front end archived issue list where you can split the whole list by set value in “list” like 25 or 10 per page. Backend back issue list by default loads EVERY issue! I have two large journals one with 5000+ issues published stucked forever (1+ hr past). Another one has less than 1000 took about 25 mins to load! the …

  [OJS3.3.0-6] DOI plugin is not generating DOI from %x custom pattern (URL path)

  Because back in 2.4.8 we used this field of issue and paper as “Custom DOI field” where patten was %x for the DOI plugin and crossref to deposit. Also this field by default will affect the final URL of the published issue & paper. Our format before was: xxx.1.1 In current OJS we are not allow to input this value. So I changed these files: \lib\pkp\schemas\context.json “urlPath”: { “type”: “string”, “validation”: [ “regex:/^[a-zA-Z0-9]+([\-_.][a-zA-Z0-9]+)*$/” ], “apiSummary”: true } …

[mapress888]

Current thinking is:

because of changing

protected function loadData($request, $filter) {

from return $issueDao->getPublishedIssues($journal->getId());
to return $issueDao->getPublishedIssues($journal->getId())->toArray();
}

Where the loadData returns now an array instead of ID, that is why the above grid think the issue id is 1?

What code i could change regarding this?

[ewhanson]

Hi @mapress888,

It looks like you’re right about it being related to the loadData function in BackIssueGridHandler. Later functions expect the issue ID to be included as part of an associative array.

Try changing

return $issueDao->getPublishedIssues($journal->getId())->toArray();

to

$issueDao->getPublishedIssues($journal->getId())->toAssociativeArray();

Hope that helps!

Best,

Erik
PKP Team

[mapress888]

@ewhanson it works! thank you very much. I have another problem with XML exporter, i will open a new post.