*** empty log message ***

git-svn-id: svn://pmwiki.org/trunk/pmwiki@456 524c5546-5005-0410-9a3e-e25e191bd360

1 files changed, 5 insertions, 5 deletions

diff --git a/wikilib.d/PmWiki.Installation b/wikilib.d/PmWiki.Installation
index c1afe367..7bf962b6 100644
--- a/wikilib.d/PmWiki.Installation
+++ b/wikilib.d/PmWiki.Installation
@@ -1,10 +1,10 @@
-version=pmwiki-2.0.beta6
+version=pmwiki-2.0.beta9
 newline=²
-text=Here are some quick instructions on how to download and install PmWiki 2.0.  Improvements to these instructions would be greatly appreciated.  Just report any problems you encounter to the pmwiki-users [[mailing list(s)]] or the [[PITS:PITS |PmWiki Issue Tracking System]].²²1. Download the latest version of PmWiki from http://www.pmwiki.org/pub/pmwiki/ .²²2. Extract the tar image using "[@tar zxvf pmwiki-''version''.tgz@]" (note that the tar file has to be extracted with the proper permissions set... see the note at the end of this page for more.).  ²²(Note: If you get the error "tar: z: unknown option", use "[@gunzip pmwiki-''version''.tgz@]" and then "[@tar xvf pmwiki-''version''.tgz@]" instead of the above command.).²²This will create a [@pmwiki-x.y.z@] directory which contains the PmWiki software.  Rename this directory to "pmwiki" by executing "[@mv pmwiki-x.y.z pmwiki@]" . The files in this directory include:²²    COPYING            The GNU General Public License²    local/             A directory for local configuration scripts²    pmwiki.php         Main PmWiki script²    pub/               Directory of publicly accessible files²      css/             Directory for generic .css files²      skins/           Directory of [[LayoutBasics |layout templates]]²    sample-config.php  A sample configuration file²    scripts/           Some scripts that extend the possibilities of PmWiki²    wikilib.d/         Directory containing some default PmWiki files²          ²These files need to be placed where they can be accessed by a web server (e.g. in a ''public_html'' directory of some sort).  ²²3. Open a web browser to the ''pmwiki.php'' script, by typing [=http://<access to the pmwiki.php script>=] (not [=file://. . .=]). PmWiki will then attempt to create the ''wiki.d'' directory for holding wiki pages with the appropriate ownerships and permissions.  This step will likely fail, but if it works then you can proceed to step 4 below.²²->3a. If you get an error message stating that PmWiki is unable to create the ''wiki.d'' directory, you need to temporarily change the permissions on the directory containing the ''pmwiki.php'' file to 2777.  In Unix this is commonly done by changing to the directory containing ''pmwiki.php'' and executing the command "[@chmod 2777 .@]" (note the dot at the end).  This will (1) make the directory writable so the web server can create the data directory it needs for the wiki files, and (2) preserve group ownership of the directory so the installer account can manipulate the files created in this directory.²²->3b. If your system doesn't allow changing permissions to 2777, then try 777 permissions instead.²²->3c. After changing the directory permissions, try opening a browser to the ''pmwiki.php'' script again.  If all is well, the ''wiki.d'' directory will have been created and you'll see the default home page.²²Hint: When "Safe Mode" is active you should create the directory wiki.d manually and give the right 777 to the directory. The same also for upload directory etc.²²4. If you're running Apache version 2.0.30 or later, you may need to set the [=AcceptPathInfo=] directive to "on" for the @@pmwiki.php@@ script.  This can be as simple as adding²²    [=AcceptPathInfo on=]²²to either the @@.htaccess@@ file in the directory containing @@pmwiki.php@@ or the server's @@httpd.conf@@ file.  If changing the @@httpd.conf@@ file, don't forget to restart Apache to have the change take effect.²²For more on this issue, see AcceptPathInfo.²²5.  Check out InitialSetupTasks for other tasks you may want to perform to begin customizing your PmWiki installation.  You might also want to peruse the ReleaseNotes for further information.²²('''Note:''' It is important that the tar file (@@*.tar@@) is unpacked with the proper permissions set.  For *nix operating systems, please check your permission mask by typing @@umask@@ at the command-line.  If it says anything other than "2", you'll need to change the permission mask by typing @@umask 002@@ at the command-line.  ''Then'' unpack the tar file.  If you do not do this the @@pmwiki.php@@ script will not be able to make use of other files in the tree.)²(:comment another alternative is to use (GNU) tar's option "-p, --same-permissions, --preserve-permissions" :)²²%trail%<<|PmWiki.DocumentationIndex|>>²
-time=1102300784
+text=Here are some quick instructions on how to download and install PmWiki 2.0.  Improvements to these instructions would be greatly appreciated.  Just report any problems you encounter to the pmwiki-users [[mailing list(s)]] or the [[PITS:PITS |PmWiki Issue Tracking System]].²²1. Download the latest version of PmWiki from http://www.pmwiki.org/pub/pmwiki/ .²²2. Unpack the archive.  This will create a [@pmwiki-x.y.z@] directory which contains the PmWiki software.  The files in this directory include:²²    COPYING            The GNU General Public License²    local/             A directory for local configuration scripts²    pmwiki.php         Main PmWiki script²    pub/               Directory of publicly accessible files²      css/             Directory for generic .css files²      skins/           Directory of [[LayoutBasics |layout templates]]²    sample-config.php  A sample configuration file²    scripts/           Some scripts that extend the possibilities of PmWiki²    wikilib.d/         Directory containing some default PmWiki files²    cookbook/          A directory for recipes obtained from the [[(Cookbook:)Cookbook]].²²3. The [@pmwiki-x.y.z@] directory needs to be placed into a location accessible by your webserver (e.g., in a ''public_html'' directory of some sort).  It doesn't matter how they get there -- FTP or a Unix [@mv@] or [@cp@] command generally work fine.²²->%note% Note: It's probably also a good idea to change the "[@pmwiki-x.y.z@]" directory name to be simply "[@pmwiki@]". ²²4. Open a web browser to the ''pmwiki.php'' script on the server (i.e., not the one on your local computer or accessed using a [=file://...=] URL).  PmWiki will then analyze your system configuration and provide instructions (if needed) for creating the ''wiki.d/'' directory which will be used to hold the pages created for your site.  Usually there are two ways to achieve this:²²->4a. You can create the ''wiki.d/'' directory manually, and then give it full write permissions (i.e., "[@chmod 777 wiki.d@]")²²->4b. On some systems you can let PmWiki create ''wiki.d/'' by temporarily changing the permissions on the directory containing the ''pmwiki.php'' file to 2777.  In Unix this is commonly done by changing to the directory containing ''pmwiki.php'' and executing the command "[@chmod 2777 .@]" (note the dot at the end).  The [@chmod@] command also works in many FTP programs.  Creating ''wiki.d/'' in this manner will (1) make the directory writable so the web server can create the data directory it needs for the wiki files, (2) preserve group ownership of the directory so the installer account can manipulate the files created in this directory, and (3) make it more difficult for other accounts on the same server to access the files in ''wiki.d/''.²²5.  After establishing directory permissions, try opening a browser to the ''pmwiki.php'' script again.  If all is well, the ''wiki.d'' directory will have been created and you'll see the default home page.²²6.  Check out InitialSetupTasks for other tasks you may want to perform to begin customizing your PmWiki installation.  You might also want to peruse the ReleaseNotes for further information.²²!!!!Notes²²* If using the Unix ''tar'' command to unpack the archive in step 2 above, be sure that the files are created with sufficient permissions for the webserver to be able to access them.  Usually you can ensure this by typing @@umask 002@@ on the command line before unpacking the tar file.²²%trail%<<|PmWiki.DocumentationIndex|>>
+time=1103090618
 name=PmWiki.Installation
 host=24.1.28.47
 agent=Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040206 Firefox/0.8
-rev=36
+rev=41
 author=Pm
-targets=PmWiki.MailingLists,PmWiki.PmWiki,PmWiki.LayoutBasics,PmWiki.AcceptPathInfo,PmWiki.InitialSetupTasks,PmWiki.ReleaseNotes,PmWiki.DocumentationIndex
+targets=PmWiki.MailingLists,PmWiki.PmWiki,PmWiki.LayoutBasics,PmWiki.InitialSetupTasks,PmWiki.ReleaseNotes,PmWiki.AuthorTracking,PmWiki.DocumentationIndex