Hello everyone. When I login and resend to dashboard, or if I go to submissions or archives, from landing page, I get error 500. In the error log appears:
[26-Jul-2023 00:57:53 UTC] PHP Parse error: syntax error, unexpected ‘}’, expecting ‘;’ in /home/…/public_html/revistasojs/lib/pkp/lib/vendor/illuminate/support/Str.php on line 682
[26-Jul-2023 00:57:55 UTC] PHP Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; ADODB_Cache_File has a deprecated constructor in /home/…/public_html/revistasojs/lib/pkp/lib/adodb/adodb.inc.php on line 263
[26-Jul-2023 00:57:55 UTC] PHP Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; ADOConnection has a deprecated constructor in /home/…/public_html/revistasojs/lib/pkp/lib/adodb/adodb.inc.php on line 359
[26-Jul-2023 00:57:55 UTC] PHP Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; ADORecordSet has a deprecated constructor in /home/…/public_html/revistasojs/lib/pkp/lib/adodb/adodb.inc.php on line 2921
[26-Jul-2023 00:57:55 UTC] PHP Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; ADORecordSet_array has a deprecated constructor in /home/…/public_html/revistasojs/lib/pkp/lib/adodb/adodb.inc.php on line 3939
[26-Jul-2023 00:57:55 UTC] PHP Warning: Declaration of CustomBlockPlugin::getBlockContext() should be compatible with BlockPlugin::getBlockContext($contextId = NULL) in /home/…/public_html/revistasojs/plugins/generic/customBlockManager/CustomBlockPlugin.inc.php on line 134
We are using OJS 3.1
Plataforma SO Linux
Versión PHP 7.1.33
Versión Apache Apache
Driver de la base de datos mysqli
Versión del servidor de bases de datos 5.6.51
I found PHP Parse error: syntax error, unexpected '?' in /lib/pkp/lib/vendor/illuminate/support/Str.php on line 681 and upgrade PHP version up to 7.1.33, but it did not work.
(I know the OJS version it’s old, we are planning an update in the next months, but at this moment we need to publish an issue and we get this error).
Thank you in advanced
J.-