Log in to get access to additional options [close]
EN PL

FAQ

We are in the process of modernizing the FAQ section. Some answers may not be relevant to Quick.Cms and Quick.Cms.Ext v6.x.

How to update Quick.Cms to the latest version?

To move database from older versions to a newer one, you need to follow the instructions below. Check which version do you want to migrate your data from to know where you should start.
Unfortunately there is no converter that would move data directly from an old version to the latest one. If your Quick.Cms version is v2.x and you want to update it to Quick.Cms v5.5 you need to go through all of the following steps.
1. Quick.Cms v2.x to v3.2 migration
  • Download the converter_v2.x-v3.x.zip » file
  • Unzip it, study the installation instructions included and follow them step by step:
    1. Download Quick.Cms v3.2 », copy its content to a new directory, then install.
    2. Copy all files from the "files/" directory in the older version of Quick.Cms v2.x (that you use) to the "files/" directory in the new version.
    3. In the new Quick.Cms v3.2 create a "db_old/" directory and to that directory copy all files from the "db/" directory in the old Quick.Cms v2.x.
    4. Copy the convert_v2.x-v3.x.php file to the main directory of Quick.Cms v3.2 and run it in a browser, for example: "http://your_domain.com/convert_v2.x-v3.x.php"
You should test the script to see if the data were properly copied and that there are no other problems. Some errors might occur that don't interfere with the script itself - ignore them.

List of problems you can encounter and ignore at this point:

  • Errors including: "Notice: Undefined offset: 4 in \core\pages-admin.php on line 34" - you can encounter it in the admin panel in the pages list. The reason for it is that the new version might not include the same menus as the previous version.
Find out more about settings in section 4.
2. Quick.Cms v3.x to v4.2 migration
  • Download the converter_v3.x-v4.x.zip » file
  • Unzip it, study the installation instructions included and follow them step by step:
    1. Download Quick.Cms v4.2 », copy its content to a new directory, then install.
    2. Copy all files from the "files/" directory in the older version of Quick.Cms v3.x (that you use) to the "files/" directory in the new version.
    3. Copy the converter.php file to the main directory of Quick.Cms v4.2 and run it in a browser, for example: "http://your_domain.com/converter.php"
    4. Once you've run the script follow the instructions you'll see in the browser window:
      1. Create a directory, e.g. "_old/" in your new Quick.Cms main directory, enter the name of the directory to the proper field in the form.
      2. Copy the "db/" directory from the older version to the directory you've just created and click on "next step »"
      3. Check the language field(s), the "copy database" option and click on the "next step »" button.
You should test the script to see if the data were properly copied and that there are no other problems. Some errors might occur that don't interfere with the script itself - ignore them.

List of problems you can encounter and ignore at this point:

  • Errors including: "Notice: Undefined offset: 4 in \core\pages-admin.php on line 34" - you can encounter it in the admin panel in the pages list. The reason for it is that the new version might not include the same menus as the previous version.
Find out more about settings in section 4.
3. Quick.Cms v4.x/v5.x to v5.5 migration
  • Download Quick.Cms v5.5 »
  • To migrate data in this case takes only copying the contents of the "database/" directory (except for the "_fields.php" file and subdirectories) from the older version to the "database/" directory of the new one.
  • Also copy the "files/" directory with all its contents from the old version to the new one.
4. Quick.Cms v4.x or v5.x to v6.x migration
  • Download the convert_v4.x_or_v5.x_to_v6.x.zip »
  • After downloading and unpacking the converter, read the instructions in the "read-me.txt" file.
  • Remember to set thumbnail sizes, image localizations, menu types and other relevant configuration variables in the "database/config.php" files in the new version of your Quick.Cms before migrating the data.
5. Settings
When conversion to the latest version is done, it's time to adjust Quick.Cms's settings.
  • Go to "Tools" -> "Settings" and set all of the fields: Page title, Description, Keywords, Logo, Slogan, Foot info, Login and Password.
  • Input setting available in tabs including: default language and start page.
  • See the manual » to verify variables displayed in the "Initial settings" sections in your script. Compare and set them to values you used in the previous version.
  • If in the older version you used thumbnail sizes and menus that are not defined in the new version, see how to add new menu » or how to add new thumbnail size »
6. Migrating design and code modifications
Design migrate

This stage requires the most work. Before making any changes to graphics we recommend creating a new directory for instance "new" in the "templates" directory of your new script and copy to that location content of the old "templates/default/" directory and in the admin panel set skin to "new".

You'll find the design modification section of the manual » helpful in this process.

If your design is based on a skin downloaded from our website, the entire process could turn out to be much simpler. Just download the skin for the latest version at skins », and modify it to look the way you want it.

Moving PHP code modifications

If modifications were made to PHP code of your website, you'll have to contact the programmer who made these modifications to make the same changes to your new script. Most of the free plugins are available for the latest version of the script, you can find them on the plugins » page.

7. Most common problems after conversion.
We've mentioned before about problems that you might come across after converting your database. They are not serious, but it takes some effort to work them out.
  • Error: "Notice: Undefined offset: 4 in \core\pages-admin.php on line 44" - it happens when a menu that existed in the older version does not exist in the new one. To solve this you can move pages from this non-existing menu to another one.
  • If you can't see thumbnails it's probably because in the old version of the script thumbnail sizes were different to the ones your new script uses. To generate thumbnails in sizes right for the new script you could use a program like IrfanView with it's "Batch conversion" function. You could also go another way. You could go to "database/config/general.php", set the $config['images_sizes'] variable that stores thumbnail sizes to values from the old version.
8. Need help with an update?

Updating your script might be a perfect opportunity to refresh your website's look, update your terms & conditions section (check for any legal inconsistencies), etc.

If you don't have the know-how to do it all or some of it and you don't know anyone who could do it for you, we can offer some suggestions:

  • Check out our partners' » offer if you want to migrate data to the latest version and refresh or make from scratch your website's design.
  • Learn more about our programming customer support » if you just want to migrate data and graphics of your current website to the script's new version. We offer mostly programming services - we are not graphic designers. This solution is perfect for those, who know their way around graphic design, but are not familiar with PHP programming.
Contact us » if you have any more questions or doubts about updating your script.

 
terms and policies about us contact