Re: [Phpwiki-talk] can't leave `index.xxx' out in 1.2?]

[Jeff D. <da...@da...>]

NOTE: These comments pertain only to the latest CVS development code,
not to the stable release (1.2.x) of PhpWiki.

In message <m3d...@ap...>,Jan Nieuwenhuizen writes:
>Ok, this seems to have been fixed in the very latest ,v1.13 or 1.14.

As I noted, the development branch is unstable code.  You're not allowed
to get snippy if it doesn't work :-)

(I think at this instant, it's fairly bug-free, but that's liable to
change once we start introducing the new database API.)

>However, now you get to see the page, but can't click on editpage:
>
>    http://appel.lilypond.org/new-wiki/?pointandclick
>
>maybe I need to specify some Path or Serveraddress?

I think this is because you've set SCRIPT_NAME to something that's not
the name of your script.

The simple fix is to leave SCRIPT_NAME unset (or set it to
a value which actually points to the index.php script.)

Then the canonical URLs for pages in your wiki will look like:
    http://appel.lilypond.org/new-wiki/index.php/pointandclick
though
    http://appel.lilypond.org/new-wiki/?pointandclick
should still work.


=======
A fancier solution, if you don't mind if URLs like
   http://appel.lilypond.org/new-wiki/index.php?pointandclick
(with an explicit 'index.php') stop working altogether, is:

1. Rename the new-wiki directory to something else.  (Actually only
the images/ subdirectory and 'phpwiki.css' need to be web-accessible.
The rest of the phpwiki code can go outside your document root.)

2. Copy index.php to /your/server/root/new-wiki.  You are copying the file
index.php to a file (not a directory) named new-wiki.

3. In /your/server/root/.htaccess add these lines:
   <Files new-wiki>
      SetHandler application/x-httpd-php
   </Files>
That should make apache treat the file new-wiki as a php script.

4. Edit new-wiki as follows (more or less):
  a. (Set admin user/pass, database config stuff normally...)
  b. Uncomment the ini_set('include_path',...) line, and set the include_path
     to point to where the rest of the PhpWiki source code is.
  c. Set DATA_PATH to the abs url (relative to the server root) where
     phpwiki.css and the images/ subdirectory can be found.

Now your wiki pages should appear at, e.g.:
    http://appel.lilypond.org/new-wiki/pointandclick
(or http://appel.lilypond.org/new-wiki?pointandclick )


=====


>Which brings me to another question.  I'm in the process of upgrading
>the php code of the wiki, but what would be the easiest way to upgrade
>the canned pages that come with the wiki (leaving the rest of the wiki
>db intact, of course)?  Esp.
>
>    http://appel.lilypond.org/new-wiki?releasenotes
>
>would be good to have upgraded.

Update the PhpWikiAdministration page by hand.  (ie. Browse to 
  http://appel.lilypond.org/new-wiki/PhpWikiAdministration ,
click on EditText, and cut-and-paste from pgsrc/PhpWikiAdministration.)

Then browse to the new PhpWikiAdministration page.  Near the top you
should see a "Log In" link.  Click on it and log in (using the
admin user/password).  Then lock the PhpWikiAdministration page.

Then you can use the "Upload File" or "Load File" forms on the
PhpWikiAdministration page to load individual files from the
pgsrc directory into your wiki.

(You could also use LoadFile to load all the pages in pgsrc in one
fell swoop --- but that would blindly overwrite any existing pages
(like FrontPage) so that probably isn't what you want to do.)


Jeff