Upgrade

 · 1.4.x to any higher version
 · 1.3.7 to 1.4.x or any higher version

---

1.4.x to any higher version

Basically one copies the source code files over an existing installation.

1. Clear the cache in your current installation.
2. Unzip the new PWP archive into a new directory.
3. Copy the new source files over your existing installation:-
   • wiki/core/*.inc
   • wiki/resp/*/*.inc (with all sub directories)
   • wiki/run.php
   • wiki/run.debug.php (if applicable)

Additionally, check the Configuration description for changes. In general, you may also continue to use your old config file as it is. But you might miss some new features.

The style sheet was extended for PWP 1.5.0 for the left/right hand side menu.

1.3.7 to 1.4.x or any higher version

Who should upgrade?

If you are satisfied with your current version and you do not miss any of the new features or text rules simply stay where you are.

There are a few incompatibilities to PWP 1.3.x which are enumerated below. Generally, you can continue to work with all your collected Wiki pages.

DEFINITION LISTS:

The text rule for definition lists has changed from ";;Term;;Definition;;"
to ";Term:Definition" and ";;Term:Definition". This was made to get closer
to the UseMod syntax and to have a similar handling for all three list types.
You have to adjust your definition lists manually - I doubt that they are
widely used. (Sorry to the ones protesting now!)

WIKI PAGE NAMES:

You might have been able to create Wiki pages with names including some
special chars like quotation marks. This will not work any longer. You have
to rename the files in the file system. If your Wiki page names only include
word characters, numbers, dots and the underscore, you are on the safe side.
From 1.4 on you can include Non-ASCII characters like "Ä" (Auml;) in
Wiki page names - as long as your file system and your webserver
will work with such file names. Names starting with a dot "." are
considered to be illegal.

CONFIG FILE ENTRIES:

The config file has changed. Make a copy of your old config file
and transport the changes by copy'n'paste after updating. The
setting "IsProductive" became obsolete. You may call
"run.debug.php" instead of "run.php" to use logging and introspection.

STYLE SHEET:

The default style sheet had to be extended by the classes ".layout"
for tables. It has new settings for "select", too.
You can now include the standard style sheet and override its settings
by providing a second style sheet containing your custom changes.

CONFIG: STATICHTML.INC:

Because of the changes in the style sheet config settings (whole tag instead
of a file name) there are changes in the file "wiki/conf/StaticHtml.inc"
to be done. Copy the tag from PWP 1.4 into your customized file.

ICON NAMES:

All icons shipping with 1.4 have new names. You can either adapt the
new names (which is simple if you've combined icons and variables) or
you can extract the old icon set from PWP 1.3.7.

OLD FORCED LINE BREAK:

There is no support for the "-->" line break rule any longer. This rule
was deprecated in PWP 1.3.4. Line breaks "-->" were silently converted
into " -_ " on each save operation in higher releases. If you still  
have old style line breaks, replace them manually.

How can I upgrade from 1.3.x?

Unlike the updates described above, one has to move the data into a new installation instead of updating the source code files.

1. Install the new version parallel.
2. Import your old config settings by editing the corresponding files in both, your old 1.3.x release and your new release.
3. Copy your style sheet and your images into the new PWP release
4. Copy your data, history and upload directory contents into the new PWP release
5. Test your new PWP installation.
6. Remove your old installation after a few days.