Replace the it with the original index.php

as the change affected this.

It changed the original line
Mage::run(’default’);

so replace
Mage::run(’’);
with
Mage::run(’default’);

The post 404 error page not found. magento appeared first on JASA Infosolutions | Expand Your Business.

This tutorial provides detailed information on how to move a Magento store from one host to another (or to a different hosting account).
MySQL database backup

On SiteGround servers you have phpMyAdmin included by default in cPanel for your account. In other cases you will have to use the same tool or a similar one that is capable of exporting your MySQL database. Detailed information on how to perform a MySQL backup can be found in our MySQL Tutorial.

Alternatively, if you don’t have phpMyAdmin installed but you have shell access you can use the mysqldump tool. The syntax is as follows:

mysqldump -h HOST -u USER -p DATABASENAME > FILENAME.sql

where:

HOST is the database server hostname or it can be omitted if you are running the MySQL server locally

USER – a user with full privileges to the Magento database

DATABASENAME – is the full name of the database which Magento is running

FILENAME – can be anything you find suitable for the backup file

Also, if you have Plesk, DirectAdmin or any other web hosting management tool, you can look at the available options. Many panels allow you to dump the database with just a few clicks. For example cPanel does have an option for this.

Transfer Files

You will need to download all files from your current store and upload them to the new location. This can be a time consuming task considering that a standard Magento installation consists of many files. A good alternative is to archive the files prior to downloading/uploading them if possible.

If you have SSH access you can log on your server -> magento installation directory and archive all the files using the following command:

tar -czif ARCHIVENAME.tar.gz

This will create a tarball archive of all the files in the directory.

You can then download the archive and easily upload it to the new location. To extract it at the new location use the following command in the desired destination folder for the Magento installation:

tar -xzif ARCHIVENAME.tar.gz

Adjust Configuration

After the files are restored you should alter the configuration file in order to match the new settings. All you need to change here is the database details at the new location. Those are stored in the app/etc/local.xml file. The lines you need to alter are:

<host><![CDATA[HOSTNAME]]></host>
<username><![CDATA[USER]]></username>
<password><![CDATA[PASSWORD]]></password>
<dbname><![CDATA[DATABASENAME]]></dbname>

where:

HOSTNAME should be the database hostname, most commonly – localhost

USER is a user that has full privileges to the database

PASSWORD is the password for the database user

DATABASENAME is the complete database name for the database you are going to use with the transferred Magento
Restore Database

Once you have adjusted the options above you should restore the database at the new location.

A good practice is to add several options in the MySQL backup file prior to uploading it. The following should be added at the beginning of the SQL file:

SET SQL_MODE=”NO_AUTO_VALUE_ON_ZERO”;
SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT;
SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS;
SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION;
SET NAMES utf8;
SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0;
SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0;
SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE=’NO_AUTO_VALUE_ON_ZERO’;
SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0;

The next option should be added at the end of the file after all other queries:

SET SQL_MODE=@OLD_SQL_MODE;
SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS;
SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS;
SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT;
SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS;
SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION;
SET SQL_NOTES=@OLD_SQL_NOTES;

You can now import the database using phpMyadmin -> Import or another MySQL tool depending on what kind of access you have to the website.

In case you would like to restore the database via a shell command you can use the following:

mysql -h HOST -u USER -p DATABASENAME < FILENAME.sql

and enter the password for the database user when asked. Note that if the Magento online store is supposed to work with a different domain name at the new location you should alter the entries for it in the MySQL database. The table you should edit is core_config_data and the values you need to change are in the path column. Change the web/unsecure/base_url and web/secure/base_url to match the new domain name by altering the value column for both records. The last step is to clear the Magento cache. You can do this either via the Magento admin panel > System > Cache management or by deleting the contents of the var/cache and var/session folders inside your Magento installation directory.

That is all. Your Magento should now be properly functioning at the new location.

The post Magento Move / Magento Transfer To A New Server appeared first on JASA Infosolutions | Expand Your Business.

Next you need to get SSH access from your hosting provider and connect to your server via SSH protocol. After connection via SSH go to your store folder and execute these commands:

1 – Change permissions on lib/pear folder to writable (recursively):

chmod -R 777 lib/PEAR

2 – Execute this command to prepare Magento for upgrade:

./pear mage-setup

Most likely you will see this result after command execution:

Channel “connect.magentocommerce.com/core” is already initialized

Upgrade from Magento 1.4.1.x to Magento 1.4.2.0

This step is necessary even if you upgrade your Magento store to 1.5 or 1.6 versions.

3 – Execute Magento upgrade command:

./pear upgrade -f magento-core/Mage_All_Latest-stable

Output of the command will show you what core packages were upgraded:

…
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

4 – When this part of the upgrade will be complete, enter these commands:

chmod 550 ./mage
./mage mage-setup .

You will see this result after command execution:

Successfully added: http://connect20.magentocommerce.com/community

It means that Magento connect 2.0 channel was added to the channels list successfully.

5 – Next, enter this command:

./mage sync

The result will 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

Upgrade to Magento 1.4.2.0 is complete and now you can proceed with upgrade to Magento 1.5.1.0 or 1.6.0.0 version.

Upgrade from Magento 1.4.2.0 to Magento 1.5.10 or Magento 1.6.0.0

Now you can upgrade your store to version 1.5 or 1.6.

Before proceeding with this part of Magento upgrade, it is very important to see to what version Magento upgrade scripts will upgrade your store. Enter this command to check this:

./mage list-upgrades

If you will see this result:

Updates for community:
Mage_All_Latest: 1.4.2.1 => 1.6.0.0
Lib_Js_Mage: 1.4.2.0 => 1.6.0.0
Lib_Varien: 1.4.2.0 => 1.6.0.0
Lib_Phpseclib: 1.4.2.0 => 1.5.0.0

It means that your Magento will be upgraded to version 1.6.0.0. If it is not what you need you can change upgrade channel to “stable” and upgrade your Magento to version 1.5.1.0.

6 – Enter this command to change the upgrade channel to stable:

./mage config-set preferred_state stable

After this the “./mage list-upgrades” command will show you this result:

Updates for community:
Mage_All_Latest: 1.4.2.1 => 1.5.1.0.1
Lib_Js_Mage: 1.4.2.0 => 1.5.1.0
Lib_Varien: 1.4.2.0 => 1.5.1.0
Lib_Phpseclib: 1.4.2.0 => 1.5.0.0
Mage_Core_Adminhtml: 1.4.2.0 => 1.5.1.0
Mage_Core_Modules: 1.4.2.0 => 1.5.1.0

7 – After channel selection you can upgrade your Magento to 1.5.1.0 (or to Magento 1.6.0.0) using this command:

./mage upgrade-all –force

You will see upgraded packages on your screen:

…
Package upgraded: community/Mage_Locale_en_US 1.6.0.0
Package upgraded: community/Lib_Mage 1.6.0.0
Package upgraded: community/Lib_ZF 1.11.1.0
Package upgraded: community/Lib_Js_Prototype 1.7.0.0.1
Package upgraded: community/Lib_ZF_Locale 1.11.1.0

Now the upgrade is complete and you can execute database upgrade visiting your Magento store in your browser. If everything was upgraded correctly, you will see upgraded store in your browser.

You can check version of your store in the footer of Magento administration panel.

The post How To Upgrade Magento from 1.4. version to Magento 1.5 and 1.6? appeared first on JASA Infosolutions | Expand Your Business.