OJS Future Issues error

After Update to OJS 3.2.0.2 yesterday we still see that the next Issue will have 7 publications
image
, but the page ist empty and we see the following error in the logfile:

[Tue Apr 14 11:48:51.439563 2020] [proxy_fcgi:error] [pid 1928:tid 140078009546496] [client 216.244.66.200:49000] AH01071: Got error ‘PHP message: PHP Fatal error: Uncaught Error: Call to a member function getPublished() on null in /srv/ejournal/classes/search/ArticleSearch.inc.php:278\nStack trace:\n#0 /srv/ejournal/plugins/generic/recommendByAuthor/RecommendByAuthorPlugin.inc.php(137): ArticleSearch->formatResults(Array)\n#1 /srv/ejournal/lib/pkp/classes/plugins/HookRegistry.inc.php(107): RecommendByAuthorPlugin->callbackTemplateArticlePageFooter(‘Templates::Arti…’, Array)\n#2 /srv/ejournal/lib/pkp/classes/template/PKPTemplateManager.inc.php(1237): HookRegistry::call(‘Templates::Arti…’, Array)\n#3 /srv/ejournal/cache/t_compile/a4fc84a2d9d2a85c011fcc528f09577e88e2fcff^1c372c95cd85572e0fbc9a53d0323a0b229cfc78_0.app.frontendpagesarticle.tpl.php(43): PKPTemplateManager->smartyCallHook(Array, Object(Smarty_Internal_Template))\n#4 /srv/ejournal/lib/pkp/lib/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_5e94b4004e8515_02893876(Object(Smarty_Internal_Template))\n#5 /srv/ejournal/lib/pkp/lib/vendor/smarty/sm…\n’

Any idea what we can do?

Hi @gstachl,

See this thread: Error: the article display is different from the others - #6 by UBWolf

Regards,
Alec Smecher
Public Knowledge Project Team

Plugin ist deactivated, error is still there:
(Uncaught Error: Call to a member function getPublished() on null )

image

image

image

Hi @gstachl,

After disabling the plugins, does your error message (in the log) still refer to RecommendByAuthorPlugin?

Regards,
Alec Smecher
Public Knowledge Project Team

You are right. After restarting php7.2-fpm the error changed to:

[Tue Apr 14 19:15:39.889165 2020] [proxy_fcgi:error] [pid 1963:tid 140374924273408] [client 80.110.87.192:22005] AH01071: Got error ‘PHP message: PHP Warning: in_array() expects parameter 2 to be array, null given in /srv/ejournal/lib/pkp/pages/workflow/PKPWorkflowHandler.inc.php on line 373\n’, referer: http://journal.ph-noe.ac.at/index.php/resource/submissions

Any hints?
Regards
Gerald Stachl

Hi @gstachl,

OK, that’s now a different problem. That warning is actually cosmetic, I think, and can be ignored. Double-check that the site is still behaving the same way (e.g. the future issues list), and double-check the PHP error log to see if anything else interesting appears there when you encounter the “problem” page.

Regards,
Alec Smecher
Public Knowledge Project Team

OK. We didn’t see any errors, but the future issue list is still empty. When we tried to publish the issue (which should happen tomorrow) it generates a empty list.

So for the moment we rolled back to 3.1.1.4 (and php5.6) - Everything works as expected. Maybe we will try the update again after the publication of the next issue.

Regards
Gerald Stachl

We are facing a similar error, when updating the OJS from version 3.1.1.4 to 3.2.0.3, in the PHP log, we only have these entries:
Undefined offset: 110 in /ojs/controllers/grid/toc/TocGridHandler.inc.php on line 138
Undefined offset: 14 in /ojs/controllers/grid/toc/TocGridHandler.inc.php on line 138
Undefined offset: 110 in /ojs/controllers/grid/toc/TocGridHandler.inc.php on line 138
Undefined offset: 14 in /ojs/controllers/grid/toc/TocGridHandler.inc.php on line 138

But in future issues the articles do not appear. As initially described by @gstachl

Regards,
William

Same situation. We did an upgrade to 3.1.2.4 (and php 7.3) last week and it works (future issues are working).
Today i tried an upgrade to 3.2.0.3 and we still have the same problem (future issues - the articles do not appear) - So we rolled back to 3.1.2.4
Regards
Gerald

We also went back to version 3.1.1.4. We tested with PHP 7.2, 7.3 and 7.4, the problem remaining. We are trying to identify the possible SQL queries that have a problem (they are not returning data), as there were changes in the structure of the database tables in this new version.
Regards,
William

Hi all,

The processes of flagging an article for publication, and designating it against a particular issue, have been separated starting in OJS 3.2.0. I suspect you might be encountering this. I’d suggest reviewing the submissions you intend to publish in the issue, and make sure they’re both marked as published (this is probably not the case yet) and designated against the particular issue (this should already be the case).

Regards,
Alec Smecher
Public Knowledge Project Team

Thanks for the hint - That solved the problem.

1 Like

@asmecher,
We tested as indicated and solved our case too. Thanks.

1 Like

Hi all,

Happy to hear it!

Regards,
Alec Smecher
Public Knowledge Project Team