Update to 2.4.7 error with PLN Pluging

JoannaB · October 15, 2015, 6:10pm

Hi,
Today I made the upgrade to version 2.4.7, all is normal but when I run de command.
sudo php upgrade.php upgrade for update the database i have problems.

Error mesage:
“You are trying to downgrade the product “pln” from version [1.0.1.0] to version [1.0.0.0]. Downgrades are not supported.ojs2: You are trying to downgrade the product “pln” from version [1.0.1.0] to version [1.0.0.0]. Downgrades are not supported.”

ctgraham · October 15, 2015, 8:24pm

The PLN plugin version that ships with 2.4.7 should be 1.0.2.0:

github.com

pkp/ojs/blob/ojs-stable-2_4_7/plugins/generic/pln/version.xml#L16


  *
  * Copyright (c) 2013-2015 Simon Fraser University Library
  * Copyright (c) 2003-2015 John Willinsky
  * Distributed under the GNU GPL v3. For full terms see the file docs/COPYING.
  *
  * Plugin version information.
  -->
<version>
	<application>pln</application>
	<type>plugins.generic</type>
	<release>1.0.2.0</release>
	<date>2015-07-13</date>
	<lazy-load>1</lazy-load>
	<sitewide>0</sitewide>
	<class>PLNPlugin</class>
</version>

What method did you use to upgrade? Are you sure it was successful?

As an aside, sudo for the upgrade script is probably unnecessary/unwanted unless combined with su to change to your web user, as in:
sudo su apache -s /bin/bash -c 'php tools/upgrade.php upgrade'

JoannaB · October 15, 2015, 10:38pm

Hi, first I upgrade ojs run this commmand
→ sudo patch –p1 < ojs-2.4.6-to-2.4.7 patch
after in the folder tool I run this commands and in the second i have the error with PLN

→ sudo php upgrade.php patch
→ sudo php upgrade.php upgrade

Actually my B.D is not upgrate for this error…
Thanks

ctgraham · October 16, 2015, 12:22pm

The commands patch -p1 < ojs-2.4.6-to-ojs-2.4.7.patch and php tools/upgrade.php patch are equivalent. Only one or the other should be used. Did you get results from running each?

I would strongly recommend using the “Full package” upgrade if you are not using version control (such as Git) to manage local changes. You are much less likely to end up with an inconsistent codebase, such as you describe above.