Magento

I followed the instructions here:
http://www.crucialwebhost.com/kb/article/upgrading-magento-via-ssh/

All seemed to go well. But the version displayed on the front and back ends of my Magento installation have not changed. How can I make sure my upgrade to 1.5.0.1 was successful?

Thanks!

Simplest way is to check the footer in admin.

Most probably the upgrade didn’t complete.

Try forcing the install if the version is still the same, e.g.:

...or:

This works as well

Hiya!

We usually check app/Mage.php in a text editor about 1/4 of the way down:

public static function getVersionInfo()
{
return array(
‘major’ => ‘1’,
‘minor’ => ‘5’,
‘revision’ => ‘0’,
‘patch’ => ‘1’,
‘stability’ => ‘’,
‘number’ => ‘’,
);
}

My app/Mage.php contains this:

‘major’ => ‘1’,
‘minor’ => ‘4’,
‘revision’ => ‘2’,
‘patch’ => ‘0’,
‘stability’ => ‘’,
‘number’ => ‘’,

Obviously my upgrade was not a happy one.

./mage install -f http://connect20.magentocommerce.com/community Mage_All_Latest
Error:
install: Argument should be: channelName packageName

./pear install -f magento-core/Mage_All_Latest
warning: pear/Console_Getopt requires PEAR Installer (version >= 1.9.1), installed version is 1.7.1

Also, this attempt downloads 18 tgz files before it chokes:

PHP Fatal error:  Allowed memory size of 20971520 bytes exhausted (tried to allocate 77 bytes) in /var/www/mywebsite/htdocs/downloader/pearlib/php/PEAR/PackageFile/v2.php on line 733

Fatal error: Allowed memory size of 20971520 bytes exhausted (tried to allocate 77 bytes) in /var/www/mywebsite/htdocs/downloader/pearlib/php/PEAR/PackageFile/v2.php on line 733

Thanks for all the replies!

Try doing your upgrade via FTP

Brent W Peterson - 21 February 2011 12:54 PM

Try doing your upgrade via FTP

I didn’t know how to do that. So what I did was download the full 1.5.0.1 tar.gz fle from Magento and extracted that into my site using SSH. That seems to have done the trick.

Thanks, everyone!

Crucial - 19 February 2011 09:18 AM

./mage install -f http://connect20.magentocommerce.com/community Mage_All_Latest

Just thought I would mention that the mage script doesn’t like the -f flag. I suspect that Connect 2.0 still has a few bugs.

Also, the full channelName URL is not required, can just type it like this:

Although, I don’t know why it is under ‘community’, shouldn’t it be under the ‘core’ channel??