Revision history for UpgradeNotes
Additions:
~- **[[Installing12 Notes on upgrading to 1.2]]**
>>Upgrading a wiki to the [[WhatsNew | latest version]] of Wikka is done via a web wizard and only takes a few minutes. However there are a few points to bear in mind when upgrading, in particular if your wiki has custom extensions or code modifications. Before upgrading make sure you read the specific **[[Installing12 | instructions]]** for the version you are upgrading to.
>>Upgrading a wiki to the [[WhatsNew | latest version]] of Wikka is done via a web wizard and only takes a few minutes. However there are a few points to bear in mind when upgrading, in particular if your wiki has custom extensions or code modifications. Before upgrading make sure you read the specific **[[Installing12 | instructions]]** for the version you are upgrading to.
Deletions:
>>Upgrading a wiki to the [[WhatsNew | latest version]] of Wikka is done via a web wizard and only takes a few minutes. However there are a few points to bear in mind when upgrading, in particular if your wiki has custom extensions or code modifications.
Additions:
~- **[[Installing12 | Notes on upgrading to 1.2]]**
Deletions:
Additions:
~- [[InstallingPlugins | How to use the plugins folder]]
Deletions:
Additions:
~-~- [[InstallingPlugins | How to use the plugins folder]]
~- **[[Installing1167 | Notes on upgrading to 1.1.6.7]]**
~- **[[Installing1167 | Notes on upgrading to 1.1.6.7]]**
Deletions:
Additions:
>>==See also==
~-**[[Installing1166 | Notes on upgrading to 1.1.6.6]]**
>>Upgrading a wiki to the [[WhatsNew | latest version]] of Wikka is done via a web wizard and only takes a few minutes. However there are a few points to bear in mind when upgrading, in particular if your wiki has custom extensions or code modifications.
~-**[[Installing1166 | Notes on upgrading to 1.1.6.6]]**
>>Upgrading a wiki to the [[WhatsNew | latest version]] of Wikka is done via a web wizard and only takes a few minutes. However there are a few points to bear in mind when upgrading, in particular if your wiki has custom extensions or code modifications.
Deletions:
No Differences
Deletions:
Additions:
Upgrading a wiki to the [[WhatsNew | latest version]] of Wikka is done via a web wizard and only takes a few minutes. However there are a few points to bear in mind when upgrading, in particular if your wiki has custom extensions or code modifications.
Deletions:
~- [[Installing1164 | Installation & upgrade notes for 1.1.6.4]]
>>Upgrading a wiki to the [[WhatsNew | latest version]] of Wikka is done via a web wizard and only takes a few minutes. However there are a few points to bear in mind when upgrading, in particular if your wiki has custom extensions or code modifications.
Additions:
>>==See also:==
~- [[Installing1164 | Installation & upgrade notes for 1.1.6.4]]
>>Upgrading a wiki to the [[WhatsNew | latest version]] of Wikka is done via a web wizard and only takes a few minutes. However there are a few points to bear in mind when upgrading, in particular if your wiki has custom extensions or code modifications.
~- [[Installing1164 | Installation & upgrade notes for 1.1.6.4]]
>>Upgrading a wiki to the [[WhatsNew | latest version]] of Wikka is done via a web wizard and only takes a few minutes. However there are a few points to bear in mind when upgrading, in particular if your wiki has custom extensions or code modifications.
Deletions:
===Upgrade notes===
~-{{since version="1.1.6.4" display="inline"}} the template files (##header.php## and ##footer.php##) can be found in a dedicated directory called ##/templates## If you made any modifications to the original files (in the ##/actions## directory), you will need to apply these changes to the new files.
Additions:
~-{{since version="1.1.6.4" display="inline"}} the template files (##header.php## and ##footer.php##) can be found in a dedicated directory called ##/templates## If you made any modifications to the original files (in the ##/actions## directory), you will need to apply these changes to the new files.
Deletions:
Additions:
===Upgrade notes===
~-{{since version="1.1.6.4" display="inline"} the template files (##header.php## and ##footer.php##) can be found in a dedicated directory called ##/templates## If you made any modifications to the original files (in the ##/actions## directory), you will need to apply these changes to the new files.
~-{{since version="1.1.6.4" display="inline"} the template files (##header.php## and ##footer.php##) can be found in a dedicated directory called ##/templates## If you made any modifications to the original files (in the ##/actions## directory), you will need to apply these changes to the new files.
Additions:
<<For older versions of Wikka that have no custom modifications at all, and which didn't use file uploads.<<::c::
<<For older versions of Wikka with extra plugins, extensions and file uploads.<<::c::
<<For older versions of Wikka with extra plugins, extensions and file uploads.<<::c::
Deletions:
>>For older versions of Wikka with extra plugins, extensions and file uploads.>>::c::
Additions:
Wikka releases are upgrade tested before release, **but**, for your protection, backup all your Wikka files **and** the Wikka MySQL tables before upgrading. Backups are particularly important when restoring custom extensions after upgrading (see notes below).
====Step 2: Select your upgrade method ====
~1) If you made modifications to files that are part of a Wikka distribution, these modifications will be lost when overwriting the files. This applies in particular to template files (e.g. ##header.php## and ##footer.php##) and stylesheets. If you made a backup before the upgrade (step 1), you will be able to restore specific modifications after the files have been overwritten by the installer. If you restore your custom ##wikka.css## stylesheet after upgrading following method B, consider that there might be changes (e.g. new CSS selectors and settings) that need to be included in the stylesheet for Wikka to display properly.
====Step 2: Select your upgrade method ====
~1) If you made modifications to files that are part of a Wikka distribution, these modifications will be lost when overwriting the files. This applies in particular to template files (e.g. ##header.php## and ##footer.php##) and stylesheets. If you made a backup before the upgrade (step 1), you will be able to restore specific modifications after the files have been overwritten by the installer. If you restore your custom ##wikka.css## stylesheet after upgrading following method B, consider that there might be changes (e.g. new CSS selectors and settings) that need to be included in the stylesheet for Wikka to display properly.
Deletions:
====Step 2: select your upgrade method ====
~1) If you made modifications to files that are part of a Wikka distribution, these modifications will be lost when overwriting the files. This applies in particular to template files (e.g. ##header.php## and ##footer.php##) and stylesheets. If you restore your custom ##wikka.css## stylesheet after upgrading following method B, consider that there might be changes (e.g. new CSS selectors and settings) that need to be included in the stylesheet for Wikka to display properly.
Additions:
~1) If you made modifications to files that are part of a Wikka distribution, these modifications will be lost when overwriting the files. This applies in particular to template files (e.g. ##header.php## and ##footer.php##) and stylesheets. If you restore your custom ##wikka.css## stylesheet after upgrading following method B, consider that there might be changes (e.g. new CSS selectors and settings) that need to be included in the stylesheet for Wikka to display properly.
Deletions:
Additions:
Upgrading a wiki to the [[WhatsNew | latest version]] of Wikka is done via a web wizard and only takes a few minutes. However there are a few points to bear in mind when upgrading, in particular if your wiki has custom extensions or code modifications.
Additions:
===Tips===
If you have a high-traffic site, it is recommended that you **lock your site first**. Simply create a file called locked in the directory Wakka is located in. This file should contain a (plain text) password on its first line. When you go to your Wakka site, it will then ask you for a user name and password -- enter ##admin##as the user name and the password in your locked file as the password. **When you're done with upgrading, you should remove the locked file again.**
If you have a high-traffic site, it is recommended that you **lock your site first**. Simply create a file called locked in the directory Wakka is located in. This file should contain a (plain text) password on its first line. When you go to your Wakka site, it will then ask you for a user name and password -- enter ##admin##as the user name and the password in your locked file as the password. **When you're done with upgrading, you should remove the locked file again.**
Deletions:
If you have a high-traffic site, it is recommended that you **lock your site first**. Simply create a file called locked in the directory Wakka is located in. This file should contain a (plain text) password on its first line. When you go to your Wakka site, it will then ask you for a user name and password -- enter "admin" as the user name and the password in your locked file as the password. **When you're done with upgrading, you should remove the locked file again.**
Additions:
====Step 1: Backup, backup, backup! ====
====Step 2: select your upgrade method ====
1) For Wikka instances //with no custom modifications// at all (very rare cases), **Method A** should be best : it's the simple "delete & replace" method. If you haven't hacked wikka's code, this method is for you. If you have changed the code, or if you used the "file upload" action, this method is risky because the wiki admin could lose data like file uploads, as well as any custom mods.
1) For Wikka instances //with custom extensions//, plugins or file uploads, **Method B** (the overwrite method) is highly recommended. It should be made clear that using the overwrite method may leave useless files in the Wikka directory if the installer does not explicitly remove them. Note that some custom extensions may not work any more if they are not compliant with the new Wikka version.
===Method A: delete old files & replace with a fresh installation ===
===Method B: overwrite a previous installation===
1) Upload all the files and subfolders in the latest Wikka release file to the Wikka installation directory on your web server by selecting the **overwrite** mode on your FTP client. [see notes]
==Notes:==
~1) Make sure you upload the Wikka files into the correct directory. For example, if your Wikka directory is ##/public_html/wikka##, upload the Wikka files and subdirectories **in** the Wikka directory into the ##/public_html/wikka## directory..... do not upload the Wikka **directory** itself into the Wikka directory. Otherwise, your installation will be in: ##/public_html/wikka/wikka/##. See the difference?
~1) If you made modifications to files that are part of a Wikka distribution, these modifications will be lost when overwriting the files. This applies in particular to stylesheets. If you restore your custom ##wikka.css## stylesheet after upgrading following method B, consider that there might be changes (e.g. new CSS selectors and settings) that need to be included in the stylesheet for Wikka to display properly.
====Step 2: select your upgrade method ====
1) For Wikka instances //with no custom modifications// at all (very rare cases), **Method A** should be best : it's the simple "delete & replace" method. If you haven't hacked wikka's code, this method is for you. If you have changed the code, or if you used the "file upload" action, this method is risky because the wiki admin could lose data like file uploads, as well as any custom mods.
1) For Wikka instances //with custom extensions//, plugins or file uploads, **Method B** (the overwrite method) is highly recommended. It should be made clear that using the overwrite method may leave useless files in the Wikka directory if the installer does not explicitly remove them. Note that some custom extensions may not work any more if they are not compliant with the new Wikka version.
===Method A: delete old files & replace with a fresh installation ===
===Method B: overwrite a previous installation===
1) Upload all the files and subfolders in the latest Wikka release file to the Wikka installation directory on your web server by selecting the **overwrite** mode on your FTP client. [see notes]
==Notes:==
~1) Make sure you upload the Wikka files into the correct directory. For example, if your Wikka directory is ##/public_html/wikka##, upload the Wikka files and subdirectories **in** the Wikka directory into the ##/public_html/wikka## directory..... do not upload the Wikka **directory** itself into the Wikka directory. Otherwise, your installation will be in: ##/public_html/wikka/wikka/##. See the difference?
~1) If you made modifications to files that are part of a Wikka distribution, these modifications will be lost when overwriting the files. This applies in particular to stylesheets. If you restore your custom ##wikka.css## stylesheet after upgrading following method B, consider that there might be changes (e.g. new CSS selectors and settings) that need to be included in the stylesheet for Wikka to display properly.
Deletions:
If you experience any issues with upgrading, leave feedback on this page or use the form below.
===Step 2: select your upgrade method ===
1) For Wikka instances with no custom modifications at all (very rare cases), **Method A** should be best : it's the simple "delete & replace" method. If you haven't hacked wikka's code, this method is for you. If you have changed the code, or if you used the "file upload" action, this method is risky because the wiki admin could lose data like file uploads, as well as any custom mods.
1) For Wikka instances with custom extensions, plugins or file uploads, **Method B** (the overwrite method) is highly recommended. It should be made clear that using the overwrite method may leave useless files in the Wikka directory if the installer does not explicitly remove them.
==Method A: delete old files & replace with a fresh installation ==
==or Method B: overwrite a previous installation==
1) Upload all the files and subfolders in the latest Wikka release file to the Wikka installation directory on your web server by selecting the **overwrite** mode on your FTP client. [Note *]
* **Note:** Make sure you upload the Wikka files into the correct directory. For example, if your Wikka directory is //##/public_html/wikka##//, upload the Wikka files and subdirectories **in** the Wikka directory into the //##/public_html/wikka##// directory..... do not upload the Wikka **directory** itself into the Wikka directory. Otherwise, your installation will be in: //##/public_html/wikka/wikka/##//. See the difference?
Additions:
=====Upgrading Wikka to the latest release=====
There are two methods to upgrade Wikka, but both begin with Step 1.
===Step 1: Backup, backup, backup! ===
Wikka releases are upgrade tested before release, **but**, for your protection, backup all your Wikka files **and** the Wikka MySQL tables before upgrading.
===Step 2: select your upgrade method ===
1) For Wikka instances with no custom modifications at all (very rare cases), **Method A** should be best : it's the simple "delete & replace" method. If you haven't hacked wikka's code, this method is for you. If you have changed the code, or if you used the "file upload" action, this method is risky because the wiki admin could lose data like file uploads, as well as any custom mods.
1) For Wikka instances with custom extensions, plugins or file uploads, **Method B** (the overwrite method) is highly recommended. It should be made clear that using the overwrite method may leave useless files in the Wikka directory if the installer does not explicitly remove them.
==Method A: delete old files & replace with a fresh installation ==
>>For older versions of Wikka that have no custom modifications at all, and which didn't use file uploads.>>::c::
1) Make a backup of your Wikka Wiki directory and MySQL data (see Step 1 above).
1) Delete all of the files and subfolders in the Wikka directory **except ##wikka.config.php##**. This is the only file that you need: it contains the information necessary to connect to your MySQL database.
1) Point a web browser at the URL for your Wikka Wiki site. The web-based updater will appear (instead of your site) and the Wikka upgrade script will run.
==or Method B: overwrite a previous installation==
>>For older versions of Wikka with extra plugins, extensions and file uploads.>>::c::
1) Make a backup of your Wikka Wiki directory and MySQL data (see Step 1 above).
1) Upload all the files and subfolders in the latest Wikka release file to the Wikka installation directory on your web server by selecting the **overwrite** mode on your FTP client. [Note *]
1) Start your favorite web browser and point it at the Wikka installation directory. The web-based updater will appear (instead of your site): look it over and make any desired changes, then click Continue at the bottom of the page.
* **Note:** Make sure you upload the Wikka files into the correct directory. For example, if your Wikka directory is //##/public_html/wikka##//, upload the Wikka files and subdirectories **in** the Wikka directory into the //##/public_html/wikka##// directory..... do not upload the Wikka **directory** itself into the Wikka directory. Otherwise, your installation will be in: //##/public_html/wikka/wikka/##//. See the difference?
==Tips==
If you have a high-traffic site, it is recommended that you **lock your site first**. Simply create a file called locked in the directory Wakka is located in. This file should contain a (plain text) password on its first line. When you go to your Wakka site, it will then ask you for a user name and password -- enter "admin" as the user name and the password in your locked file as the password. **When you're done with upgrading, you should remove the locked file again.**
There are two methods to upgrade Wikka, but both begin with Step 1.
===Step 1: Backup, backup, backup! ===
Wikka releases are upgrade tested before release, **but**, for your protection, backup all your Wikka files **and** the Wikka MySQL tables before upgrading.
===Step 2: select your upgrade method ===
1) For Wikka instances with no custom modifications at all (very rare cases), **Method A** should be best : it's the simple "delete & replace" method. If you haven't hacked wikka's code, this method is for you. If you have changed the code, or if you used the "file upload" action, this method is risky because the wiki admin could lose data like file uploads, as well as any custom mods.
1) For Wikka instances with custom extensions, plugins or file uploads, **Method B** (the overwrite method) is highly recommended. It should be made clear that using the overwrite method may leave useless files in the Wikka directory if the installer does not explicitly remove them.
==Method A: delete old files & replace with a fresh installation ==
>>For older versions of Wikka that have no custom modifications at all, and which didn't use file uploads.>>::c::
1) Make a backup of your Wikka Wiki directory and MySQL data (see Step 1 above).
1) Delete all of the files and subfolders in the Wikka directory **except ##wikka.config.php##**. This is the only file that you need: it contains the information necessary to connect to your MySQL database.
1) Point a web browser at the URL for your Wikka Wiki site. The web-based updater will appear (instead of your site) and the Wikka upgrade script will run.
==or Method B: overwrite a previous installation==
>>For older versions of Wikka with extra plugins, extensions and file uploads.>>::c::
1) Make a backup of your Wikka Wiki directory and MySQL data (see Step 1 above).
1) Upload all the files and subfolders in the latest Wikka release file to the Wikka installation directory on your web server by selecting the **overwrite** mode on your FTP client. [Note *]
1) Start your favorite web browser and point it at the Wikka installation directory. The web-based updater will appear (instead of your site): look it over and make any desired changes, then click Continue at the bottom of the page.
* **Note:** Make sure you upload the Wikka files into the correct directory. For example, if your Wikka directory is //##/public_html/wikka##//, upload the Wikka files and subdirectories **in** the Wikka directory into the //##/public_html/wikka##// directory..... do not upload the Wikka **directory** itself into the Wikka directory. Otherwise, your installation will be in: //##/public_html/wikka/wikka/##//. See the difference?
==Tips==
If you have a high-traffic site, it is recommended that you **lock your site first**. Simply create a file called locked in the directory Wakka is located in. This file should contain a (plain text) password on its first line. When you go to your Wakka site, it will then ask you for a user name and password -- enter "admin" as the user name and the password in your locked file as the password. **When you're done with upgrading, you should remove the locked file again.**
Deletions:
==Backup, backup, backup! ==
Wikka releases are upgrade tested before release, **but**, for your protection, backup all your Wikka files and the Wikka MySQL tables before upgrading.
>>If you have a high-traffic site, it is recommended that you **lock your site first**. Simply create a file called locked in the directory Wakka is located in. This file should contain a (plain text) password on its first line. When you go to your Wakka site, it will then ask you for a user name and password -- enter "admin" as the user name and the password in your locked file as the password. **When you're done with upgrading, you should remove the locked file again.**>>== Instructions ==
1) Upload all the files and subfolders in the latest Wikka release file to the Wikka installation directory on your web server. Overwrite existing Wikka files. [Note *]
1) Start [[http://www.mozilla.org/products/firefox/ | your favorite web browser]] and point it at the Wikka installation directory.
1) The web-based updater will appear (instead of your site): look it over and make any desired changes, then click Continue at the bottom of the page.
1) That's it.
== Alternative instructions: ==
1) Delete all of the files and subfolders in the Wikka directory **except wikka.config.php**. This is the only file that you need.
1) Read step 3 again -- do not delete the ##[[ConfigurationOptions | wikka.config.php]]## file.
1) Point a web browser at the URL for your Wikka Wiki site: The web-based updater will appear (instead of your site) and the Wikka upgrade script will run.
* **Note:** Make sure you upload the Wikka files into the correct directory. For example, if your Wikka directory is //##/public_html/wikka##//, upload the Wikka files and subdirectories into the //##/public_html/wikka##// directory..... do not upload the Wikka **directory** into the Wikka directory so that it looks like this: //##/public_html/wikka/wikka/##//. See the difference? In other words, when you select the files in your FTP client, browse **into** the Wikka release directory and select all files and folders, then upload.
- What's the difference between the two methods above?
- In the first set of intructions you are only uploading new files over the old files.
- In the second set, you are cleaning out old, potentially unneeded files.
Additions:
HomePage
1) Upload all the files and subfolders in the latest Wikka release file to the Wikka installation directory on your web server. Overwrite existing Wikka files. [Note *]
1) Read step 3 again -- do not delete the ##[[ConfigurationOptions | wikka.config.php]]## file.
1) Upload all the files from the latest Wikka release into the Wikka directory. [Note *]
* **Note:** Make sure you upload the Wikka files into the correct directory. For example, if your Wikka directory is //##/public_html/wikka##//, upload the Wikka files and subdirectories into the //##/public_html/wikka##// directory..... do not upload the Wikka **directory** into the Wikka directory so that it looks like this: //##/public_html/wikka/wikka/##//. See the difference? In other words, when you select the files in your FTP client, browse **into** the Wikka release directory and select all files and folders, then upload.
CategoryEN
1) Upload all the files and subfolders in the latest Wikka release file to the Wikka installation directory on your web server. Overwrite existing Wikka files. [Note *]
1) Read step 3 again -- do not delete the ##[[ConfigurationOptions | wikka.config.php]]## file.
1) Upload all the files from the latest Wikka release into the Wikka directory. [Note *]
* **Note:** Make sure you upload the Wikka files into the correct directory. For example, if your Wikka directory is //##/public_html/wikka##//, upload the Wikka files and subdirectories into the //##/public_html/wikka##// directory..... do not upload the Wikka **directory** into the Wikka directory so that it looks like this: //##/public_html/wikka/wikka/##//. See the difference? In other words, when you select the files in your FTP client, browse **into** the Wikka release directory and select all files and folders, then upload.
CategoryEN
Deletions:
1) Upload all the files and subfolders in the latest Wikka release file to the Wikka installation directory on your web server. Overwrite existing Wikka files. *
1) Read step 3 again -- do not delete the wikka.config.php file.
1) Upload all the files from the latest Wikka release into the Wikka directory. *
* **Note:** Make sure you upload the Wikka files into the correct directory. For example, if your Wikka directory is /public_html/wikka, upload the Wikka files and subdirectories into the /public_html/wikka directory..... do not upload the Wikka **directory** into the Wikka directory so that it looks like this: /public_html/wikka/wikka/. See the difference? In other words, when you select the files in your FTP client, browse **into** the Wikka release directory and select all files and folders, then upload.
Any questions?
Q: Is the table structure the same as WakkaWiki 0.1.2 ? Is it possible to upgrade to Wikka by simply overwriting the previous wakka installation? -- DarTar
A: Yes, it is possible to upgrade by overwriting. See UpgradingFromWakkaWiki for more info. -- JsnX
CategoryDocumentation
