<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Allan Brown &#187; Magento connect</title>
	<atom:link href="http://allanbrown.me/tag/magento-connect/feed/" rel="self" type="application/rss+xml" />
	<link>http://allanbrown.me</link>
	<description>Proramming, Magento and me</description>
	<lastBuildDate>Tue, 19 Jan 2010 21:29:13 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Magento connect pear upgraded wrong Magento site!</title>
		<link>http://allanbrown.me/magento/magento-connect-pear-upgraded-wrong-magento-site/</link>
		<comments>http://allanbrown.me/magento/magento-connect-pear-upgraded-wrong-magento-site/#comments</comments>
		<pubDate>Sun, 01 Nov 2009 15:14:01 +0000</pubDate>
		<dc:creator>Allan Brown</dc:creator>
				<category><![CDATA[Magento]]></category>
		<category><![CDATA[Magento connect]]></category>
		<category><![CDATA[pear]]></category>
		<category><![CDATA[pear.ini]]></category>
		<category><![CDATA[staging site]]></category>

		<guid isPermaLink="false">http://allanbrown.me/?p=33</guid>
		<description><![CDATA[I upgraded Magento through Connect, and nothing happened!]]></description>
			<content:encoded><![CDATA[<p>When we started working with Magento, we started with a single site which we could being learning from.  Once we were happy that we would continue on this platform and decided we needed a 2nd development environment to work on we created a copy of our current Magento install, changed the DB connection config, and thought that was that.</p>
<p>Last week when I went to upgrade Magento to the latest version, a strange thing happened.  The upgrade through Magento connect (<a href="http://magento-devel.2fluid.co.uk/downloader/index.php?A=pearPackages" target="_blank">downloader/index.php?A=pearPackages</a>) worked perfectly, it said all was upgraded, but the files that were changed were changed on the wrong site.  I eventually tracked this down to the Magento Connect, and the fact that it has its own static config files (pear.ini) which saves the local Magento path.  This obviously did not change when the 2nd copy of the site was created, so when we then performed the upgrade on the staging version of the site, the live site was upgraded instead.</p>
<p>To fix this, simply delete pear.ini, and it will be recreated with the correct settings automatically.</p>
<p>Threads which reference this issue are:</p>
<p><a href="http://www.magentocommerce.com/boards/viewthread/17165/">http://www.magentocommerce.com/boards/viewthread/17165/</a><br />
<a href="http://www.magentocommerce.com/boards/viewthread/56226/">http://www.magentocommerce.com/boards/viewthread/56226/</a></p>
<p>Bit of an odd one!</p>
<div class="shr-publisher-33"></div>]]></content:encoded>
			<wfw:commentRss>http://allanbrown.me/magento/magento-connect-pear-upgraded-wrong-magento-site/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
