u8hodt1 1l6e3rcn4 <a href="http://mtcg.snu.ac.kr/index.php?mid=sphmsg&document_srl=9525#">maglie calcio poco prezzo</a> zw8hd0bag 4wlapzc5x\n 1o8xnzej aklmrgf <a href="http://steelcongress.ru/matthias-fodboldtrojer-med-tryk-susannah/">billige fodboldtrøjer</a> wu0onr c5pw24\n uzcfo7p louvx0nfkr <a href="http://www.robotous.com/index.php?mid=photo&document_srl=5422#">maglie calcio bambino</a> 6p81a49ju0 4knlajd6h\n |
(:Summary:Contains the 'action' links (like Browse, Edit, History, etc.), placed at the top of the page, see site page actions:) (:comment This page can be somewhat complex to figure out the first time you see it. Its contents are documented at PmWiki.SitePageActions if you need help. :) * View * Edit * History * Print (:comment delete if and ifend to enable backlinks:) PmWiki /
Upgrades(:Summary: PmWiki group header. Includes styles and trail.:) (:comment please leave the multiple style definitions concatenated as a single line. Linebreaks do appear in the output when the wiki is configured with linebreaks enabled -- thanks!:) (:comment included in PmWiki localisation headers and footers :) 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. '''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 Upgrading From PmWiki 1 for more details. >>lframe smaller<< Contents * Generic instructions * Upgrading from version 2.1.27 to 2.2.0 * Upgrading from version 2.2.0 to the latest version * FAQ >><<<<? Generic instructions1. Read the release notesPlease read carefully the ReleaseNotes before performing an upgrade, about the changes between your previous version and the new one. See if there are any significant changes or preparation tasks that must be handled before performing the upgrade. 2. BackupIt's ''always'' a good idea to have a backup 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 extractDownload the version of PmWiki that you want from the 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. CopyCopy 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''. Some environments have an alias established for ''cp'' that enable interactive prompts before overwriting a file. To work around this specify the absolute path to ''cp'', such as ''/bin/cp''. On (some) FreeBSD servers and Mac OS X systems you need to use ->@@cp -Rpv pmwiki-x.y.z/. pmwiki@@ 5. Update customisations and recipesThat'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. Upgrading from version 2.1.27 to 2.2.0Between the stable versions 2.1.27 and 2.2.0 there are a number of additions. Some of them may need changes to local config files or to wiki pages, and they are outlined here. For the full list of changes see the release notes. If you are upgrading from a 2.2.beta version, your wiki may already include these features. * Some pages that were formerly in the Site.* group are now in a separate read-protected SiteAdmin.* group: Site.AuthUser, Site.AuthList, Site.NotifyList, Site.Blocklist, and Site.ApprovedUrls. If upgrading from an earlier version, PmWiki will prompt to automatically copy these pages to their new location if needed. If a site wishes to continue using the old Site.* group for these pages, simply set to config.php @@ * To authorize reading or editing in protected areas, the former password @@"nopass"@@ should now be written as @@"@nopass"@@. * WikiWords are now disabled by default. To re-enable them, set either * The * Page links inside included pages, sidebars, headers or footers are now treated as relative to the page where they are written, instead of the page where they appear. For example, in Site.SideBar, always set the group in a wikilink like * PageLists
** Spaces no longer separate wildcard patterns -- use commas.
** * Skin templates are now required to have <!--HTMLHeader--> and <!--HTMLFooter--> directives. * Authentication using Active Directory is now simplified, see PmWiki.AuthUser. Upgrading from version 2.2.0 to the latest version''Note: this page may have a more recent version, see PmWiki:Upgrades.'' Some additions since version 2.2.0 may need changes to local config files or to wiki pages, and they are outlined here. For the full list of changes see release notes and change log. * Version 2.2.10: * Version 2.2.35: Important change for international wikis: the XLPage() function no longer loads encoding scripts such as xlpage-utf-8.php. When you upgrade, you need to include those scripts from config.php, before the call to XLPage(): include_once("scripts/xlpage-utf-8.php"); # if your wiki uses UTF-8 XLPage('bg','PmWikiBg.XLPage'); FAQQ: How can I determine what version of PmWiki I'm running now? A: See version - Determining and displaying the current version of PmWiki (pmwiki-2.2.74). 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): <:vspace> $WikiLibDirs = array(&$WikiDir, new PageStore('/path/to/existing/wiki.d/{$FullName}'), new PageStore('wikilib.d/{$FullName}')); <:vspace>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). (:nl:)(:Summary:Trail and talk page links:) (:comment included in PmWiki localisation headers and footers :) <<? >>bgcolor=#ffe border-top="1px solid black" font-size=.8em<< This page may have a more recent version on pmwiki.org: PmWiki:Upgrades, and a talk page: PmWiki:Upgrades-Talk. >><< |