sorry for asking but How to upgrade 1.3.2 to 1.4 ?

[leblover]

sorry I know , I know I am doing a bad thing by asking a question which shouldnt be asked.
but belive me I searched , and the things whihch I found were confusing.

can you please tell me how I can easily upgrade my 1.3.2 to 1.4 ?

[Joachim Müller]

can you please tell me how I can easily upgrade my 1.3.2 to 1.4 ?

Exactly as suggested in the upgrading section of the documentation that we provide. Not related to installing, but to upgrading. Therefor moving your thread accordingly.

I know I am doing a bad thing by asking a question which shouldnt be asked.

Although cpg1.3.x is outdated and goes unsupported, you're of course welcome to ask questions on how to upgrade (in fact, this type of cpg1.3.x-related questions is the only one allowed). Please do as I suggested above and read the docs.

[leblover]

I am confused with the doc does the doc says, I have to first updage 1.3.2 to 1.3.3 then to 1.3.4 then ... ?

can u copy paste the part is for me ?

[Nibbler]

You already got a direct link to the relevent part

3.4 Upgrading from cpg1.2.x or cpg1.3.x to version cpg1.4.10

    * First, make a backup (dump) of your database.
    * Backup your include/config.inc.php file, your anycontent.php file and your "albums" directory.
    * Unpack the archive
    * If the file install.php exists in the root directory, delete it.
    * Except for the "albums" directory, upload all of the new files and directories making sure not to overwrite the include/config.inc.php file, your anycontent.php file or the albums directory.
    * Delete all leftover, outdated language files in the lang folder that are named XXX-utf-8.php
    * If you have not already done so, create a folder called "edit" within your "albums" directory - this folder will be used by coppermine as a temporary folder, do not ftp-upload files there. Make sure the new "edit"-folder is CHMODed the same way your albums-directory is (755 or 777, depending on your server's config)
    * Run the file "update.php" in the coppermine directory once in your browser (e.g. http://yourdomain.tld/coppermine/update.php). This will update your coppermine install by making all necessary changes in the database.
    * If you have made a custom theme, apply the changes that were introduced in the themes structure to your custom-made theme - refer to the theme-upgrade guide.
    * You can not use language files from older versions of Coppermine as primary language (the language the admin will use) - make sure you only have the language files that come with this package inside of your lang folder (delete or rename all files from older versions within the lang folder).
      If you need to use a language that hasn't been translated for cpg1.4.x, you can try using the language file from cpg1.3.x, however there are certain caveats:
          o You need to enable the language fallback option in coppermine's config page
          o cpg1.4.x-phrases that don't exist in your old language file will go untranslated or show in english
          o Coppermine can't be administered using an old language file - the admin needs to use a "true" cpg1.4.x language file
          o You're free to try using old language files, however when running into issues or error messages, switch to US-English and see if the issue goes away then. Using outdated language files goes unsupported
    * The bridging method has changed from cpg1.3.x to cpg1.4.x. When upgrading, your bridged coppermine install will be unbridged - you will have to re-apply the bridging using the bridge-manager (using your standalone admin account you initially used to set up coppermine). You will not lose anything though, don't worry.

Please note: as there have been changes both in the coppermine files and the database from cpg1.3.0 or better to cpg1.4.x, users of previous versions will have to apply all steps mentioned above: both the files have to be replaced and the update.php script has to be run once.

You can update from 1.3.x to the latest 1.4 in one step.