I´m trying to upgrade OJS 2.4.8 to 2.4.8-5 because of PHP7 Support.
.I downloaded all the 2.4.8-5 software, copied file_updates directory, back up the data base, configure the new config.inc file but when I type the URL ojs.mysite.es/install.php it appear a page full od php warnings but nothing similar like the OJS install page.
Nothing interpreted appears.
I know we sholud go to OJS 3 and I did an update months ago but our users said it was very different than the current versión and they prefer to stay in 2.4.8.
As we have to migrate to PHP7 I thought that this was the solution (2.4.8-5) but I must be doing something wrong.
I don´t know if I have to apply patches (-1, -2, -3, -4) before updating to -5 or it must work the way I’ve done.
Can anybody help me? Have you updated to this version -5 to be able to run it with PHP7?
Thanks in advance!
Cristina
After exec " php tools/upgrade.php check" in the command line, the output indicates me that the database version is older than the software, so I exec php tools/upgrade.php upgrade and it seems that I managed to upgrade the system to 2.4.8.5.
Now I have some warnings and I´m trying not to been shown into the web system.
Something like:
Deprecated : Non-static method PKPApplication::defineExposedConstant() should not be called statically in /web/sp/ojs-2.4.8-5/lib/pkp/classes/core/PKPApplication.inc.php on line 545
Deprecated : Non-static method PKPApplication::getExposedConstants() should not be called statically in /web/sp/ojs-2.4.8-5/lib/pkp/classes/core/PKPApplication.inc.php
I´ll inform if I solve that inconvenience.
Regards!
C.
I’ve tried putting different options but those two lines keep coming out.
;error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT & ~E_NOTICE
;error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT
error_reporting = E_ALL & ~E_DEPRECATED → this is the old server option (ojs 2.4.8 with php 5.3)
error_reporting = E_COMPILE_ERROR|E_RECOVERABLE_ERROR|E_ERROR|E_CORE_ERROR
Double check that the PHP interpreter in use for your webserver is connected to the php.ini which you are editing, and that the error_reporting setting is not being overriden by another ini file or PHP directive. Your system administrator or hosting provider would be able to assist in verifying that.
If you are comfortable adding a new PHP file to your system, a quick way to test this would be to add one with just the content of:
<?php phpinfo(); ?>
Visiting this php file in your webbrowser will share a large amount of (potentially sensitive) information about your PHP install. One line will describe what the error_reporting variable defaults to, and what the effective value is after all processing.
The phpinfo() confirms that the file that is being used is /etc/php.ini and that is where I am doing these tests with the different options to show the errors (error_reporting).
I will try the first option again [ error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT & ~E_NOTICE], reload apache and load ojs to see if with a new day, it works … (ha, ha).
I have done what I said above but nothing has changed.
The same two lines appear on all OJS pages, from the cover page to the detail of an article (*)
[ Deprecated : Non-static method PKPApplication::defineExposedConstant() should not be called statically in /web/sp/ojs-2.4.8-5/lib/pkp/classes/core/PKPApplication.inc.php on line 545
Deprecated : Non-static method PKPApplication::getExposedConstants() should not be called statically in /web/sp/ojs-2.4.8-5/lib/pkp/classes/core/PKPApplication.inc.php on line 513
]
I don’t know PHP but could I try to modify those two lines to avoid those messages? It is easy?
Cristina
(*) Before modifying php.ini, many warning lines appear. Now I only have two, so something has been done thanks to modifying the php.ini error_reporting but I can’t remove all warnings. It’s very strange!
I have been adding new parameters but I still see the same two warning lines
error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT & ~E_NOTICE & ~E_USER_DEPREC
ATED & ~E_WARNING & ~E_USER_WARNING & ~E_CORE_WARNING & ~E_COMPILE_WARNING
I´m lost.
I’m not sure yet whether we’ll release another OJS 2.x package – it does take time and we’re much more focused on OJS 3.x; I’d encourage you to consider upgrading rather than maintaining OJS 2.x.
Regards,
Alec Smecher
Public Knowledge Project Team