Print

[mgraf]

Been reading up on converting my 1.3.1 gallery to 1.4.2...  I have quite a few theme changes to make, as well as transfer of my shopping cart configuration, and my use of watermarks.   I am already planning on using WinMerge to track them all down, but still worried something may go wrong in the upgrade process.

I am just wondering if you can create 2 running versions of Coppermine on the same site?  So I could debug and test the upgrade, while letting my 1.3.1 version run live.   

Would this just be a matter of duplicating my current SQL database to a new name, and then performing the 1.4 upgrade on it?

Am I also correct in understanding that watermarks cannot be transferred from my usage in 1.3.1 to work in 1.4.2?   I am using the mod that applies the mark over the top of the image on display, but doesn't actually modify the original image file.  I prefer to keep it this way.

My gallery is at:  http://www.grafphoto.com/gallery/index.php

Thanks much!

Mark

[kegobeer]

You can install 1.4.2 next to your 1.3.x gallery.  Just make sure the table prefixes are different (should be ok, as your tables are probably cpg13x_) and the cookie names are different.  That's for a fresh install, however.

For your situation, I would use phpMyAdmin to make copies of your current tables and then change the table prefix to cpg142_.  Duplicate your Coppermine directory and call it something easy to remember, like cpg142.  Edit your config.inc.php file to point to the correct tables (change the table prefix entry).  Use phpMyAdmin and edit your new cpg142_config table - update your ecards_more_pic_target and cookie entries to reflect the new location and the new cookie name.

Clear your cookies, then try to access your newly copied site.  If everything works, upload the new 1.4.2 files to your test site and perform the upgrade.

As always, make sure to back up your database and critical files before proceeding.

[mgraf]

Maybe I am not understanding correctly, but are you suggesting going in and modifying my existing SQL database with 142 prefixes, or creating a new SQL database?   I haven't really dabbled too much in data within the database other than input through coppermine.

[Tranz]

You can put a copy of the current tables in a new database where you won't need to change the prefix. If you put them in the same database, they need to have different prefixes to avoid conflict.

[kegobeer]

I don't recommend going forward until you have more experience with MySQL and phpMyAdmin.  Start with Google and read everything you can.  If you plan on experimenting, you need to know what tools you'll have to use and how to use them.