Categories
magento

Having issues upgrading to Magento 1.3.1

Magento 1.3.1 was just released with a few new features and bug fixes. I decided to upgrade my test environment for a client site that is launching soon.

Going through Magento Connect

I get the following errors:

magento-core/mage_core_adminhtml requires package “magento-core/Mage_Core_Modules”
(version >= 1.3.0, version <= 1.3.0), downloaded version is 1.3.1
...
Install Errors
No valid packages found
PEAR ERROR: upgrade failed

It was giving me this error for all packages, requiring an odd version and not letting me go any further.

Searching around

Looking around I couldn’t find any fixes for this issue. There were a few people who had the same issue but no replies to their forum threads.

The Solution

Upgrade the installation via command line. For some reason going through the web interface just did not work. But if you have SSH access (which you should) to your server just navigate to your Magento install directory and run the following commands. I believe this works on both Linux and Windows servers.

./pear upgrade-all
rm -rf downloader/pearlib/cache/*
rm -rf var/cache/*

And then tada! “Magento ver. 1.3.1” should show up in the footer of your admin area.

Categories
rails

Fixing: uninitialized constant Gem::GemRunner (NameError) – Ubuntu

After upgrading to the newest version of rails (2.2.2) I was getting this error:

administrator@shuttle:~/$ gem -v
/usr/bin/gem:10:Warning: Gem::manage_gems is deprecated and will be removed on or after March 2009.
/usr/bin/gem:23: uninitialized constant Gem::GemRunner (NameError)

Anytime I called “gem” I would get this error and could not get past.

Here is the fix

administrator@shuttle:~/$ sudo vim /usr/bin/gem

Change the top of the file to look like this:

require 'rubygems'
require 'rubygems/gem_runner'
#Gem.manage_gems

Save and when you run this you should see this:

administrator@shuttle:~/$ gem -v
1.3.1

You should no longer get the error with running “gem”