![]() #8 /lib/pkp/lib/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(386): Smarty_Internal_Template->render() #7 /lib/pkp/lib/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(217): Smarty_Template_Compiled->render(Object(Smarty_Internal_Template)) ![]() #6 /lib/pkp/lib/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode(Object(Smarty_Internal_Template)) #5 /lib/pkp/lib/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_6530dc5b06a767_04114008(Object(Smarty_Internal_Template)) #3 /lib/pkp/lib/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(384): Smarty_Template_Compiled->render(Object(Smarty_Internal_Template)) #2 /lib/pkp/lib/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode(Object(Smarty_Internal_Template)) #1 /lib/pkp/lib/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_6530dc5b01f504_33444509(Object(Smarty_Internal_Template)) ![]() ![]() I included the trace with the original unmodified plugin below: For us it is only back issues past a certain dat/year, for you, as I understood your post, it was all Turned on display errors and got this:įatal error: Uncaught Error: Call to a member function getDisplayName() on null in /lib/pkp/classes/galley/Galley.php:160įollowed by a 28 step stack trace that is mostly the same with or without the modifications to RecommendBySimilarityPlugin that you suggested to Salam above (which resultet in 29 steps). The same did not work for us.So the two errors are probably not related. I don’t get I saw you got help with your issue. Not sure if this is connected to the problem or if it is just a theme thing. Some times with padding on the left and some times with 0 padding. Maybe related and maybe not: The Archive page no longer displays the issues in lines of four (or less depending on browser width), rather a bit random. Using latest healthSciences theme (but the problem is the same in standard theme). Yet to find anything that does not work here. The upgrade from 3.3.0.9 to 3.4.0.3 finished without errors after deleting a couple of log files.Īfter the upgrade the backend seems to work as expected. Here is an example of one that works from 2020: Īnd here is one that does not from 2019: I have looked at the database and can’t see any obvious difference between an issue that does work and one that does not. The last journal, which is no longer actively published and only has issues dating back from 2016 is not accessible at all (this journal is also accessible in the dashboard and all back issues can be edited). (Original post marked for deletion because the title did not reflect the problem and can’t be edited.)įor all but one journal any issue older than 2020/2019 gives an http 500 error even though they are visible on the archive page and can be edited in the dashboard (for instance I can change the cover image and the change is reflected on the archive page). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |