Magento

hi all - not solved this but may have come up with a work around. i have only tested on my test site for an upgrade from 1.1.1 to 1.1.4 but it worked ok there.

i ran the magento-core/Mage_All_Latest let it run until the usual stop - it installed a few of the updates and then stopped. i then opened a new safari window (left the original window open) and ran it again from that window. this time it installed a few more and stopped. i repeated opening new windows, leaving the previous one open until all updates had been installed. once they were all there - i check the test site was up and working and the admin back end was happy and then closed the windows - ignoring the warning message about PEAR processes still running as i knew they had all finished.

i would not recommend testing this on your configuration on a live site & database - try on your test/development ones.

it may have been a fluke and not repeatable - but thought i’d mention. not sure if i am brave enough to run on my live site. after having spent 3 days fixing if from the 1.0.X to 1.1.X upgrade debacle…

ok update - i have discovered that the issue seems to be with the Mage_Core elements. if you bring down each of the magento-core/Lib_x and even the Mage_Downloader these install ok. doing it element by element also seems to work.

but at the moment i cannot get the Mage_Core_Adminhtml or the Mage_Core_Modules to do anything than the usual downloading....... and stop. this includes any elements that pull down these elements as well. e.g. Interface_X elements also pull down these and seem to stop.

i do not know what this means - not particularly technically minded. but my test site is upgraded to 1.1.4 via the method above. i am half way through on my live site but now stuck on the Mage_Core bits.

good news everyone.

i have successfully updated the live site to 1.1.4 via the method above. it did seem to get stuck on the Mage_Core elements. i kept checking the /downloader/pearlib/download directory to see the extracted files come through. they all did but very slow.

my advice is still to try this method with your test site first - your config may be different to mine.

so the process was

1. back everything up - full site back up and MySQL databases.
2. go to Magento Connect and type magento-core/Mage_All_Latest
3. wait for the last message to come up - if your lucky it will install at least one of the elements - usually the Lib_X bits.
4. if this does not happen go to step 9
5. open a new browser window & go to you test website front end and check everything ok. repeat for back end in a new browser window.
6. DO NOT CLOSE ANY MAGENTO CONNECT WINDONWS UNTIL STEP 7 IS COMPLETED. open new browser window (not sure if a new tab would work) and repeat steps 2 onwards. when you go to the Magento Connect it should now show the elements that have successfully installed each time you repeat the steps above.
7. once all elements installed the Mage_All_Latest should report - Nothing to Update. test your site again (front and back end) and then close all the browser windows - note: i had 10 windows open during the process. you can now ignore the PEAR processes running messages. test you site again.
8. you’re done.
9. if none of the elements get the installed ok message - try instead of using Mage_All_Lastest use the individual elements one at a time e.g. magento-core/Lib_ZF etc. this way you may get the refresh button appear at the bottom - then you do not need to open a new browser window.
10. go through each of the elements until they are all installed and when you run Mage_All_Latest you get nothing to update message.

Interface_Adminhtml_Default 1.1.2 (stable) Default interface for Adminhtml
Interface_Frontend_Default 1.1.2 (stable) Default interface for Frontend
Interface_Install_Default 1.1.1 (stable) Default interface for Install
Lib_Google_Checkout 1.1.1 (stable) Google Checkout Library
Lib_Js_Calendar 1.0.18800 (stable) Javascript Libraries for Magento
Lib_Js_Ext 1.0.18800 (stable) Extjs Javascript Libraries for Magento
Lib_Js_Mage 1.1.1 (stable) Javascript Libraries for Magento
Lib_Js_Prototype 1.1.1 (stable) Prototype and Scriptaculous Javascript Libraries for Magento
Lib_LinLibertineFont 1.1.1 (stable) Libertine Open Fonts Project fonts for PDF print-outs
Lib_Varien 1.1.1 (stable) Varien Library
Lib_ZF 1.1.1 (stable) Zend Framework
Lib_ZF_Locale 1.1.1 (stable) Zend Framework Locale
Mage_All_Latest 1.1.4 (stable) Metapackage for latest Magento 1.1 release
Mage_Core_Adminhtml 1.1.4 (stable) Magento Administration Panel
Mage_Core_Modules 1.1.4 (stable) Collection of Magento Core Modules
Mage_Downloader 1.1.1 (stable) Magento Downloader

this was tested on Safari browser on OS X Mac with 1and1 hosting. no changes were made to the base config.

as i say not a fix but seems to offer a work around.

good luck.

I’ll be sure to try.  It makes sense.

Good job for figuring that out.

Hi,

Exactly the same problem here.

Could we maybe have a list of ALL the required core modules, and install them one-by-one, as that seems to work?

Also, I have reported this as a bug - but guess what - it’s not visible in the bug tracker…

Anywho - this should be fixed.
Thanks!

hi - not sure about anybody else but i have not been able to use this method for upgrade from 1.1.4 to 1.1.6 - all of the modules work apart from the interface and core modules (pretty critical).

i have been doing a manual overwrite via from a newly downloaded v1.1.6 - but this really is not a good method. actually it causes some small screw ups on my test site.

there’s a bug raised for this??