Search type Search syntax
Tags [tag]
Exact "words here"
Author user:1234
user:me (yours)
Score score:3 (3+)
score:0 (none)
Answers answers:3 (3+)
answers:0 (none)
isaccepted:yes
hasaccepted:no
inquestion:1234
Views views:250
Sections title:apples
body:"apples oranges"
URL url:"*.example.com"
Favorites infavorites:mine
infavorites:1234
Status closed:yes
duplicate:no
migrated:no
wiki:no
Types is:question
is:answer
Exclude -[tag]
-apples
For more details on advanced search visit our help page
Results tagged with Search options user 3132

Questions related or caused by Magento upgrade process.

0
votes
To confirm you have upgraded all your code you can check your app/Mage.php file to confirm your new version is in place. cat app/Mage.php | grep version -A 12 This will return a string that gives y …
answered Jul 5 '17 by brentwpeterson
2
votes
When you upgrade Magento you will keep all your old data See the WIKI on the Magento site here http://www.magentocommerce.com/wiki/1_-_installation_and_configuration/manual_upgrade_using_fresh_install_and_original_database It will layout the steps to upgrade your site. Remember always make a backup!! …
answered Feb 4 '14 by brentwpeterson
1
vote
First: You should not do this with Magento Connect, nor would I ever recommend using Magento connect [for anything]. According to Magento You DO NOT have to do an incremental upgrade. You will … need to test and apply the new XML updates on your theme. There is alot of work involved in this upgrade and there are many steps that have to happen and you need to check each aspect of the upgrade. I …
answered May 19 '15 by brentwpeterson
0
votes
You are never going to have ZERO down time unless you want to re-enter or sync order data. The problem you are facing is that the database will take time to upgrade. The above answer from Fabian or … ) and we brought the site down during the upgrade. Any site can expect some maintenance and it will depend on the version to version, the number orders and the general size of the database to determine how long your down time will be. …
answered Jun 3 '14 by brentwpeterson
0
votes
I would recommend the following: 1) Make a complete working backup of your site 2) Copy the 1.7 files into you project (Using RSYNC or FTP) 3) Run your upgrade - Test On your production site …
answered Sep 23 '13 by brentwpeterson
0
votes
1answer
Looking for thoughts if I should go to 13.1 before going to 14.0.1 on an upgrade from 13.0.1? EDIT: My question more specifically. Should I bother into copy in the 1.13.1 files, then do the php scripts, then run the 1.14 files? …
asked May 25 '14 by brentwpeterson
2
votes
application. The easiest way to do this is using rsync. (rsync -avz /from/path/ /to/path/live/) Visit your dev site (http://dev.mydomain.com) and run the upgrade Test everything Once you have done … your site. The copy the new files into your application like you did in your dev environment. Run you upgrade and you are set! …
answered Mar 4 '15 by brentwpeterson
1
vote
There are many testing platforms that you can use with Selenium being on of the more usable versions. There are also a number of 3rd party sites that will help you use Selenium (http://www.seleniumhq. …
answered Jan 2 '15 by brentwpeterson
3
votes
The safest way to do an upgrade is the following: Get a database dump of your current website and test the upgrade process with a clean version of Magento. This is a version of Magento fresh out of … the box. From this you can get a baseline of how your upgrade will go. You can then access your modules by testing one at a time into your system. Finally you can move your Theme in and test this …
answered Nov 16 '14 by brentwpeterson
1
vote
Since nearly everything you are waiting for is database updates you should review processlist. mysql> show processlist; +----+------+-----------+------+---------+------+-------+------------------+ | …
answered May 6 '18 by brentwpeterson
2
votes
Yes, you did the upgrade correctly and you DON'T have to do incremental upgrades No you don't have to run the 1.13 upgrade scripts. …
answered Jul 8 '15 by brentwpeterson
1
vote
1answer
Getting this error after an upgrade and after I try to run php indexer.php --reindex catalog_category_product. Please Help to solve this Problem. …
asked Jan 17 '14 by brentwpeterson
0
votes
If you update your entire Magento application by downloading, un-taring and rsyncing Magento over your current version you should see the corrections. WARNING: If you do have core changes they will b …
answered Jul 11 '14 by brentwpeterson
1
vote
Magento provided a patch for this error app/code/core/Mage/Catalog/etc/config.xml app/code/core/Mage/Catalog/sql/catalog_setup/upgrade-1.6.0.0.18.1.1-1.6.0.0.18.1.2.php Sorry, this is silly but I … > + <version>1.6.0.0.18.1.2</version> </Mage_Catalog> </modules> <admin> diff --git app/code/core/Mage/Catalog/sql/catalog_setup/upgrade-1.6.0.0.18.1.1-1.6.0.0.18.1.2.php app/code/core …
answered Jan 18 '14 by brentwpeterson
0
votes
This was a stupid mistake: I forgot to put the prefix in the local.xml
answered Jan 9 '14 by brentwpeterson

15 30 50 per page