Upgrades
PmWiki.Upgrades History
Hide minor edits - Show changes to output
August 31, 2011, at 11:58 AM
by -
Changed lines 1-64 from:
ZDiNzH , [url=http://wckooasqfgdk.com/]wckooasqfgdk[/url], [link=http://jixdobldwrjd.com/]jixdobldwrjd[/link], http://xxdhgcledxei.com/
to:
(:Summary:How to upgrade an existing PmWiki installation:)
[[PmWiki]] is designed to make it easy to upgrade the PmWiki software without affecting your existing data files or installation. For most upgrades, you simply copy the files in the new release over your existing installation.
%block bgcolor=#f7f7f7 color=black border='1px solid black' padding=5px% '''Note for PmWiki 1.0 sites:''' Upgrading from 1.0.x to 2.0 requires more than simply copying the 2.0 software over the 1.0 installation. See [[PmWiki:Upgrading From PmWiki 1]] for more details.
!! To upgrade PmWiki:
!!! 1. Read the release notes
If you're upgrading to a new major release (a release where the second number changes, as in going from 0.5.27 to 0.6.0), then carefully read the [[(PmWiki:)ReleaseNotes]] before performing an upgrade to see if there are any significant changes or preparation tasks that must be handled before performing the upgrade. Upgrading from a beta version of 2.0 is quite easy, but taking a look at the 2.0 [[(PmWiki:)ReleaseNotes]] doesn't hurt.
!!! 2. Backup
It's ''always'' a good idea to have a [[(PmWiki:)backup (And Restore)]] copy of your existing PmWiki installation before starting. You can copy the entire directory containing your existing installation, or you can just make copies of the ''wiki.d/'' directory and any other local customization files you may have created (e.g., ''config.php'', ''localmap.txt'', etc.).
!!! 3. Download and extract
Download the version of PmWiki that you want from the [[(PmWiki:)download]] page.
Extract the tar image using @@tar -xvzf ''tgzfile''@@, where ''tgzfile'' is the tar file you downloaded above. This will create a @@pmwiki-x.y.z@@ directory with the new version of the software.
!!! 4. Copy
Copy the files in @@pmwiki-x.y.z@@ over the files of your existing PmWiki installation. For example, if your existing PmWiki installation is in a directory called ''pmwiki'', then one way to copy the new files over the existing ones is to enter the command:
->@@cp -a pmwiki-x.y.z/. pmwiki@@
Note that BSD systems will not have the -a option as a command-line argument for ''cp'', but that's okay, since it's just shorthand for ''cp -dpR'', so use that instead of ''-a''.
On (some) [=FreeBSD=] servers and Mac OS X systems you need to use
->@@cp -Rpv pmwiki-x.y.z/. pmwiki@@
!!! 5. Update customisations and recipes
That's it! Your base PmWiki installation is complete.
Now use the [[PmWiki:Site Analyzer]] to determine which recipes could be updated to the most recent version.
Unless you have made customizations to the ''pmwiki.php'' script or to the files in ''scripts/'', your PmWiki installation should continue to run correctly! (Changes to these files are {+not+} recommended).
([[Local customizations]] should go in ''local/config.php'', ''pub/css'', and ''pub/skins/''yourskinname)
'''Note''': Additional tips can be found on the [[PmWiki:Troubleshooting]] page.
>>faq<< [[#faq]]
Q: How can I determine what version of PmWiki I'm running now?
A: See [[version]] - {Version$:Summary}.
Q: How can I test a new version of PmWiki on my wiki without changing the prior version used by visitors?
A: The easy way to do this is to install the new version in a separate
directory, and for the new version set (in local/config.php):
[@
$WikiLibDirs = array(&$WikiDir,
new PageStore('/path/to/existing/wiki.d/{$FullName}'),
new PageStore('wikilib.d/{$FullName}'));
@]
This lets you test the new version using existing page content
without impacting the existing site or risking modification of
the pages. (Of course, any recipes or local customizations have to
be installed in the new version as well.)
Then, once you're comfortable that the new version seems to work
as well as the old, it's safe to upgrade the old version (and one
knows of any configuration or page changes that need to be made).
[[PmWiki]] is designed to make it easy to upgrade the PmWiki software without affecting your existing data files or installation. For most upgrades, you simply copy the files in the new release over your existing installation.
%block bgcolor=#f7f7f7 color=black border='1px solid black' padding=5px% '''Note for PmWiki 1.0 sites:''' Upgrading from 1.0.x to 2.0 requires more than simply copying the 2.0 software over the 1.0 installation. See [[PmWiki:Upgrading From PmWiki 1]] for more details.
!! To upgrade PmWiki:
!!! 1. Read the release notes
If you're upgrading to a new major release (a release where the second number changes, as in going from 0.5.27 to 0.6.0), then carefully read the [[(PmWiki:)ReleaseNotes]] before performing an upgrade to see if there are any significant changes or preparation tasks that must be handled before performing the upgrade. Upgrading from a beta version of 2.0 is quite easy, but taking a look at the 2.0 [[(PmWiki:)ReleaseNotes]] doesn't hurt.
!!! 2. Backup
It's ''always'' a good idea to have a [[(PmWiki:)backup (And Restore)]] copy of your existing PmWiki installation before starting. You can copy the entire directory containing your existing installation, or you can just make copies of the ''wiki.d/'' directory and any other local customization files you may have created (e.g., ''config.php'', ''localmap.txt'', etc.).
!!! 3. Download and extract
Download the version of PmWiki that you want from the [[(PmWiki:)download]] page.
Extract the tar image using @@tar -xvzf ''tgzfile''@@, where ''tgzfile'' is the tar file you downloaded above. This will create a @@pmwiki-x.y.z@@ directory with the new version of the software.
!!! 4. Copy
Copy the files in @@pmwiki-x.y.z@@ over the files of your existing PmWiki installation. For example, if your existing PmWiki installation is in a directory called ''pmwiki'', then one way to copy the new files over the existing ones is to enter the command:
->@@cp -a pmwiki-x.y.z/. pmwiki@@
Note that BSD systems will not have the -a option as a command-line argument for ''cp'', but that's okay, since it's just shorthand for ''cp -dpR'', so use that instead of ''-a''.
On (some) [=FreeBSD=] servers and Mac OS X systems you need to use
->@@cp -Rpv pmwiki-x.y.z/. pmwiki@@
!!! 5. Update customisations and recipes
That's it! Your base PmWiki installation is complete.
Now use the [[PmWiki:Site Analyzer]] to determine which recipes could be updated to the most recent version.
Unless you have made customizations to the ''pmwiki.php'' script or to the files in ''scripts/'', your PmWiki installation should continue to run correctly! (Changes to these files are {+not+} recommended).
([[Local customizations]] should go in ''local/config.php'', ''pub/css'', and ''pub/skins/''yourskinname)
'''Note''': Additional tips can be found on the [[PmWiki:Troubleshooting]] page.
>>faq<< [[#faq]]
Q: How can I determine what version of PmWiki I'm running now?
A: See [[version]] - {Version$:Summary}.
Q: How can I test a new version of PmWiki on my wiki without changing the prior version used by visitors?
A: The easy way to do this is to install the new version in a separate
directory, and for the new version set (in local/config.php):
[@
$WikiLibDirs = array(&$WikiDir,
new PageStore('/path/to/existing/wiki.d/{$FullName}'),
new PageStore('wikilib.d/{$FullName}'));
@]
This lets you test the new version using existing page content
without impacting the existing site or risking modification of
the pages. (Of course, any recipes or local customizations have to
be installed in the new version as well.)
Then, once you're comfortable that the new version seems to work
as well as the old, it's safe to upgrade the old version (and one
knows of any configuration or page changes that need to be made).
August 26, 2011, at 04:49 PM
by - auPbjiuzHcK
Changed line 1 from:
JBS8os <a href="http://ggwffyabzabw.com/">ggwffyabzabw</a>
to:
ZDiNzH , [url=http://wckooasqfgdk.com/]wckooasqfgdk[/url], [link=http://jixdobldwrjd.com/]jixdobldwrjd[/link], http://xxdhgcledxei.com/
August 26, 2011, at 01:07 PM
by - isuxCVdzHOZQ
Changed line 1 from:
Boy that relaly helps me the heck out.
to:
JBS8os <a href="http://ggwffyabzabw.com/">ggwffyabzabw</a>
August 25, 2011, at 02:57 PM
by - SgkXEAOzqLihjAoCI
Changed line 1 from:
This airtcle is a home run, pure and simple!
to:
Boy that relaly helps me the heck out.
July 19, 2011, at 07:22 PM
by - uGWHebbcFePIvqZE
Changed line 1 from:
There's nothing like the rleeif of finding what you're looking for.
to:
This airtcle is a home run, pure and simple!
July 19, 2011, at 06:21 PM
by - uaUdKPkTbzXMoqIs
Changed line 1 from:
Thanks alot - your answer solved all my problems after several days srgtugilng
to:
There's nothing like the rleeif of finding what you're looking for.
July 18, 2011, at 12:19 PM
by - geOhDDzsOzyrdr
Changed line 1 from:
Great coommn sense here. Wish Id thought of that.
to:
Thanks alot - your answer solved all my problems after several days srgtugilng
July 18, 2011, at 07:09 AM
by - VAxeAmCFGYT
Changed line 1 from:
One or two to reemmber, that is.
to:
Great coommn sense here. Wish Id thought of that.
July 08, 2011, at 01:19 AM
by - BcQnzWJIRf
Changed line 1 from:
QGG48S , [url=http://rtoyocnpqqhn.com/]rtoyocnpqqhn[/url], [link=http://qvnyqwoxaxkv.com/]qvnyqwoxaxkv[/link], http://bktxlcykmmam.com/
to:
One or two to reemmber, that is.
July 07, 2011, at 03:03 PM
by - DtcjDRUsOsssfRb
Changed line 1 from:
3tFAjg <a href="http://bhmlpeiizzsu.com/">bhmlpeiizzsu</a>
to:
QGG48S , [url=http://rtoyocnpqqhn.com/]rtoyocnpqqhn[/url], [link=http://qvnyqwoxaxkv.com/]qvnyqwoxaxkv[/link], http://bktxlcykmmam.com/
July 07, 2011, at 10:04 AM
by - PIlvIVIsBNQEp
Changed line 1 from:
You're the gertaest! JMHO
to:
3tFAjg <a href="http://bhmlpeiizzsu.com/">bhmlpeiizzsu</a>
July 06, 2011, at 11:17 AM
by - kNYQeMxaXABaIqN
Changed lines 1-64 from:
(:Summary:How to upgrade an existing PmWiki installation:)
[[PmWiki]] is designed to make it easy to upgrade the PmWiki software without affecting your existing data files or installation. For most upgrades, you simply copy the files in the new release over your existing installation.
%block bgcolor=#f7f7f7 color=black border='1px solid black' padding=5px% '''Note for PmWiki 1.0 sites:''' Upgrading from 1.0.x to 2.0 requires more than simply copying the 2.0 software over the 1.0 installation. See [[PmWiki:Upgrading From PmWiki 1]] for more details.
!! To upgrade PmWiki:
!!! 1. Read the release notes
If you're upgrading to a new major release (a release where the second number changes, as in going from 0.5.27 to 0.6.0), then carefully read the [[(PmWiki:)ReleaseNotes]] before performing an upgrade to see if there are any significant changes or preparation tasks that must be handled before performing the upgrade. Upgrading from a beta version of 2.0 is quite easy, but taking a look at the 2.0 [[(PmWiki:)ReleaseNotes]] doesn't hurt.
!!! 2. Backup
It's ''always'' a good idea to have a [[(PmWiki:)backup (And Restore)]] copy of your existing PmWiki installation before starting. You can copy the entire directory containing your existing installation, or you can just make copies of the ''wiki.d/'' directory and any other local customization files you may have created (e.g., ''config.php'', ''localmap.txt'', etc.).
!!! 3. Download and extract
Download the version of PmWiki that you want from the [[(PmWiki:)download]] page.
Extract the tar image using @@tar -xvzf ''tgzfile''@@, where ''tgzfile'' is the tar file you downloaded above. This will create a @@pmwiki-x.y.z@@ directory with the new version of the software.
!!! 4. Copy
Copy the files in @@pmwiki-x.y.z@@ over the files of your existing PmWiki installation. For example, if your existing PmWiki installation is in a directory called ''pmwiki'', then one way to copy the new files over the existing ones is to enter the command:
->@@cp -a pmwiki-x.y.z/. pmwiki@@
Note that BSD systems will not have the -a option as a command-line argument for ''cp'', but that's okay, since it's just shorthand for ''cp -dpR'', so use that instead of ''-a''.
On (some) [=FreeBSD=] servers and Mac OS X systems you need to use
->@@cp -Rpv pmwiki-x.y.z/. pmwiki@@
!!! 5. Update customisations and recipes
That's it! Your base PmWiki installation is complete.
Now use the [[PmWiki:Site Analyzer]] to determine which recipes could be updated to the most recent version.
Unless you have made customizations to the ''pmwiki.php'' script or to the files in ''scripts/'', your PmWiki installation should continue to run correctly! (Changes to these files are {+not+} recommended).
([[Local customizations]] should go in ''local/config.php'', ''pub/css'', and ''pub/skins/''yourskinname)
'''Note''': Additional tips can be found on the [[PmWiki:Troubleshooting]] page.
>>faq<< [[#faq]]
Q: How can I determine what version of PmWiki I'm running now?
A: See [[version]] - {Version$:Summary}.
Q: How can I test a new version of PmWiki on my wiki without changing the prior version used by visitors?
A: The easy way to do this is to install the new version in a separate
directory, and for the new version set (in local/config.php):
[@
$WikiLibDirs = array(&$WikiDir,
new PageStore('/path/to/existing/wiki.d/{$FullName}'),
new PageStore('wikilib.d/{$FullName}'));
@]
This lets you test the new version using existing page content
without impacting the existing site or risking modification of
the pages. (Of course, any recipes or local customizations have to
be installed in the new version as well.)
Then, once you're comfortable that the new version seems to work
as well as the old, it's safe to upgrade the old version (and one
knows of any configuration or page changes that need to be made).
[[PmWiki]] is designed to make it easy to upgrade the PmWiki software without affecting your existing data files or installation. For most upgrades, you simply copy the files in the new release over your existing installation.
%block bgcolor=#f7f7f7 color=black border='1px solid black' padding=5px% '''Note for PmWiki 1.0 sites:''' Upgrading from 1.0.x to 2.0 requires more than simply copying the 2.0 software over the 1.0 installation. See [[PmWiki:Upgrading From PmWiki 1]] for more details.
!! To upgrade PmWiki:
!!! 1. Read the release notes
If you're upgrading to a new major release (a release where the second number changes, as in going from 0.5.27 to 0.6.0), then carefully read the [[(PmWiki:)ReleaseNotes]] before performing an upgrade to see if there are any significant changes or preparation tasks that must be handled before performing the upgrade. Upgrading from a beta version of 2.0 is quite easy, but taking a look at the 2.0 [[(PmWiki:)ReleaseNotes]] doesn't hurt.
!!! 2. Backup
It's ''always'' a good idea to have a [[(PmWiki:)backup (And Restore)]] copy of your existing PmWiki installation before starting. You can copy the entire directory containing your existing installation, or you can just make copies of the ''wiki.d/'' directory and any other local customization files you may have created (e.g., ''config.php'', ''localmap.txt'', etc.).
!!! 3. Download and extract
Download the version of PmWiki that you want from the [[(PmWiki:)download]] page.
Extract the tar image using @@tar -xvzf ''tgzfile''@@, where ''tgzfile'' is the tar file you downloaded above. This will create a @@pmwiki-x.y.z@@ directory with the new version of the software.
!!! 4. Copy
Copy the files in @@pmwiki-x.y.z@@ over the files of your existing PmWiki installation. For example, if your existing PmWiki installation is in a directory called ''pmwiki'', then one way to copy the new files over the existing ones is to enter the command:
->@@cp -a pmwiki-x.y.z/. pmwiki@@
Note that BSD systems will not have the -a option as a command-line argument for ''cp'', but that's okay, since it's just shorthand for ''cp -dpR'', so use that instead of ''-a''.
On (some) [=FreeBSD=] servers and Mac OS X systems you need to use
->@@cp -Rpv pmwiki-x.y.z/. pmwiki@@
!!! 5. Update customisations and recipes
That's it! Your base PmWiki installation is complete.
Now use the [[PmWiki:Site Analyzer]] to determine which recipes could be updated to the most recent version.
Unless you have made customizations to the ''pmwiki.php'' script or to the files in ''scripts/'', your PmWiki installation should continue to run correctly! (Changes to these files are {+not+} recommended).
([[Local customizations]] should go in ''local/config.php'', ''pub/css'', and ''pub/skins/''yourskinname)
'''Note''': Additional tips can be found on the [[PmWiki:Troubleshooting]] page.
>>faq<< [[#faq]]
Q: How can I determine what version of PmWiki I'm running now?
A: See [[version]] - {Version$:Summary}.
Q: How can I test a new version of PmWiki on my wiki without changing the prior version used by visitors?
A: The easy way to do this is to install the new version in a separate
directory, and for the new version set (in local/config.php):
[@
$WikiLibDirs = array(&$WikiDir,
new PageStore('/path/to/existing/wiki.d/{$FullName}'),
new PageStore('wikilib.d/{$FullName}'));
@]
This lets you test the new version using existing page content
without impacting the existing site or risking modification of
the pages. (Of course, any recipes or local customizations have to
be installed in the new version as well.)
Then, once you're comfortable that the new version seems to work
as well as the old, it's safe to upgrade the old version (and one
knows of any configuration or page changes that need to be made).
to:
You're the gertaest! JMHO