Posting in the Magento forums has been disabled pending the implementation of a new and improved forum solution which should better serve the community.

For new questions please post at magento.stackexchange.com, the community-run support site for the Magento community. We will be providing updates on the new forum solution soon. For questions or concerns please email community@magento.com.

Magento Forum

PEAR Upgrade problem: How to change the document root location? 
 
kramusica
Member
 
Total Posts:  55
Joined:  2008-07-16
 

I got something with SSH but Magento connects still gives me an error. It’s the old path:
ERROR: failed to mkdir /home/online/public_html/shops/app/etc/modules

Where can I find the new_serialized folder?

EDIT: found it in .registry. Do I need to copy those registry files somewhere?

 
Magento Community Magento Community
Magento Community
Magento Community
 
diglin
Sr. Member
 
Avatar
Total Posts:  93
Joined:  2008-12-29
Zurich - Switzerland
 

The new_serialized folder should be in your .registry folder.
It seems that you provided a wrong path concerning your registry folder because there is an error in the etc/modules folder. It’s the wrong place to create the directory. The mkdir is for the .registry folder and create the new_serialized folder inside. That’s why I’m surprised to see this error.

 
Magento Community Magento Community
Magento Community
Magento Community
 
kramusica
Member
 
Total Posts:  55
Joined:  2008-07-16
 

I do have the new_serialized folder in my .registry folder. For some reason Magento Connect is still picking up the old path from somewhere, /online/ should be /online-marketing-consultancy/ . Is there a way to check where it is getting that reference from?

 
Magento Community Magento Community
Magento Community
Magento Community
 
diglin
Sr. Member
 
Avatar
Total Posts:  93
Joined:  2008-12-29
Zurich - Switzerland
 

Stupid question from me: did you copy the content of the new_serialized folder into the corresponding folder ? You have to copy this content to the parent folder normally.
The folders are hidden, so make a ls -a in unix system

You can check in the .registry folder and search the module you installed, it seems to be a module for SEO so search this one, open the file with a text editor and search inside the path to see if you have the old or the new one. It’s a serialized file so don’t be surprised to see some characters.

When you edit in a post here I have no notification, reply to this thread. I say that because I saw your question only now: Do I need to copy those registry files somewhere? You have your response just above.

 
Magento Community Magento Community
Magento Community
Magento Community
 
kramusica
Member
 
Total Posts:  55
Joined:  2008-07-16
 

It was the pear.ini file. It was still referencing to the old url. Magento Connect is working now. Thanks very much for your help!

 
Magento Community Magento Community
Magento Community
Magento Community
 
stephane142
Member
 
Total Posts:  43
Joined:  2009-01-11
 

Ross’s third post worked fine !
I had the same problem, now fixed ! Thanks a lot !

 
Magento Community Magento Community
Magento Community
Magento Community
 
lividinstruments
Member
 
Total Posts:  64
Joined:  2008-10-03
 

Deleting pear.ini worked perfect for me. I didn’t seem to loose the other extension I had installed. I didn’t see a new pear.ini get created, is that a problem?

 
Magento Community Magento Community
Magento Community
Magento Community
 
deskartez
Jr. Member
 
Total Posts:  18
Joined:  2009-07-04
 

the extensions information for magento are stored in the following folders :

/downloader/pearlib/php/.registry/.channel.connect.magentocommerce.com_community
/downloader/pearlib/php/.registry/.channel.connect.magentocommerce.com_core

depending on the type of extension it is stored in a different “.channel”

here is great information by MDBattery about migrating extensions from a test site to a live site.
magento manual migration of extensions to live site

i have utilized the information here to resolve issues that i have been haveing with the main site because of the installation of an extension. When i would completely remove the “dowloader/” direcotry and upload a new “downloader/” folder from a fresh magento install all my issues would more or less be resolved .

regards
deskartez

 
Magento Community Magento Community
Magento Community
Magento Community
 
Eminent Style
Sr. Member
 
Avatar
Total Posts:  86
Joined:  2008-02-17
Bromsgrove, United Kingdom
 
Ross - 14 February 2008 08:50 AM

Ok, I think I found out what to do.

delete the old pear.ini
magento/lib/pear/pear.ini

Now, in doing this we loose the old directory settings, but also loose the ‘stable’ or ‘beta’ upgrade options, so resave the PEAR configuration via the Magento backend.
Go to: System -> Extensions -> PEAR Configuration
set: Preferred State to ‘Beta’ (or whateva)
Save PEAR Config

Then the PEAR upgrade should work (of course your mileage may vary).

Thanks Ross, this fixed it for me.

 
Magento Community Magento Community
Magento Community
Magento Community
 
Eminent Style
Sr. Member
 
Avatar
Total Posts:  86
Joined:  2008-02-17
Bromsgrove, United Kingdom
 
lividinstruments - 04 September 2009 06:07 AM

Deleting pear.ini worked perfect for me. I didn’t seem to loose the other extension I had installed. I didn’t see a new pear.ini get created, is that a problem?

I don’t know whether its an issue but if you go into the settings from Magento Connect and save your preferred stability state (e.g. stable / beta etc.), then another gets created.

 
Magento Community Magento Community
Magento Community
Magento Community
 
Mango Swiss
Jr. Member
 
Total Posts:  21
Joined:  2009-09-21
 

Perhaps I missing something and I’m going to come accross a problem later but I deleted the pear.ini file and saved the setting in my Magento Connect settings tab to ‘Stable’ and it all seemed to just work. Can’t find any problems with it yet. My old extensions were still in place and I’ve just installed some new ones that appear to have installed correctly.

 
Magento Community Magento Community
Magento Community
Magento Community
 
standout
Jr. Member
 
Total Posts:  7
Joined:  2009-11-02
 

Ladies, Gents,
Please could you help - I believe this same thread to discuss my problem
Upon using Mag. Connect to install a theme - I get the following

downloading magento_classic_theme_free-1.1.3.tgz ...
Starting to download magento_classic_theme_free-1.1.3.tgz (356,142 bytes)
. . . . . ...done: 356,142 bytes
ERROR: failed to mkdir /home/staondut/public_html/app/design/frontend/default/f002/layout

I have deleted pear.ini, and regenerated it using the settings button and opting for “stable”.

But this still leads me to this error!

How can this be overcome?

Thanks in advance!

 
Magento Community Magento Community
Magento Community
Magento Community
 
danielifrim7
Member
 
Avatar
Total Posts:  63
Joined:  2009-04-29
Bucuresti
 
standout - 29 November 2009 02:26 PM

Ladies, Gents,
Please could you help - I believe this same thread to discuss my problem
Upon using Mag. Connect to install a theme - I get the following

downloading magento_classic_theme_free-1.1.3.tgz ...
Starting to download magento_classic_theme_free-1.1.3.tgz (356,142 bytes)
. . . . . ...done: 356,142 bytes
ERROR: failed to mkdir /home/staondut/public_html/app/design/frontend/default/f002/layout

I have deleted pear.ini, and regenerated it using the settings button and opting for “stable”.

But this still leads me to this error!

How can this be overcome?

Thanks in advance!

I got the same error on an extension with a missing directory in it.
Check the tar.gz archive in pear cache download dir and see if the dir exists.

./pear mage-setup
will fix most of your problems
 
Magento Community Magento Community
Magento Community
Magento Community
 
capncaveman
Jr. Member
 
Total Posts:  22
Joined:  2009-10-24
 

Awesome! Thanks!

I had the same issue with pear linking to another domain.  All I did to resolve was delete the pear.ini file...after I backed it up of course, refreshed the cache and Voila!  Back in business.  I was able to install extensions again with Magento Connect.

Thanks to all who participated in my solution!

 
Magento Community Magento Community
Magento Community
Magento Community
 
lazzo
Jr. Member
 
Avatar
Total Posts:  10
Joined:  2009-09-07
Malmö, Sweden
 

Thanx - renaming / deleting the downloader/pearlib/pear.ini file after moving the a Magento store to another path saved my day. Now Magento Connect works fine again. Great!

cheese

 
Magento Community Magento Community
Magento Community
Magento Community
Magento Community
Magento Community
Back to top