However the copy procces of  Magento shop has following main steps

• duplication of database schema
• duplication of core sources
• duplication of downloader sources

Database

First, let me say say, that it is good idea to not install two Magento instances to the same database. Magento in  version 1.1.8 s has 198 database tables. Most of them are of type  InnoDB and they are  related with each other by checked foreign key constraints. That is background information.

So new database for every  Magento instance save you from having headaches  and this not only because having just two magento installation i one DB leads too approx. 400 tables in one database but more to avoid possible problems or side effects with constraints and Co. (e.g. ) .  .

The easiest way to export the database is to use phpMyAdmin. Go to export dialog of original database, select “zipped” option, select tabbles, let other options on their defaults (See screen 1) and get zipped download. Switch to new database and  upload the downloaded  there in the import dialog.

Sound as a piece of cake, but sometimes the import of the SQL files will not work. I have already seen many different exceptions bu trying. Beginning with “SQL Syntax..” and ending with “constraint violation…”.  In my opinion the purpose of problems is size of some tables and therefore of whole backup. There are few MyISAM tables that are full with (useless) log data. And the amount of this data makes problems to the import routine. Don’t export them first at time! they don’t have any constraint to other tables so you can import them on second or third turn. Alternative  you can export only the DDL-Statement of this table not the data itself.

Here are tables you can  omit in first step:

• log_url
• log_url_info
• log_visitor
• log_visitor_info

Don’t forget to change configured URL of origin shop to the  URLs of new shop in the table core_config_data. You can also use Search-Tool of phpMyAdmin and identify every record where old URL is used – but outside of core_config_data table  they are not so important and could be changed later in the Shop interface.

Core Sources

That is most easiest part. Just copy the source of magento to the new location, but don’t copy the following:

• downloader dir
• any content of dirs inside of var but .htacces file.
• media/tmp dir

If you use another DB for new Magento installation don’t forget to change DB setting in app/etc/local.xml file. Var directory hold any temporary content like sessions, caches and error-logs. Downloader is used by Magento connect module, before copy must do some preparations.

Magento Downloader

Warning! do not copy unchanged downloader to new location on the same server it may break your origin magento installation!

Now I got your attention The problem is that downloder stores serverpath in many many configuration files. And if you don’t change the serverpath  and  starts updates on  new shop copy, you will update the origin shop and not the new copy of it!

The server path of origin magento shop is stored in many many files in the downloader directory, you can’t change all of them manually. But you can do it automatically. If you have SSH access to your web-space  following command will help you:

Update: The described way to handle downloader sometimes causes problems by doing upgrade. Especially pear.ini shold be treatet carefully. Check also a workaround proposed by Enno Julian.

//shows all files with OLD_PATH element

find  . -type f -exec grep -q "OLD_PATH" '{}' \; -print

//Replaces OLD_PATH string in all occurrences in every file to NEW_PATH

find . -type f -print | xargs sed -i -e ’s/OLD_PATH/NEW_PATH/g’

If you have only ftp access, then you can use [Alt+F7]-search in Total Commander. Then open each file with Notepad++ and then use “Search and Replace” functionality of Notepad++ on each file. Whole replacement willtake you max. 5 minutes.

After replacing old path you can upload downloader to the new instance of Magento.

Now everything including “Magento Connect” should work properly and independent form each othen on thow instances. The last thing my be useful   is to clear all caches in admin back-end of new instance. Good luck!

Open Question

This article describes how to double the Magento instance once. The next question which i didn’t answered for me yet is how to make permanent  mirroring of data from production environment to the test installation. Maybe someone has cool ideas?

Disclaimer

Please consider that I can’t guarantee that everything described here will work in your environment as it worked for me. Please use this tutorial as incitement and adopt my methods to your own situation. Be sure that you don’t peril origin Magento installation or other data. Do regular backup befor you begin!

Be Sociable, Share!

• 

But updating of WordPress means download, backup, copy files per FTP and maybe backuping old files. And it get’s terrible, when you have to manage several sites.

But the lazy way exists too! And you need just two plug-ins, which can make you life really easier and secure, cause you don’t need to adjourn such important tasks.

Here are needed Plug-Ins:

• The DB back up Plug-in.
• The Instant Upgrade Plug-In

After installing these two you can start with the upgrading of your blog.

Backup

First use backup Plug-in to secure your DB cause ever update can brake your WordPress for several reasons. Presented Backup Plug-In is really handy. Yo can select where to save the backup file, or whether it should be send per mail.

Of cause the configuration of scheduler is possible. Furthermore the is possibility to back up all other db tables in the same Database scheme just by selectem them.

Update

Updating with instant update Plug-In is easy too. It can be really done with one click, how promissed in the caption and in the Plug-In description. There is one option to choose wheter to upgrade to latest version, or some other version of your wish. And if everything went fine, you will see something like this:

“Everything went smooth. Have fun with your new WordPress version!”

Don’t forget to check your WordPress carefully after upgrading. In case of my blogs the instant upgrade with these blogs has produced no errors. I have done upgrades form 2.2 and 2.2 version to 2.3.1 no troubles so far.

In the next time I’ll tell you about other Cool WordPress Plug-Ins.

Be Sociable, Share!

•