This is actually the current explanation from the Magento 1.3.x,
1.4.x, 1.5.x, 1.6.x and 1.7.x x update procedure.It includes step x
step directions as well as repair info.
After that you want to get SSH accessibility from the web hosting supplier as well as connect with your own machine through SSH process (using Cpanel control covering or even Putty SSH customer with regard to Windows).
Right after link through SSH, visit your own shop document as well as perform these types of instructions:
1 Modify accord upon lib/pear document in order to writable (recursively):
1 Perform Magento update control:
…
upgrade ok: channel://connect.magentocommerce.com/core/Mage_Centinel-1.4.2.0
upgrade ok: channel://connect.magentocommerce.com/core/Interface_Frontend_Base_Default-1.4.2.0
upgrade ok: channel://connect.magentocommerce.com/core/Phoenix_Moneybookers-1.2.3
upgrade ok: channel://connect.magentocommerce.com/core/Find_Feed-1.0.7
upgrade ok: channel://connect.magentocommerce.com/core/Interface_Adminhtml_Default-1.4.2.0
2 Whenever this particular section of the update is going to be total, get into these types of instructions:
Effectively additional: http://connect20.magentocommerce.com/community
This means which Magento link 2 .0 station had been put into the actual stations listing effectively.
3 Following, get into this particular control:
…
Successfully added: community/Mage_Locale_en_US-1.4.2.0
Successfully added: community/Interface_Install_Default-1.4.2.0
Successfully added: community/Phoenix_Moneybookers-1.2.3
Successfully added: community/Mage_Downloader-1.5.0.0
Successfully added: community/Lib_Google_Checkout-1.4.2.0
Update in order to Magento 1.4.2.0 is actually total and today you are able to continue along with update in order to Magento 1.7.x edition.
Prior to going forward with this particular portion of Magento update, it is very important notice as to what edition Magento update intrigue will certainly get some new shop.Get into this particular control to check on this particular:
Updates for community:
Mage_All_Latest: 1.4.2.1 => 1.7.0.2
Lib_Js_Mage: 1.4.2.0 => 1.7.0.2
Lib_Varien: 1.4.2.0 => 1.7.0.2
This means that the Magento is going to be improved in order to edition 1.7.0.2. When it is not really the thing you need you are able to modify update station in order to “beta” as well as get some new Magento in order to RC (beta) edition.
1 Get into this particular control to improve the actual update station in order to stable (remember, “stable” station will certainly get some new Magento in order to most recent 1.7.x stable version):
Updates for community:
Mage_All_Latest: 1.4.2.1 => 1.7.0.2.
Lib_Js_Mage: 1.4.2.0 => 1.7.0.2.
Lib_Varien: 1.4.2.0 => 1.7.0.2.
Lib_Phpseclib: 1.4.2.0 => 1.7.0.2.
Mage_Core_Adminhtml: 1.4.2.0 => 1.7.0.2.
Mage_Core_Modules: 1.4.2.0 => 1.7.0.2.
2 Right after station choice you are able to get some new Magento in order to Magento 1.7.0.2) employing this control:
…
Package upgraded: community/Mage_Locale_en_US 1.7.0.2
Package upgraded: community/Lib_Mage 1.7.0.2
Package upgraded: community/Lib_ZF 1.11.1.0
Package upgraded: community/Lib_Js_Prototype 1.7.0.2.
Package upgraded: community/Lib_ZF_Locale 1.11.1.0
Right now the actual update is actually total and you may perform data source update going to your own Magento shop within your internet browser, this method will require a number of moments, therefore have patience.In case every thing had been improved properly, you will notice improved shop within your internet browser.Prior to data source update it is strongly recommended to improve some memory space limitations associated with the PHP motor.
When it is impossible to improve this, you can test in order to perform data source update through SSH, electronic. gary the gadget guy.:
upgrade-all: Booking with regard to adequate create document accord.
Mistake: upgrade-all: Your own Magento document don't have adequate create accord, that downloader needs.
Perform this particular control to correct the actual mistake:
upgrade-all: Incorrect balance within compare Stabilities discussion.
Perform these types of instructions, it is going to repair the problem:
“Internal Machine Error” rather than Magento local store web page or even management area webpages.
Almost certainly problem is actually linked to incorrect accord.
Repair this problem using 1 of these recursive instructions:
Re-index your own data source within Magento management screen as well as crystal clear Magento cache.
5 Magento mistake:
“Invalid way of clean() method”.
Crystal clear Zend cache (all documents, such as “Backend” folder) within [magento_folder]/app/code/core/Zend/Cache/
6 Magento mistake:
“Call to some associate functionality to Html() on the non-object within …/Layout.php”.
Open [magento_folder]/app/design/frontend/default/[your_theme]/layout/page.xml and replace this line of the code:
“Maximum crucial dimension should be smaller sized 32″. Crystal clear Magento cache.
8 Pagination is not really displaying upon item real estate:
Open up this particular document: app/code/core/Mage/Catalog/Block/Product/List/Toolbar.php
As well as substitute this particular type of the actual program code
course Mage_Catalog_Block_Product_List_Toolbar stretches Mage_Core_Block_Template
along with:
course Mage_Catalog_Block_Product_List_Toolbar stretches Mage_Page_Block_Html_Pager
9 Magento mistake:
Line not really discovered: 1 054 Not known line ‘custom_use_parent_settings’ within ‘where clause’
Re-index your own data source utilizing Control panel covering.
10 Magento mistake:
Are not able to connect with the actual data source. What is /app/etc/local.xml and ensure there is this kind of program code
Get ready for Magento update (for 1.3.x, 1.4.x x variations only)
Allows image resolution you have aged Magento 1.3.x – 1.4.x.x shop and you also have to update this in order to most recent Magento 1.7.x edition.To begin with it really is strongly suggested in order to back-up your own reside shop files/database as well as deactivate Magento compiler cache.After that you want to get SSH accessibility from the web hosting supplier as well as connect with your own machine through SSH process (using Cpanel control covering or even Putty SSH customer with regard to Windows).
Right after link through SSH, visit your own shop document as well as perform these types of instructions:
1 Modify accord upon lib/pear document in order to writable (recursively):
chmod -R 777 lib/PEAR2 Perform this particular control to get ready Magento with regard to update:
./pear mage-setupAlmost certainly you guys will discover this particular outcome right after control performance: Station “connect.Magento commerce.com/core” has already been initialized
Update through Magento 1.3.x, aged 1.4.x in order to Magento 1.4.2.0
Update in order to 1.4.2.0 is needed, even though you get some new aged Magento 1.3.x shop in order to 1.7.x edition.1 Perform Magento update control:
./pear upgrade -f magento-core/Mage_All_Latest-stableOutcome from the control will reveal exactly what primary deals had been improved:
…
upgrade ok: channel://connect.magentocommerce.com/core/Mage_Centinel-1.4.2.0
upgrade ok: channel://connect.magentocommerce.com/core/Interface_Frontend_Base_Default-1.4.2.0
upgrade ok: channel://connect.magentocommerce.com/core/Phoenix_Moneybookers-1.2.3
upgrade ok: channel://connect.magentocommerce.com/core/Find_Feed-1.0.7
upgrade ok: channel://connect.magentocommerce.com/core/Interface_Adminhtml_Default-1.4.2.0
2 Whenever this particular section of the update is going to be total, get into these types of instructions:
chmod 550 ./mage ./mage mage-setup .People will discover this particular outcome right after control performance:
Effectively additional: http://connect20.magentocommerce.com/community
This means which Magento link 2 .0 station had been put into the actual stations listing effectively.
3 Following, get into this particular control:
./mage syncThe end result is going to be:
…
Successfully added: community/Mage_Locale_en_US-1.4.2.0
Successfully added: community/Interface_Install_Default-1.4.2.0
Successfully added: community/Phoenix_Moneybookers-1.2.3
Successfully added: community/Mage_Downloader-1.5.0.0
Successfully added: community/Lib_Google_Checkout-1.4.2.0
Update in order to Magento 1.4.2.0 is actually total and today you are able to continue along with update in order to Magento 1.7.x edition.
Update through Magento 1.4.x, 1.5.x, 1.6.x in order to Magento 1.7.x
Right now you guys may update the shop in order to edition 1.7.0.2 .Prior to going forward with this particular portion of Magento update, it is very important notice as to what edition Magento update intrigue will certainly get some new shop.Get into this particular control to check on this particular:
./mage list-upgradesIn case you will discover this particular outcome:
Updates for community:
Mage_All_Latest: 1.4.2.1 => 1.7.0.2
Lib_Js_Mage: 1.4.2.0 => 1.7.0.2
Lib_Varien: 1.4.2.0 => 1.7.0.2
This means that the Magento is going to be improved in order to edition 1.7.0.2. When it is not really the thing you need you are able to modify update station in order to “beta” as well as get some new Magento in order to RC (beta) edition.
1 Get into this particular control to improve the actual update station in order to stable (remember, “stable” station will certainly get some new Magento in order to most recent 1.7.x stable version):
./mage config-set preferred_state stableFollowing this the actual “./mage list-upgrades” control will reveal this particular outcome:
Updates for community:
Mage_All_Latest: 1.4.2.1 => 1.7.0.2.
Lib_Js_Mage: 1.4.2.0 => 1.7.0.2.
Lib_Varien: 1.4.2.0 => 1.7.0.2.
Lib_Phpseclib: 1.4.2.0 => 1.7.0.2.
Mage_Core_Adminhtml: 1.4.2.0 => 1.7.0.2.
Mage_Core_Modules: 1.4.2.0 => 1.7.0.2.
2 Right after station choice you are able to get some new Magento in order to Magento 1.7.0.2) employing this control:
./mage upgrade-all --forceIn case “./mage upgrade-all -force” will never function, you can test in order to perform this particular control:
./mage install http://connect20.magentocommerce.com/community Mage_All_Latest --forceYou will notice improved deals on the display screen:
…
Package upgraded: community/Mage_Locale_en_US 1.7.0.2
Package upgraded: community/Lib_Mage 1.7.0.2
Package upgraded: community/Lib_ZF 1.11.1.0
Package upgraded: community/Lib_Js_Prototype 1.7.0.2.
Package upgraded: community/Lib_ZF_Locale 1.11.1.0
Right now the actual update is actually total and you may perform data source update going to your own Magento shop within your internet browser, this method will require a number of moments, therefore have patience.In case every thing had been improved properly, you will notice improved shop within your internet browser.Prior to data source update it is strongly recommended to improve some memory space limitations associated with the PHP motor.
When it is impossible to improve this, you can test in order to perform data source update through SSH, electronic. gary the gadget guy.:
php -f ./index.phpWhenever data source update is going to be completed, you should check edition of the shop within the footer associated with Magento management screen.
Repair
1 Magento update software mistake:upgrade-all: Booking with regard to adequate create document accord.
Mistake: upgrade-all: Your own Magento document don't have adequate create accord, that downloader needs.
Perform this particular control to correct the actual mistake:
chmod -R 777 Upgrade2 Magento update software mistake:
upgrade-all: Incorrect balance within compare Stabilities discussion.
Perform these types of instructions, it is going to repair the problem:
./mage channel-add connect20.magentocommerce.com/community ./mage channel-add connect20.magentocommerce.com/core ./mage syncOr even like a remedy you are able to operate this particular control:
./mage install http://connect20.magentocommerce.com/community Mage_All_Latest --force3 Machine mistake:
“Internal Machine Error” rather than Magento local store web page or even management area webpages.
Almost certainly problem is actually linked to incorrect accord.
Repair this problem using 1 of these recursive instructions:
find . -type f -exec chmod 644 {} \;
find . -type d -exec chmod 755 {} \;
4 Magento mistake: Various mistakes within Magento data source.Re-index your own data source within Magento management screen as well as crystal clear Magento cache.
5 Magento mistake:
“Invalid way of clean() method”.
Crystal clear Zend cache (all documents, such as “Backend” folder) within [magento_folder]/app/code/core/Zend/Cache/
6 Magento mistake:
“Call to some associate functionality to Html() on the non-object within …/Layout.php”.
Open [magento_folder]/app/design/frontend/default/[your_theme]/layout/page.xml and replace this line of the code:
With:
7 Magento mistake:
“Maximum crucial dimension should be smaller sized 32″. Crystal clear Magento cache.
8 Pagination is not really displaying upon item real estate:
Open up this particular document: app/code/core/Mage/Catalog/Block/Product/List/Toolbar.php
As well as substitute this particular type of the actual program code
course Mage_Catalog_Block_Product_List_Toolbar stretches Mage_Core_Block_Template
along with:
course Mage_Catalog_Block_Product_List_Toolbar stretches Mage_Page_Block_Html_Pager
9 Magento mistake:
Line not really discovered: 1 054 Not known line ‘custom_use_parent_settings’ within ‘where clause’
Re-index your own data source utilizing Control panel covering.
10 Magento mistake:
Are not able to connect with the actual data source. What is /app/etc/local.xml and ensure there is this kind of program code
{{db_model}}
Источник
Комментариев нет:
Отправить комментарий