/*
    Pagetool
    Copyright 2001,2002 Pagetool Development Team
    pagetool-user@lists.sourceforge.net http://www.pagetool.org/
    $Id: UPGRADE.txt,v 1.8 2004/11/10 23:57:52 daveguerin Exp $
*/

[1.06 to 1.07]
You do not need to run the setup script to update. Simply copy the src directory 
over your existing source directory. There are no table changes from Pagetool 
version 1.00.



[1.05 to 1.07]
You do not need to run the setup script to update. Simply copy the src directory 
over your existing source directory. There are no table changes from Pagetool 
version 1.00.



[1.04 to 1.07]
You do not need to run the setup script to update. Simply copy the src directory 
over your existing source directory. There are no table changes from Pagetool 
version 1.00.



[1.03 to 1.07]
You do not need to run the setup script to update. Simply copy the src directory 
over your existing source directory. There are no table changes from Pagetool 
version 1.00.



[1.02 to 1.07]
You do not need to run the setup script to update. Simply copy the src directory 
over your existing source directory. There are no table changes from Pagetool 
version 1.00.



[1.01 to 1.07]
You do not need to run the setup script to update. Simply copy the src directory 
over your existing source directory. There are no table changes from Pagetool 
version 1.00. See CHANGELOG.txt for information about how Auto_HTML pages are 
now treated as this may affect the look of your site.



[1.00 to 1.07]
You do not need to run the setup script to update. Simply copy the src directory 
over your existing source directory. There are no table changes from Pagetool 
version 1.00. See CHANGELOG.txt for information about how Auto_HTML pages are 
now treated as this may affect the look of your site.



[1.02 to 1.07]
You do not need to run the setup script to update. Simply copy the src directory 
over your existing source directory. There are no table changes from Pagetool 
version 1.00. See CHANGELOG.txt for information about how Auto_HTML pages are 
now treated as this may affect the look of your site.



[1.01 to 1.07]
You do not need to run the setup script to update. Simply copy the src directory 
over your existing source directory. There are no table changes from Pagetool 
version 1.00. See CHANGELOG.txt for information about how Auto_HTML pages are 
now treated as this may affect the look of your site.



[1.00 to 1.07]
You do not need to run the setup script to update. Simply copy the src directory 
over your existing source directory. There are no table changes from Pagetool 
version 1.00. See CHANGELOG.txt for information about how Auto_HTML pages are 
now treated as this may affect the look of your site.



[1.00.0pre1 to 1.07]
You do not need to run the setup script to update. Simply copy the src directory 
over your existing source directory. There are no table changes from Pagetool 
version 1.00. See CHANGELOG.txt for information about how Auto_HTML pages are 
now treated as this may affect the look of your site.



[0.11.1 to 1.07]
You do not need to run the setup script to update. Simply copy the src directory 
over your existing source directory. There are no table changes from Pagetool 
version 1.00. See CHANGELOG.txt for information about how Auto_HTML pages are 
now treated as this may affect the look of your site. Also the character set 
parameter is now stored in the pt_config.inc file - so you can change it from 
the default ISO to UTF or whatever you want. See the sample pt_config.inc in 
src/setup/sample/ for details of the variable to be added.



[0.11.0 to 1.07]
You do not need to run the setup script to update. Simply copy the src directory 
over your existing source directory. There are no table changes from Pagetool 
version 1.00. See CHANGELOG.txt for information about how Auto_HTML pages are 
now treated as this may affect the look of your site. Also the character set 
parameter is now stored in the pt_config.inc file - so you can change it from 
the default ISO to UTF or whatever you want. See the sample pt_config.inc in 
src/setup/sample/ for details of the variable to be added. Versions after 0.11.0 
use there own style sheet! It's called style.php. It uses phpSniff to do some 
browser detection. You don't have to use it, but if you do, you will need to add 
the following code to the head code section of your active profile:

<link rel="stylesheet" href="style.php" type="text/css">

Also - the system messages (file not found, search results, etc), all use style 
sheets to format their display rather than the old $ptconf["header1open"] style 
tags. So, if you are using your own style sheets, you will need to add header1, 
header2, header3,text1 text2, and text3 classes so that these system messages 
display properly.



[0.11.0pre1 to 1.07]
You do not need to run the setup script to update. Simply copy the src directory 
over your existing source directory. There are no table changes from Pagetool 
version 1.00. See CHANGELOG.txt for information about how Auto_HTML pages are 
now treated as this may affect the look of your site. Also the character set 
parameter is now stored in the pt_config.inc file - so you can change it from 
the default ISO to UTF or whatever you want. See the sample pt_config.inc in 
src/setup/sample/ for details of the variable to be added. Versions after 0.11.0 
use there own style sheet! It's called style.php. It uses phpSniff to do some 
browser detection. You don't have to use it, but if you do, you will need to add 
the following code to the head code section of your active profile:

<link rel="stylesheet" href="style.php" type="text/css">

Also - the system messages (file not found, search results, etc), all use style 
sheets to format their display rather than the old $ptconf["header1open"] style 
tags. So, if you are using your own style sheets, you will need to add header1, 
header2, header3,text1 text2, and text3 classes so that these system messages 
display properly.



[0.10.2 to 1.07]
You do not need to run the setup script to update. Simply copy the src directory 
over your existing source directory. There are no table changes from Pagetool 
version 1.00. See CHANGELOG.txt for information about how Auto_HTML pages are 
now treated as this may affect the look of your site. Also the character set 
parameter is now stored in the pt_config.inc file - so you can change it from 
the default ISO to UTF or whatever you want. See the sample pt_config.inc in 
src/setup/sample/ for details of the variable to be added. Versions after 0.11.0 
use there own style sheet! It's called style.php. It uses phpSniff to do some 
browser detection. You don't have to use it, but if you do, you will need to add 
the following code to the head code section of your active profile:

<link rel="stylesheet" href="style.php" type="text/css">

Also - the system messages (file not found, search results, etc), all use style 
sheets to format their display rather than the old $ptconf["header1open"] style 
tags. So, if you are using your own style sheets, you will need to add header1, 
header2, header3,text1 text2, and text3 classes so that these system messages 
display properly.



[0.10.1 to 1.07]
Upgrading is only supported for versions 0.10.1 or higher. If you are upgrading 
from a previous version - first upgrade to 0.10.1 then upgrade to version 1. 
Versions after 0.11.0 use there own style sheet! It's called style.php. It uses 
phpSniff to do some browser detection. You don't have to use it, but if you do, 
you will need to add the following code to the head code section of your active 
profile:

<link rel="stylesheet" href="style.php" type="text/css">

Also - the system messages (file not found, search results, etc), all use style 
sheets to format their display rather than the old $ptconf["header1open"] style 
tags. So, if you are using your own style sheets, you will need to add header1, 
header2, header3,text1 text2, and text3 classes so that these system messages 
display properly.

Before you do anything, back up everything in you Pagetool directory and backup 
your Pagetool database.

Next, ftp the src directory over your existing src directory and create a 
directory called plugins in the root of your www directory (should be 
side-by-side with your media directory and src directory)..

Next delete your pt_config.inc, test.php, and index.php so that the install 
program will be able to re-create them (don't forget to back them up first!).

Run the setup program by pointing your browser to:

http://www.yourserver.org/src/setup/
