phpwiki-talk

[Phpwiki-talk] standards-compliant lists

[Tara S. <te...@cl...>]

I can't find my way in the code to do this, but this is how nested lists=20
could be made standards-compliant.

First, this is what a nested list should look like (hope you can see the=20
tags):

<ul>
	<li>first</li>
	<li>second
		<ul>
			<li>first nested</li>
			<li>second nested</li>
		</ul></li>
	<li>third</li>
	<li>last</li>
</ul>

you can see that the inner <ul> simply needs to be inserted inside an=20
existing (closed) list item.

One way to do this would be (it's probably similar to some extent to=20
what is currently being done in 1.3):

On meeting the first * (or #), replace it with <ul><li>.
Replace the next * by </li>\n</li> (etc)

If we get two ** replace by <ul><li> (you can see that it is the same as=20
the first, so no need to treat it differently)

So basically, we need two "opening" lines:

one of the "first" or "extra" * (if there is one more than the last=20
line, of if this is the first line)

one for a "next" ** in a series.

The tricky part is the closing.

When we go "down" one level, we need to have:

</li></ul></li> (closing the nested list-item, closing the nested list,=20
closing the list-item the nested list is in.

But if we're going down to level zero, we need:

<li></ul>

I think there is some sort of counter in the current code that keeps=20
track of which level we are in?

There. I'm just posting this thinking to the list in case it can inspire=20
someone. If you see clearer than me into the existing code (which isn't=20
difficult), is there a simple way this could be implemented in it?

I'm sure I could hack out a little function or such to do this, but it=20
would probably take me a VERY long time and be VERY ugly ;)

waiting for feedback :)

Tara
--=20
Je r=E9ponds au mieux de mes connaissances
Climb to the Stars! - http://climbtothestars.org/
SpiroLattic - http://climbtothestars.org/spiro/
Pompeurs Associ=E9s - http://pompage.net/

Re: [Phpwiki-talk] removing "index.php" from url

[Aredridel <are...@nb...>]

> I see you (who?) did it for http://phpwiki.sourceforge.net/wiki/ - page=20
> urls look like: http://phpwiki.sourceforge.net/wiki/PageName
> 
> How did you do it? with mod_rewrite or somewhere inside the php?

I did it on NBTSWikiWiki with a symlink and .htaccess file:

wiki is installed in htdocs/wiki-code (though this could be anywhere on the
filesystem), and then I symlinked htdocs/wiki-code/index.php to htdocs/wiki,
then put in this htdocs/.htaccess:

<Files wiki>
	ForceType	application/x-httpd-php
</Files>

It works for me, but I'm using a strongly hacked phpwiki-1.2

[Phpwiki-talk] Semi-major bug in 1.2.x

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

There is a bug in PhpWiki 1.2.x which causes PhpWiki to produce
corrupt zip dumps.  The bug affects the dbm, dba and flat filesystem
backends, and is present both in both releases (1.2.0 and 1.2.1).
(It is not present in the current CVS, release-1_2-branch.)

The fix: Either:
  Upgrade to the latest CVS code.
  Upgrade to release 1.2.2 (which is not yet available, as of this
writing)
 or
  Manually fix your PhpWiki code as described below:

My apologies for all inconvenience.
Thanks to Malcom Ryan for finding the bug.

=====

To Manually Patch PhpWiki 1.2.0 or 1.2.1:

 1. Edit the appropriate backend driver:
      Backend    Driver File
      =======    ============
      DBA        lib/dbalib.php
      DBM        lib/dbmlib.php
      flat file  lib/db_filesystem.php

 2. Find the function definition for RetrievePage().  (Look for a file
    which begins "function RetrievePage"...)

 3. Within RetrievePage() look for the line which begins: 
       $pagehash = unserialize(
    (the exact arguments of unserialize depend on the backend.)

 4. Immediately after that line add a line which reads:
       $pagehash['pagename'] = $pagename;

That's it.  When you're done, the appropriate portion of the file
should look like:


lib/dbalib.php:

   // Return hash of page + attributes or default
   function RetrievePage($dbi, $pagename, $pagestore) {
      if ($data = dba_fetch($pagename, $dbi[$pagestore])) {
         // unserialize $data into a hash
         $pagehash = unserialize(UnPadSerializedData($data));
         $pagehash['pagename'] = $pagename;
         return $pagehash;
      } else {
         return -1;
      }
   }


lib/dbmlib.php:

   // Return hash of page + attributes or default
   function RetrievePage($dbi, $pagename, $pagestore) {
      if ($data = dbmfetch($dbi[$pagestore], $pagename)) {
         // unserialize $data into a hash
         $pagehash = unserialize(UnPadSerializedData($data));
         $pagehash['pagename'] = $pagename;
         return $pagehash;
      } else {
         return -1;
      }
   }


lib/db_filesystem.php (Phpwiki-1.2.1): 

          if ($data = fread($fd, filesize($filename))) {
             // unserialize $data into a hash
             $pagehash = unserialize($data);
             $pagehash['pagename'] = $pagename;
            if (!is_array($pagehash))
                ExitWiki(sprintf(gettext("'%s': corrupt file"),
                                 htmlspecialchars($filename)));

lib/db_filesystem.php (Phpwiki-1.2.0): 

         if ($data = file($filename)) {
             // unserialize $data into a hash
            $pagehash = unserialize(join("\n", $data));
            $pagehash = unserialize($data);
         }

Re: [Phpwiki-talk] signing in before editing

[Adam S. <ad...@pe...>]

> What I'll have a shot at trying to do (in a few hours), is make the
> edit page automatically pop up the sign in form if the user is not
> authenticated. I'll let you know if I succeed (oh, and if I don't,
> you'll probably hear cries of help coming from somewhere in
> Switzerland).

i think that's actually a pretty neat idea.  what you'll need to do though
is make sure that you print a very clear message that says something to
the tune of "you must log in to edit a page but any name will work so long
as it's a WikiWord".  otherwise people will just say "crap" and click
cancel cause they think they don't have an account.

i'm not sure how you do that consisely and clearly with the apache style
auth pop ups.  a better way would be to have a SignIn wiki page, and
redirect them there if they aren't logged in and explain how things work
... but i suspect that will require a different authentication system then
the one currently in place.

adam.

[Phpwiki-talk] signing in before editing

[Tara S. <te...@cl...>]

I think my approach to make people sign in so that they can "see" the=20
edit button is discouraging people from using the wiki. In any case, I=20
don't think it's exactly the right approach.

What I'll have a shot at trying to do (in a few hours), is make the edit=20
page automatically pop up the sign in form if the user is not=20
authenticated. I'll let you know if I succeed (oh, and if I don't,=20
you'll probably hear cries of help coming from somewhere in Switzerland).

(just thinking out loud before I do it).

Ideas or remarks, anyone? Has it been done before?

Tara
--=20
Je r=E9ponds au mieux de mes connaissances
Climb to the Stars! - http://climbtothestars.org/
SpiroLattic - http://climbtothestars.org/spiro/
Pompeurs Associ=E9s - http://pompage.net/

Re: [Phpwiki-talk] RecentChanges - view minor edits too?

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

On Tue, 13 Nov 2001 09:26:48 +0100
"Tara Star" <te...@cl...> wrote:

> Is there any way I could choose the view the minor edits too in 
> RecentChanges - for example when I'm logged in as admin?
> 
> Is it something that could easily be added to the user prefs, or not?

I don't think you can do this based on username or user preference
right now.  To add a user preference for this is a good idea, I think.
It would be straightforward, but not trivial to do --- I'll think I'll
postpone it until the user login code is closer to it's final form.


Currently the RecentChanges plugin accepts four arguments:
  days: (floating point value) number of days to show.
  show_minor: (boolean, default = false) Include minor edits in listing?
  show_major: (boolean, default = true) Include major edits in listing?
  show_all: (boolean, default = false) Include all edits for each page,
            not just the most recent.

So with the default args: show_minor=false, show_major=true,
show_all=false,
you get the most recent non-minor change for each page.

<?plugin RecentChanges show_minor=true?> Will give you the most recent
change,
whether it's minor or non-minor.

<?plugin RecentChanges show_minor=true show_all=true?> will give you all
the changes for each page.  (This is what's used on
http://phpwiki.sourceforge.net/wiki/RecentEdits.)

You can also pass arguments to plugins via HTTP query args, so
http://phpwiki.sourceforge.net/wiki/RecentChanges?show_minor=true will
give you the most recent change to each page.

Combining this with MagicPhpWikiURLs, you could put a button on
RecentChanges to get to this view.  Something like [Include Minor
Edits|phpwiki:?show_minor=true] should work.  This is how the "Show
changes for n days" buttons work in the stock RecentChanges in
pgsrc/RecentChanges.

[Phpwiki-talk] RecentChanges - view minor edits too?

[Tara S. <te...@cl...>]

Is there any way I could choose the view the minor edits too in=20
RecentChanges - for example when I'm logged in as admin?

Is it something that could easily be added to the user prefs, or not?

Tara
--=20
Je r=E9ponds au mieux de mes connaissances
Climb to the Stars! - http://climbtothestars.org/
SpiroLattic - http://climbtothestars.org/spiro/
Pompeurs Associ=E9s - http://pompage.net/

Re: [Phpwiki-talk] removing "index.php" from url

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

On Mon, 12 Nov 2001 22:03:39 +0100
"Tara Star" <te...@cl...> wrote:

> a) is there any way I can make the script "wiki" access the WikiFiles 
> which are in /public_html/spirolattic/ (mapped as another domain name)?

(If I understand the question correctly:) Sure.  You can put phpwikis
all over the place --- they can even be on different physical hosts.
As long as each one is configured to talk to the same database (same
mysql server/database, or same dbm files) they will all have the same
contents.

> b) if it was possible (I suspect it isn't, though), then I could access 
> the wiki by spirolattic.net/wiki/

Certainly possible.

> => b1) could I tell my server that "wiki" is the default file to look 
> for in a directory (not "index.php"), so that the "wiki/" part 
> disappears in the uri? (again, I don't think it is possible, as it isn't

> when the default file is "index.php")


You want e.g. the RecentChanges to be at
http://spirolattic.net/RecentChanges,
I think.

You can do this, I think, but not, I think (again), in quite the way you
suggest.  You could do it, I'm sure, with mod_rewrite (since you can do
just about anything with mod_rewrite).  It's also probably possible
to do this using Apache's 'Handler' directive.  There's some cryptic
notes I made on this at http://phpwiki.sf.net/wiki/PageNamesInPathInfo.

The reason most people would not want to do this is that if you do,
the wiki occupies the entire URL name space of your domain.  If you ever
want to add something else (other than wiki) under that domain, you're
out of luck, since every URL points to a wiki page.

Re: [Phpwiki-talk] removing "index.php" from url

[Tara S. <te...@cl...>]

Jeff Dairiki wrote:

> On Sun, 11 Nov 2001 22:18:25 +0100
> "Tara Star" <te...@cl...> wrote:
>=20
>=20
>>I see you (who?) did it for http://phpwiki.sourceforge.net/wiki/ - page=
=20
>>urls look like: http://phpwiki.sourceforge.net/wiki/PageName
>>
>=20
> Here's how it's done on the sourceforge site:

[snip]


>=20
> That's it!  There are many ways to get this to work.  Study the comment=
s
> in index.php for some more hints.
>=20
> Also if you do this kind of funnyness you're much more likely to uncove=
r
> arcane bugs, snakes and spiders.


*arms herself with Raid(TM) for dealing with the avalanche of=20
six-to-eight-legged beings which is likely to show up*

Now, let's consider another (soon-to-be-real-life) case. The wiki files=20
are in /public_html/spirolattic/.

<thinking class=3D"aloud">

Let's say I create /thing/ (same level as /public_html/) and set that as=20
the root directory for the domain spirolattic.net. I create a file=20
called "wiki" as directed above, in the directory /thing/ =3D> /thing/wik=
i.

a) is there any way I can make the script "wiki" access the WikiFiles=20
which are in /public_html/spirolattic/ (mapped as another domain name)?

b) if it was possible (I suspect it isn't, though), then I could access=20
the wiki by spirolattic.net/wiki/

=3D> b1) could I tell my server that "wiki" is the default file to look=20
for in a directory (not "index.php"), so that the "wiki/" part=20
disappears in the uri? (again, I don't think it is possible, as it isn't=20
when the default file is "index.php")

</thinking>

Ok, in fact I just want to be sure I'm right in thinking these things=20
aren't possible.

As I see it (considering I don't want to move my WikiFiles), I'll have=20
to make the new domain point to a directory on the same level as the=20
current wiki directory, and then do some nasty mod_rewrite so that pages=20
can be accessed as http://spirolattic.net/RecentChanges - for example.

Does anybody see any other solutions to this?

Thanks :)

Tara

--=20
Je r=E9ponds au mieux de mes connaissances
Climb to the Stars! - http://climbtothestars.org/
SpiroLattic - http://climbtothestars.org/spiro/
Pompeurs Associ=E9s - http://pompage.net/

Re: [Phpwiki-talk] linking scheme and markup

[Reini U. <ru...@x-...>]

Gary Benson schrieb:
> 
> On Fri, 9 Nov 2001, Reini Urban wrote:
> 
> > you probably mean to sore only xhtml and not the wiki markup in the db?
> > hmm, weird idea.
> 
> Store wiki markup and the html _after templating_ so all it has to do
> for browse pageviews is select and send.

I think it was Jeff you answered on this suggestion of mine earlier this year:
http://phpwiki.sourceforge.net/phpwiki/index.php?PerformanceHacks

"Change/rerender the html when a referred page is deleted or added. Do as much
as possible in the editpage post step.
Maybe check timestamps of the templates and gettext messages, which influence
the rendering also, but better is to dirty all pages in the admin mode with a
seperate button. 
=>
IMHO the HTML rendering is negligible compared to the database access. It
would be much more important to cache complete pages in the filesystem and
update them if templates or anything else has changed. Minimizing database
access is much more important than code optimization."

So we could add some admin code to update or dirty wiki pages when templates
and php code change. This would lead to a faster caching code (=> 302), but
would require another 
wikipage flag.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: [Phpwiki-talk] removing "index.php" from url

[Tara S. <te...@cl...>]

Jeff Dairiki wrote:

> On Sun, 11 Nov 2001 22:18:25 +0100
> "Tara Star" <te...@cl...> wrote:
>=20
>=20
>>I see you (who?) did it for http://phpwiki.sourceforge.net/wiki/ - page=
=20
>>urls look like: http://phpwiki.sourceforge.net/wiki/PageName
[snip]
>=20
> Also if you do this kind of funnyness you're much more likely to uncove=
r
> arcane bugs, snakes and spiders.
>=20


you know I love those, don't you? ;)

Tara


--=20
Je r=E9ponds au mieux de mes connaissances
Climb to the Stars! - http://climbtothestars.org/
SpiroLattic - http://climbtothestars.org/spirolattic/
Pompeurs Associ=E9s - http://pompage.net/

Re: [Phpwiki-talk] plugin trouble

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

> is there any reason for that restriction?

No, I guess not.  

I think you can fix it by changing the regexp in the call to
$transform->register() around line 298 of lib/transform.php.  My untested
guess is that changing
 "$InterWikiLinkRegexp:$WikiNameRegexp"
to
 "$InterWikiLinkRegexp:\\S+"
will do the trick.

Spaces will still not be allowed in the RHSs (unless brackets are used)
for fairly obvious reasons.

If I remember, I'll fix it in CVS in a couple of days.  If I don't
remember, remind me.


On Mon, 12 Nov 2001 09:01:26 -0800 (PST)
"Adam Shand" <ad...@pe...> wrote:

> 
> > (It's not obvious from the code,) but you can use arbitrary right hand
> > sides if you put the whole thing in square brackets, like:
> > [PhpWiki:square brackets].
> 
> okay that'll work.  is there any reason for that restriction?  it just
> makes doing things this ugly:
> 
> Google:PhpWiki or ISBN:12-34566-789 or Category:Documentation
> 
> adam.
> 


-- 
--
Jeff Dairiki <da...@da...>

Re: [Phpwiki-talk] plugin trouble

[Adam S. <ad...@pe...>]

> (It's not obvious from the code,) but you can use arbitrary right hand
> sides if you put the whole thing in square brackets, like:
> [PhpWiki:square brackets].

okay that'll work.  is there any reason for that restriction?  it just
makes doing things this ugly:

Google:PhpWiki or ISBN:12-34566-789 or Category:Documentation

adam.

Re: [Phpwiki-talk] plugin trouble

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

> at least the version of phpwiki 1.3 i have doesn't work with some of
them
> though because it requires that the right hand side of the interwiki
link
> is a wiki word.

(It's not obvious from the code,) but you can use arbitrary right hand
sides if you put the whole thing in square brackets, like: [PhpWiki:square
brackets].

Re: [Phpwiki-talk] plugin trouble

[Tara S. <te...@cl...>]

Jeff Dairiki wrote:

> On Sun, 11 Nov 2001 21:45:55 +0100
> "Tara Star" <te...@cl...> wrote:

>>I have plugin problems, though:=20
>>
>>
> http://www.climbtothestars.org/spirolattic/index.php/LikePages?page=3DB=
ackLinks
>=20
> I just fixed it for you.  (It's fixed in CVS too.)


Thanks!!


> As you've just noticed, the plugin argument conventions are:
>  1) probably still in flux.
>  2) not documented
> It's alpha software.  Sorry.
>=20


That's fine. I hope you don't think I'm complaining about stuff not=20
working. But as I've got you handy, I ask questions (one thing I know=20
how to do very well) ;)




--=20
Je r=E9ponds au mieux de mes connaissances
Climb to the Stars! - http://climbtothestars.org/
SpiroLattic - http://climbtothestars.org/spirolattic/
Pompeurs Associ=E9s - http://pompage.net/

[Phpwiki-talk] pikiepikie's thoughts on rss'd wikis.

[Adam S. <ad...@pe...>]

maybe some food for thought ...

    http://pikie.darktech.org/cgi/pikie?BrainstormingPikieRss

it mostly seems to be what we've talked about in the past but it's nice to
see what other people are thinking as well.

adam.

Re: [Phpwiki-talk] plugin trouble

[Adam S. <ad...@pe...>]

> Currently, 1.3's interwiki links are pretty much an exact clone of
> UsemodWiki's

i have a collection of interwiki which is a superset of all the wiki's
i've used that i've build here:

    http://www.spack.org/download/interwiki.map

at least the version of phpwiki 1.3 i have doesn't work with some of them
though because it requires that the right hand side of the interwiki link
is a wiki word.

adam.

Re: [Phpwiki-talk] Element() and QElement() in lib/stdlib.php

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

On Sun, 11 Nov 2001 20:45:38 -0800 (PST)
"Adam Shand" <ad...@pe...> wrote:

> okay, will do, will there be an automated migration of data from the old
> one to the new one?  or will we just let people pick and choose what
they
> think is worth while?

As of four days ago, when Steve put up the new wiki, the contents were
identical.  I've been manually propagating non-Sandboxish changes
to the main (/phpwiki) wiki over to the new (/wiki) wiki.  So it
should all already be there (the good along with the bad.)

> no problem. to start with it'll mostly just be cut'n'paste from the
> mailing list but hopefully as the site becomes more and more useful
we'll
> get some community refactoring going on :)

That's a fine plan.

> Is there any reason that CategoryDocumentation or CategoryManual
> wouldn't work just as well?

No.

Re: [Phpwiki-talk] Element() and QElement() in lib/stdlib.php

[Adam S. <ad...@pe...>]

> > I'd vote for the new one (/wiki/).  I think we will be switching soon.

okay, will do, will there be an automated migration of data from the old
one to the new one?  or will we just let people pick and choose what they
think is worth while?

> Forgot to add: That would be great if you'd massage some of this stuff
> into the wiki!  Thanks very much.

no problem. to start with it'll mostly just be cut'n'paste from the
mailing list but hopefully as the site becomes more and more useful we'll
get some community refactoring going on :)

> Perhaps you could start a category tag (CategoryPhpWikiManual?) for
> pages which should be included in the phpwiki distribution.

is there a reason categories need to be wiki words?  is there any reason
that CategoryDocumentation or CategoryManual wouldn't work just as well?

adam.

Re: [Phpwiki-talk] Element() and QElement() in lib/stdlib.php

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

On Sun, 11 Nov 2001 19:41:09 -0800
"Jeff Dairiki" <da...@da...> wrote:

> On Sun, 11 Nov 2001 14:32:42 -0800 (PST)
> "Adam Shand" <ad...@pe...> wrote:
> 
> > so should i add content to the new /wiki/ or to the old /phpwiki/ ?
> 
> I'd vote for the new one (/wiki/).  I think we will be switching soon.


Forgot to add: That would be great if you'd massage some of this
stuff into the wiki!  Thanks very much.

Perhaps you could start a category tag (CategoryPhpWikiManual?) for
pages which should be included in the phpwiki distribution.

Jeff

Re: [Phpwiki-talk] Element() and QElement() in lib/stdlib.php

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

On Sun, 11 Nov 2001 14:32:42 -0800 (PST)
"Adam Shand" <ad...@pe...> wrote:

> so should i add content to the new /wiki/ or to the old /phpwiki/ ?

I'd vote for the new one (/wiki/).  I think we will be switching soon.

Re: [Phpwiki-talk] removing "index.php" from url

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

On Sun, 11 Nov 2001 22:18:25 +0100
"Tara Star" <te...@cl...> wrote:

> I see you (who?) did it for http://phpwiki.sourceforge.net/wiki/ - page 
> urls look like: http://phpwiki.sourceforge.net/wiki/PageName

Here's how it's done on the sourceforge site:

Phpwiki is installed in htdocs/phpwiki-1.3/.  So the wiki is available
the "normal" way through http://phpwiki.sf.net/phpwiki-1.3/index.php.

Then:

1. htdocs/phpwiki-1.3/index.php is copied to htdocs/wiki

2. Tell apache that htdocs/wiki is really a php script.
   As long as apache is configured to allow you to do this,
   (and you have a fairly recent apache) this is done by
   putting the following into htdocs/.htaccess:
      <Files wiki>
          SetHandler application/x-httpd-php
      </Files>

3. htdocs/wiki is edited as follows:
   a. Set include path so that the rest of the phpwiki code can be found.
      Something like:
        ini_set('include_path', 'phpwiki-1.3');
   b. Set DATA_PATH so that URLs to images and css get generated
      correctly.
        define('DATA_PATH', '/phpwiki-1.3');

That's it!  There are many ways to get this to work.  Study the comments
in index.php for some more hints.

Also if you do this kind of funnyness you're much more likely to uncover
arcane bugs, snakes and spiders.





 

Re: [Phpwiki-talk] plugin trouble

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

On Sun, 11 Nov 2001 21:45:55 +0100
"Tara Star" <te...@cl...> wrote:


> I have plugin problems, though: 
>
http://www.climbtothestars.org/spirolattic/index.php/LikePages?page=BackLinks

I just fixed it for you.  (It's fixed in CVS too.)
 
> and if I try inserting <?plugin BackLinks?> in a page, nothing happens.

Try <?plugin BackLinks page=[pagenamee]?>

As you've just noticed, the plugin argument conventions are:
 1) probably still in flux.
 2) not documented
It's alpha software.  Sorry.

> I was also wondering if there was a WikiPage somewhere about InterWiki 
> (I don't think it's shipped in the PhpWiki 1.3.1 package, but was there 
> one somewhere on PhpWiki?)
 
There's nothing that comes with PhpWiki.  Try UseMod:InterWiki at:
  http://www.usemod.com/cgi-bin/wiki.pl?InterWiki
Currently, 1.3's interwiki links are pretty much an exact clone of
UsemodWiki's

Re: [Phpwiki-talk] Element() and QElement() in lib/stdlib.php

[Adam S. <ad...@pe...>]

> It looks like you've figured out the answer already but just in case:
> The only difference is that QElement runs the element contents through
> htmlspecialchars().  Htmlspecialchars() encodes characters like '<',
> '>', '&', etc... as HTML entities ('&lt;', ...).

there's been some really good info coming out on the mailing list recently
and i've been wanting to put it up on the wiki site for future reference
but i'm not sure where i should put it.  i think i heard jeff/steve say
that /wiki/ was going to be the new main wiki but it appears to be using a
different set of page data then the main one ... so should i add content
to the new /wiki/ or to the old /phpwiki/ ?

adam.

[Phpwiki-talk] removing "index.php" from url

[Tara S. <te...@cl...>]

I see you (who?) did it for http://phpwiki.sourceforge.net/wiki/ - page=20
urls look like: http://phpwiki.sourceforge.net/wiki/PageName

How did you do it? with mod_rewrite or somewhere inside the php?

Thanks for any info (thanks to to all of you for your patience with my=20
tons of emails)

;)

Tara
--=20
Je r=E9ponds au mieux de mes connaissances
Climb to the Stars! - http://climbtothestars.org/
no tables: http://climbtothestars.org/coding/tableless/
Pompeurs Associ=E9s - http://pompage.net/