Blank/white screen after upgrade from OJS 3.1.2.4 to 3.3.0.20

After upgrading (‘successfully’) OJS from 3.1 to 3.3 I am met with a blank white ‘screen of death’ when accessing the website.

Originally the upgrade failed because of the known db-engine issue in the submissions_files table entry of the database, but after following the fix of changing the engine to InnoDB the upgrade was successful (n.b. I did perform the second attempt on the backup 3.1 database).

I performed the upgrade in Xampp 3.3 (php v. 7.2.1.16) rather than on the server, and used the web-based method (in any case, I am not familiar or comfortable with command-based work), which was fast enough.

When I turn on display errors and deprecation warning this is what is shown:

Notice: Deprecated call without request object. in C:\xampp\htdocs\HCS\public_html\ojs\lib\pkp\classes\template\PKPTemplateManager.inc.php on line 1297

Fatal error: Uncaught Error: Call to a member function getOption() on null in C:\xampp\htdocs\HCS\public_html\ojs\cache\t_compile\b9da708b775ca192cb9735589afa7e98b537357a^e64e579388e5615e11e939b12134d6ae8679eba6_0.app.frontendpagesindexJournal.tpl.php:37 Stack trace: #0 C:\xampp\htdocs\HCS\public_html\ojs\lib\pkp\lib\vendor\smarty\smarty\libs\sysplugins\smarty_template_resource_base.php(123): content_67a73e8b37caa0_87479361(Object(Smarty_Internal_Template)) #1 C:\xampp\htdocs\HCS\public_html\ojs\lib\pkp\lib\vendor\smarty\smarty\libs\sysplugins\smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode(Object(Smarty_Internal_Template)) #2 C:\xampp\htdocs\HCS\public_html\ojs\lib\pkp\lib\vendor\smarty\smarty\libs\sysplugins\smarty_internal_template.php(217): Smarty_Template_Compiled->render(Object(Smarty_Internal_Template)) #3 C:\xampp\htdocs\HCS\public_html\ojs\lib\pkp\lib\vendor\smarty\smarty\libs\sysplugins\smarty_internal_templatebase.php(238): Smarty_Internal_Template->render(false, 1) #4 in C:\xampp\htdocs\HCS\public_html\ojs\cache\t_compile\b9da708b775ca192cb9735589afa7e98b537357a^e64e579388e5615e11e939b12134d6ae8679eba6_0.app.frontendpagesindexJournal.tpl.php on line 37

One common suggestion is to clear the cache, but this make no difference.

Another thing I did was implement the change to the upgrade script file 3.2.0_preupdate_versioning_articleGalleySettings, with the following at line 18:
CREATE TABLE IF NOT EXISTS submission_galley_settings, as approved by asmecher at Upgrade OJS 3.1.2-1 to 3.2.1-4 Successfully upgraded - #11 by murilodbva

Still no joy.

Correction: I am using PHP 7.4

Hi @thilor,

See: Empty page after updating from ojs-3.3.0-14 to ojs-3.4.0-4 - #5 by asmecher

Regards,
Alec Smecher
Public Knowledge Project Team

Many thanks. I fixed the problem by manually installing the default Manuscript plugin (which our journal had been using). It was frustrating that this isn’t caught by an error handler after an upgrade; a handler might have diverted the user at least to the login screen instead (where the issue does appear to not arise) and from where the dashboard can be accessed.

1 Like

This topic was automatically closed after 9 days. New replies are no longer allowed.