Upgrading means migrating your earlier version of Cre Loaded to a more recent version – eg 6.2.x (or 6.3.x) to 6.4.x – where the second and third numbers of the versions are different. Updating means migrating between minor versions – eg 6.4.x to 6.4.x – where the third number differs between the two versions. If you want help with updating, have a read of migrating from 6.4.0 to 6.4.1 here.
The following is an attempt to make the upgrade process a bit easier and is based on an upgrade from Creloaded 6.2 to 6.4.1a.
Before setting off with the Upgrade instructions below, if you currently use the Information infobox and want to upgrade your current 6.2 store’s template, perform the following steps on your existing store:
Switch on Site Maintenance on your store
Admin >> Configuration >> Site Maintenance >> edit True
Set the Information infobox inactive
Admin >> Design Controls >> Infobox Configure and set the Information Infobox inactive (red light)
Check which template is your Default template
Admin >> Design Controls >> Template Manager .. the one in bold is your currently active template.
There are only two ‘stock’ templates supported in Creloaded 6.4.1 – original_ats and cre63_ats. Both use templates/default/boxes for infoboxes.
Original_ats uses templates/content for tpl.php files; cre63_ats keeps its tpl.php files in templates/cre63_ats/content. Any other templates will have their own folder in /templates and might use their own /boxes and/or /content folders too.
Keeping the point above in mind, make sure your template has a file called pages.tpl.php.
If not, go to /templates/content and copy the pages.tpl.php file from there to /templates/your template/content.
- Download your /images and your edited /templates/your template/ folders to your computer
The Cre Loaded Upgrade process is described in Cre’s own Installation pdf but it’s a bit tangled up with the New Installation instructions.
You will need:
- The ‘upgrade zip’ containing catalog.zip and the Installation.pdf (the pdf referred to is dated March 15 2010)
- Access to your server and database manager – possibly through cPanel or your host’s own control panel, or a free (s)ftp programme like Filezilla
- 20-30 minutes
Once the above is together, proceed as follows:
Step One: Create a ‘new_store’ folder on your server
Use the File Manager in cPanel or even Filezilla for this
Step Two: Create a ‘new_store’ database on your mysql server
Use the MySQL Manager through your control panel – make sure to set Privileges for the User correctly too. Record the database name, username, user password and hostname (this may be ‘localhost’) for later use
Step Three: Open the Installation.pdf and go to page 18
There are a couple of ways of getting the catalog.zip onto your server. One way is as Cre suggests, which involves unzipping all of the folders and files in the catalog.zip to your computer and uploading each via (s)ftp. I wouldn’t recommend this because – it becomes a 12MB upload when unzipped (instead of 6MB); there are over 3500 items to be uploaded and if your connection to the server fails at some point, something may be only partially uploaded and corrupted.
If you have a Plesk control panel you probably don’t have the option of extracting a .zip through its file manager, in which case you’d have to upload the extracted files and folders from your computer.
- I’d recommend uploading just the catalog.zip (one file only) to your ‘new_store’ folder and extracting the files on the server. You can do this using Extract from the cPanel File Manager OR if you have command line access, cd to the directory where the catalog.zip is and ‘unzip catalog’ OR ask your host to do this simple process for you.
Step Four: Set Permissions on the unzipped folders and files
There are several folders and files that require permission changes. Once again you can use your control panel or Filezilla (right click on the folder / file >> File Permissions …) to change Permissions.The Installation pdf lists most of the changes required on page 9. Here is the complete list:
These Files and Folders to Read, Write, eXecute (777) for Owner/Group/Public /admin/include/configure.php /debug/shipwire_debug.txt /include/configure.php /includes/header_tags.php /includes/languages/english/mainpage.php /includes/languages/english/header_tags.php (7) /admin/backups /admin/images/graphs /cache /images /images/banners /images/logo /images/events_images /debug /tmp /temp /library - if Pro or B2B (10/11 if Pro or B2B)Note: /debug/shipwire_debug.txt is also required to have Read/Write/Execute by Owner/Group (777) permissions set.
Step Five: The Upgrade Screen
Now turn to page 19 of the Installation pdf to continue with the upgrade instructions. Your screen will look like this:
Just choose the ‘PCI Upgrade’ option here, whether your Store held credit card information or not. It doesn’t make any difference if you try to remove non-existent information.The next screen is a Pre-Install Check …. everything must be green to proceed. If you didn’t correct the Permissions in Step Four, you’ll be seeing red here.
The next screen asks you to confirm the (absolute) pathway to your existing Cre Store that is being upgraded, as per page 20 of the Installation pdf. The follows a check and confirmation of this path (page 21.)
Step Six: Follow the Installation pdf through pages 21 – 28
The rest of the Installation pdf will take you through through Database Settings and Upgrade, PCI Compliance, Summarize your Server Configuration and cover resetting Permissions, Cre Secure and your Payment Modules etc.
Step Seven: Template and Image folder upload
Upload your old store’s /images and /template/your template folders that you downloaded prior to these six steps. Remember to set permissions for these too.
- delete your /Upgrade folder from the server
- check all permissions on files are set to 644 at most (configure files 444) and on folders to 755 (or 757, avoid 777)
- protect your Admin folder
- set up various htaccess protection methods for other folders and files too if possible.