phpwiki-talk

Re: [Phpwiki-talk] interwiki

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

On Fri, 09 Nov 2001 20:47:50 +0100
"Tara Star" <te...@cl...> wrote:

> did I dream, or does 1.3.1 have inter-wiki functionality but I'm 
> incapable of finding it now?

It's there.  There's code in lib/interwiki.php.  The map data
is in lib/interwiki.map.

Try putting something like

  PhpWiki:FrontPage

in your SandBox.  You should get a link to the main PhpWiki wiki.

Re: [Phpwiki-talk] admin.php 1.2.1 problem

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

On Fri, 09 Nov 2001 20:13:32 +0100
"Tara Star" <te...@cl...> wrote:

> http://tara.scdi.org/wiki/admin.php won't load. The wiki is in a 
> .htpasswd protected directory (username: guest, password: star).


Oh.  Yes.   PhpWiki's authentication does not mix well with 
server handled HTTP authentication.

You are just hitting all the problems, aren't you?  :-)

For 1.2.x, I think the solution is to edit admin.php, and
delete or comment out the $adminpasswd checks.

Change:
   if (empty($wikiadmin) || empty($adminpasswd)) {
to
   if (empty($wikiadmin) /* || empty($adminpasswd) */) {

And:
   if (($PHP_AUTH_USER != $wikiadmin  )  ||
       ($PHP_AUTH_PW   != $adminpasswd)) {
to
   if (($PHP_AUTH_USER != $wikiadmin  )  /* ||
       ($PHP_AUTH_PW   != $adminpasswd)*/ ) {

Also set $wikiadmin to the username who you'd like to grant admin
privileges to.  I think (but I'm not certain --- so this might be
a security problem) that as long as apache is doing the authentication,
$PHP_AUTH_USER will always be set the the authentication user name.


For 1.3.x, at this point the solution is basically the same,
except you have to edit lib/WikiUser.php.

Comment out or delete line 148:
            if (!empty($passwd) && $passwd == ADMIN_PASSWD)
(but leave the next line intact.)

At line 160, change:
        if (!defined('ADMIN_USER') || !defined('ADMIN_PASSWD')
            || ADMIN_USER == '' || ADMIN_PASSWD =='') {
to
        if (!defined('ADMIN_USER') /* || !defined('ADMIN_PASSWD') */
            || ADMIN_USER == '' /* || ADMIN_PASSWD =='' */) {

And, as before, set ADMIN_USER (in index.php) to be the username
to whom you want to grant administrative privs.

(I haven't tested this hack with 1.3.x, so if you have trouble,
let me know.)  

(At some point, we'll stop using HTTP authenication to gather
the username/passwd, and this problem will go away.  But we're
not there yet.)

[Phpwiki-talk] interwiki

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

did I dream, or does 1.3.1 have inter-wiki functionality but I'm=20
incapable of finding it now?

--=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/

Re: [Phpwiki-talk] replaced INNER JOIN with LEFT JOIN - still WikiFatalError

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

Jeff Dairiki wrote:


> 1. Start 1.3.x with an empty database.  Browse the FrontPage.  This sho=
uld
> fill the wiki with the distributed default 1.3.x pgsrc.  (You've probab=
ly
> already gotten this far.)


done.


> 2. Make a zip dump of your 1.2 wiki.  If the contents of
> PhpWikiAdministration are correct there should be a links=20
> (near the top) which will do that for you.  You need to be
> in admin mode, though.  This means you must have set an
> admin user and passwd in admin.php, and you should be browsing
> through a URL like:
>   http://path.to.your/wiki/admin.php?PhpWikiAdministration
> (If your PhpWikAdministration page is broken, then
>   http://path.to.your/wiki/admin.php?zip=3Dall
> should get you a zip dump.)


do I do the zip dump from my 1.2 wiki or from the 1.3 one? It seems to=20
me you mean that I must make the dump in the 1.2 wiki, but I can't get=20
to the admin section (see my other mail to the list).

It's fun by the way, I'm getting old mail in bunches, as my dns=20
propagates I suppose. So I get the last conversations in patches (you'll=20
excuse me if some of my replies to those sound a bit out of context).


> 3. Now upload your zip dump to your new 1.3 wiki.  (First you need to
> have set the admin user/passwd in the new index.php.)  You should
> be able to use the "Upload File" form on the PhpWikiAdministration
> page.


ok, that sounds doable, once I've got the zip ;)


> If that works, the pages from your 1.2 wiki have now overwritten
> the 1.3 pages (though the 1.3 pages are still saved in the archive).


er... will the admin page know where to upload the zip dump? how will it=20
put the contents of the zip file in the db? *a bit confused*


> This will break a bunch of 1.3 functionality until you restore
> the page contents.  Of the top of my head, some pages for which=20
> this will be an issue are:
>   MostPopular, RecentChanges, PhpWikiAdministration,
>   MagicPhpWikiURLs, and ReleaseNotes.


ok, understood.


> To restore these pages to the original (1.3) contents:
 [snip]


that part looks ok.

Can anyone give ma a quick briefing on how the templates work, so I can=20
modify them without messing everything up?

Thanks,

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/

Re: [Phpwiki-talk] replaced INNER JOIN with LEFT JOIN - still WikiFatalError

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

On Fri, 09 Nov 2001 "Stephanie" <st...@po...> wrote:

> done:
> 
>   $maxmajor = "MAX(IF(minor_edit=0,version,NULL))";
>          $maxminor = "MAX(IF(minor_edit<>0,version,NULL))";
>          $maxversion = "MAX(version)";
> 
> it worked!

Yay!
 
> Now, say I want to migrate all my 1.2.1 pages. I need to do a zip dump 
> (does the admin page let me do that?) and then.... what?
 
It's still a bit of a messy process at this point.  Here's my suggestion.

1. Start 1.3.x with an empty database.  Browse the FrontPage.  This should
fill the wiki with the distributed default 1.3.x pgsrc.  (You've probably
already gotten this far.)

2. Make a zip dump of your 1.2 wiki.  If the contents of
PhpWikiAdministration are correct there should be a links 
(near the top) which will do that for you.  You need to be
in admin mode, though.  This means you must have set an
admin user and passwd in admin.php, and you should be browsing
through a URL like:
  http://path.to.your/wiki/admin.php?PhpWikiAdministration
(If your PhpWikAdministration page is broken, then
  http://path.to.your/wiki/admin.php?zip=all
should get you a zip dump.)

3. Now upload your zip dump to your new 1.3 wiki.  (First you need to
have set the admin user/passwd in the new index.php.)  You should
be able to use the "Upload File" form on the PhpWikiAdministration
page.


If that works, the pages from your 1.2 wiki have now overwritten
the 1.3 pages (though the 1.3 pages are still saved in the archive).
This will break a bunch of 1.3 functionality until you restore
the page contents.  Of the top of my head, some pages for which 
this will be an issue are:
  MostPopular, RecentChanges, PhpWikiAdministration,
  MagicPhpWikiURLs, and ReleaseNotes.

To restore these pages to the original (1.3) contents:

4a. Login as the administration user (using the SignIn button at the
bottom right corner of the page.)  (You need to do this because
some of the pages which need fixing are locked.)

4b. Browse to a page which needs restoring.  Hit the "History" button
(at the bottom of the page).  This should get you a list of all
archived versions of the page.

4c. Browse to the archive 1.3 version of the page (probably version number
1) by clicking on the version number of the desired version.

4d. Click the "Edit old revision" button (bottom of page).  This should
get you to the edit form.

4e. Click the "Save" button.  This should save the archived page contents
as the current contents.



We really need to figure out a way to simplify this process, but, for now,
that's what you gotta do.

Re: [Phpwiki-talk] linking scheme and markup - xhtml

[Stephanie B. <st...@cl...>]

Jeff Dairiki wrote:


> Thanks Gary & Reini for the XHTML primer.
> It seems XHTML is backwards compatible with HTML 4, if one takes
> certain precautions.  See
>   http://www.w3.org/TR/2001/WD-xhtml1-20011004/#guidelines

[snip]


> The biggest problem I see is in the transform code.  I know there's som=
e
> pretty kludgy code currently in 1.3 which is concerned with making sure
> the <p>s are properly </p>ed.  It would be nice to clean that up.


that's what made me cringe when i went to peek into the wiki code with=20
the hope of making it 100% xhtml compatible, with layout in css.


> (I am planning on re-writing the transform code sometime, to make
> fancy marked-up diff output possible, among other things.  But,
> as usual, it might be awhile before I get to it.)

I probably can't help much with the php stuff, though I'm

pretty proficient in matters xhtml (not that it's very complicated!) and=20
css, so if ever my assistance could be of any help, I'd be happy to=20
contribute.

I'm going to be hacking my wiki to make it spit out laundried code=20
anyway, so...

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/

[Phpwiki-talk] admin.php 1.2.1 problem

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

http://tara.scdi.org/wiki/admin.php won't load. The wiki is in a=20
.htpasswd protected directory (username: guest, password: star).

Any ideas?

browser status bar switches back and forth from connecting to...=20
connected... transferring... connecting... connected... transferring...


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/

Re: [Phpwiki-talk] replaced INNER JOIN with LEFT JOIN - still WikiFatalError

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

On Fri, 09 Nov 2001 18:46:06 +0100
"Tara Star" <te...@cl...> wrote:

Argh.  Okay, it seems CASE WHEN ... is unsupported in MySQL before
3.23.x.

(And I don't think postgres supports MySQL other conditional operators,
which is why I used the CASE WHEN...)

Try replacing
   CASE WHEN cond THEN val END
by
   IF(cond, val, NULL)

I.e. 
"CASE WHEN minor_edit=0 THEN version END" 
   becomes "IF(minor_edit=0,version,NULL)"
and

"CASE WHEN minor_edit<>0 THEN version END"
  becomes "IF(minor_edit<>0, version, NULL)"

At least you're making progress!

Jeff

[Phpwiki-talk] replaced INNER JOIN with LEFT JOIN - still WikiFatalError

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

I replaced INNER JOIN by LEFT JOIN, as suggested, and got the following=20
error:

Loading up virgin wiki

lib/WikiDB/backend/PearDB.php:653: Fatal[256]: wikidb_backend_mysql:=20
fatal database error

     * DB Error: syntax error<\li>
     * (INSERT INTO recent (id, latestversion, latestmajor, latestminor)=20
SELECT id, MAX(version), MAX(CASE WHEN minor_edit=3D0 THEN version END),=20
MAX(CASE WHEN minor_edit<>0 THEN version END) FROM version WHERE id=3D1=20
GROUP BY id [nativecode=3DYou have an error in your SQL syntax near 'WHEN=
=20
minor_edit=3D0 THEN version END), MAX(CASE WHEN minor_edit<>0 THEN versio=
n=20
EN' at line 1])<\li>
     * <\li>

lib/WikiDB/backend/PearDB.php:52: Notice[8]: Undefined property: _lock_co=
unt

lib/WikiDB/backend/PearDB.php:625: Notice[8]: Undefined property:=20
_lock_count

WikiFatalError

lib/WikiDB/backend/PearDB.php:653: Fatal[256]: wikidb_backend_mysql:=20
fatal database error

     * DB Error: syntax error<\li>
     * (INSERT INTO recent (id, latestversion, latestmajor, latestminor)=20
SELECT id, MAX(version), MAX(CASE WHEN minor_edit=3D0 THEN version END),=20
MAX(CASE WHEN minor_edit<>0 THEN version END) FROM version WHERE id=3D1=20
GROUP BY id [nativecode=3DYou have an error in your SQL syntax near 'WHEN=
=20
minor_edit=3D0 THEN version END), MAX(CASE WHEN minor_edit<>0 THEN versio=
n=20
EN' at line 1])<\li>
     * <\li>


http://tara.scdi.org/newwiki/ if you want to see the disaster. Any=20
suggestions?


--=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/

Re: [Phpwiki-talk] wysiwyg

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

> No, but it shouldn't be too difficult. Most of the functionality is
> encapsulated in RenderCalender() which is in stdlib.php -- the rest of
> the patch is just hooks.

hrm, cool.  maybe i'll check it out.  one of my main regrets is being a
sysadmin for so long ... i'm still such a shitty programmer :-(  i just
never needed to write any more then 100 lines of perl to get my job done
and most of that was all text file processing, not anything fun.

> Bear in mind that it uses the cal program, so Steve might not want it
> in the main tree as it won't work on Windows; you could always add
> this to the top of RenderCalender():

well if nothing else it could go in the contrib section.  i personally see
windows users as second class citizens but i understand that he wants it
as portable as possible.

> Most of the stuff I use for WikiAsPim uses existing wiki
> functionality, and I haven't needed to add anything else yet. I've
> been working on some other funky stuff, however, but I'm keeping quiet
> about it until I get it straight in my head. Stay tuned...

cool.  i look forward to it :)

adam.

Re: [Phpwiki-talk] linking scheme and markup

[Gary B. <ga...@in...>]

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.

Gary

[ ga...@in... ][ GnuPG 85A8F78B ][ http://inauspicious.org/ ]

Re: [Phpwiki-talk] linking scheme and markup

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

On Fri, 09 Nov 2001 10:24:46 +0000
"Reini Urban" <ru...@x-...> wrote:
 
> not really. xhtml is backwards compatible. 
> you can simply output xhtml and every browser will render it.


Thanks Gary & Reini for the XHTML primer.
It seems XHTML is backwards compatible with HTML 4, if one takes
certain precautions.  See
  http://www.w3.org/TR/2001/WD-xhtml1-20011004/#guidelines

As long as older browsers will have only minor-ish cosmetic problems
with XHTML, I do think it's time to make that move.  (The new CSS
stuff exhibits significant cosmetic problems on older (and some newer)
browsers, anyway.)

The biggest problem I see is in the transform code.  I know there's some
pretty kludgy code currently in 1.3 which is concerned with making sure
the <p>s are properly </p>ed.  It would be nice to clean that up.

(I am planning on re-writing the transform code sometime, to make
fancy marked-up diff output possible, among other things.  But,
as usual, it might be awhile before I get to it.)

Re: [Phpwiki-talk] wysiwyg

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

On Thu, 8 Nov 2001 22:37:02 -0800 (PST)
"Adam Shand" <ad...@pe...> wrote:

> ah, cool.  any plans to port it to 1.3? :-)

I've been planning on doing so.  Then again, I've been planning on
doing lots of things.  I think it's a pretty cool idea.

Re: [Phpwiki-talk] wysiwyg

[Gary B. <ga...@in...>]

On Thu, 8 Nov 2001, Adam Shand wrote:

> > The calender is available, but only for PhpWiki 1.2. You can find
> > every patch I ever wrote for PhpWiki at
> > http://inauspicious.org/files/phpwiki/
>
> ah, cool.  any plans to port it to 1.3? :-)

No, but it shouldn't be too difficult. Most of the functionality is
encapsulated in RenderCalender() which is in stdlib.php -- the rest of the
patch is just hooks.

Bear in mind that it uses the cal program, so Steve might not want it in
the main tree as it won't work on Windows; you could always add this to
the top of RenderCalender():

| if (!is_exec("/usr/bin/cal")) {
|     return "Get a proper OS!";
| }

:)

> > ToDo is just a page where I add random things I have to do, and it
> > also gets used as a WikiBadge.
>
> ah, good thought.  i thought you might have made another step towards the
> wiki as pim stuff and got all excited :)  speaking of which after our last
> exchange of email on that subject ... have you had any further thoughts on
> how/why to do it?

Most of the stuff I use for WikiAsPim uses existing wiki functionality,
and I haven't needed to add anything else yet. I've been working on some
other funky stuff, however, but I'm keeping quiet about it until I get it
straight in my head. Stay tuned...

Gary

[ ga...@in... ][ GnuPG 85A8F78B ][ http://inauspicious.org/ ]

Re: [Phpwiki-talk] linking scheme and markup

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

Steve Wainstead schrieb:
> 
> On Wed, 7 Nov 2001, Adam Shand wrote:
> > > I've wanted to do XHTML output for a while. That might be a good
> > > middle step for now.
> >
> > i like the idea of xml file storage.  this might make sense for the text
> > file backend as well.  convert wiki markup to xml and then xml to html.
> 
> Hmm. You remind me of an optimization I've thought about in the past: when
> a page is saved after editing, convert it to xhtml and store it. When
> pages are served, there's no transformation to do. 

http://phpwiki.sourceforge.net/phpwiki/index.php?PerformanceHacks

> When a page is pulled for editing, you have to convert it to wiki markup 
> again. The downside, of course, is twice as much code (converting between 
> the two formats).

not really. xhtml is backwards compatible. 
you can simply output xhtml and every browser will render it.

you probably mean to sore only xhtml and not the wiki markup in the db? 
hmm, weird idea.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: [Phpwiki-talk] wysiwyg

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

> The calender is available, but only for PhpWiki 1.2. You can find
> every patch I ever wrote for PhpWiki at
> http://inauspicious.org/files/phpwiki/

ah, cool.  any plans to port it to 1.3? :-)

> ToDo is just a page where I add random things I have to do, and it
> also gets used as a WikiBadge.

ah, good thought.  i thought you might have made another step towards the
wiki as pim stuff and got all excited :)  speaking of which after our last
exchange of email on that subject ... have you had any further thoughts on
how/why to do it?

adam.

[Phpwiki-talk] Zip dump bugh

[Malcolm R. <mal...@cs...>]

I was trying recently to upgrade my NomicWiki to PhpWiki 1.3.1 (it currently
uses 1.2). I tried to do a zip-dump of the existing wiki. I presume this is
done by logging in as admin and then accessing the page admin/zip.php (I
couldn't find any docs on this). When I do this, I get the error:

Call to undefined function: closedatabase() in zip.php on line 73.

I am using the default database (dba). 

Am I doing something wrong? Is there another way to do this? Where is the
zip dump that is generated sent to? Is this documented somewher that I
have missed?

Malcolm
-- 
Malcolm Ryan - mal...@cs... - http://www.cse.unsw.edu.au/~malcolmr/
  AI Dept, CSE, UNSW, Australia, Phone: +61 2 9385-6906 Fax: +61 2 9385-4936

           "He causes his sun to rise on the evil and the good,
           and sends rain on the righteous and the unrighteous." - Matt 5:45

Re: [Phpwiki-talk] wysiwyg

[Gary B. <ga...@in...>]

On Thu, 8 Nov 2001, Adam Shand wrote:

> > See a (slightly outdated) screenshot of my PersonalWiki at:
> > http://inauspicious.org/files/screenshots/calender-improved.png
>
> speaking of which, can you're calandar (and maybe todo judging by the
> screenshot) be contributed back?  is it a plugin?  it would be very
> useful.  could even put slashboxes below it :)

The calender is available, but only for PhpWiki 1.2. You can find every
patch I ever wrote for PhpWiki at http://inauspicious.org/files/phpwiki/

ToDo is just a page where I add random things I have to do, and it also
gets used as a WikiBadge.

Gary

[ ga...@in... ][ GnuPG 85A8F78B ][ http://inauspicious.org/ ]

Re: [Phpwiki-talk] wysiwyg

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

> See a (slightly outdated) screenshot of my PersonalWiki at:
> http://inauspicious.org/files/screenshots/calender-improved.png

speaking of which, can you're calandar (and maybe todo judging by the
screenshot) be contributed back?  is it a plugin?  it would be very
useful.  could even put slashboxes below it :)

adam.

Re: [Phpwiki-talk] linking scheme and markup

[Gary B. <ga...@in...>]

On Thu, 8 Nov 2001, Gary Benson wrote:

> If you are running your PhpWiki on your own webserver then you can put
> a reverse-proxy in front of it. This is what /. does if I remember
> correctly -- all pages have a five minute expiry time or something.

In fact, you could do away with the expiry time altogether if you hacked
PhpWiki to emit the relevant cache control headers and respond to the
requests appropriatly. Look at http://www.w3.org/Protocols/rfc2068/rfc2068
for the full gory details but basically you add ETag: and Last-modified:
headers on pages you send, and respond to If-Modified-Since: and
If-None-Match: headers in the requests (by returning a 304 Not Modified
instead of the page itself).

Oh, and /. doesn't have a proxy but they are considering it:
http://slashdot.org/article.pl?sid=01/09/13/154222&mode=thread

Re: [Phpwiki-talk] wysiwyg

[Gary B. <ga...@in...>]

On Thu, 8 Nov 2001, Steve Wainstead wrote:

> Yes, just yesterday I started on a "classicweb.css" style sheet. That was
> when I discovered I couldn't get a copy out of CVS on my laptop (OS X).
>
> It will have a beautiful gray background and everything else will be user
> defaults. To the extent possible.

If you wanted to offer more that one stylesheet and allow the user to
choose between them then it would be trivial to do with a ###STYLESHEET###
token (gets replaced with the URL) and a cookie.

Gary

[ ga...@in... ][ GnuPG 85A8F78B ][ http://inauspicious.org/ ]

Re: [Phpwiki-talk] linking scheme and markup

[Gary B. <ga...@in...>]

On Thu, 8 Nov 2001, Adam Shand wrote:

> > If you are running your PhpWiki on your own webserver then you can put
> > a reverse-proxy in front of it. This is what /. does if I remember
> > correctly -- all pages have a five minute expiry time or something.
>
> actually that's a good point, and should be fairly easy to do.

It is -- give me a shout off the list if you want a hand.
Gary

Re: [Phpwiki-talk] linking scheme and markup

[Gary B. <ga...@in...>]

On Wed, 7 Nov 2001, Jeff Dairiki wrote:

> What exactly are the practicalities involved in converting to XHTML?
> Is it really much of a new paradigm (if so, I don't see it yet) or is
> it just syntactical cleanup?

It's a syntactical cleanup. Chief differences are that

 a) there is no such thing as an empty tag: <hr> in HTML becomes <hr></hr>
    in XHTML. Since this would be a PITA, XHTML has the form <hr /> which
    is equivalent to <hr></hr>

 b) parsing is much stricter:
     | <ul>
     |   <li>foo
     |   <li>bar
     | </ul>
    is illegal in XHTML -- you must close the <li> tags:
     | <ul>
     |   <li>foo</li>
     |   <li>bar</li>
     | </ul>
    The rules of which tags may go where are more strictly enforced.

 c) tag attributes must be quoted. <img src=foo> is illegal: it should say
    <img src="foo"> or <img src='foo'>.

 d) it is case sensitive (all tags are lower case)

Everything on inauspicious.org -- apart from the PhpWiki-based wiki :) --
is valid XHTML -- view the source :)

> Steve, Tara, those who know: If we move to XHTML what are the
> implications for those who use older browsers?

Absolutely nothing -- XHTML was designed so that HTML compliant browsers
wouldn't choke on it. The only problem you get is that some seriously
broken browsers display <hr /> as if it was <hr>/ (ie the slash is
visible), but since such browsers are unlikely to render HTML properly
anyway it isn't worth worrying about.

Gary

[ ga...@in... ][ GnuPG 85A8F78B ][ http://inauspicious.org/ ]

Re: [Phpwiki-talk] linking scheme and markup

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

> If you are running your PhpWiki on your own webserver then you can put
> a reverse-proxy in front of it. This is what /. does if I remember
> correctly -- all pages have a five minute expiry time or something.

actually that's a good point, and should be fairly easy to do.

adam.

Re: [Phpwiki-talk] wysiwyg

[Gary B. <ga...@in...>]

On Thu, 8 Nov 2001, Sergio A. Kessler wrote:

> and a question: is there any plan to clean up the visual
> design of phpWiki ?
> after seeing wikis like http://openwiki.com/ phpWiki look
> dirty and baroque...

Just create some new templates -- you don't have to clean up the code.
See a (slightly outdated) screenshot of my PersonalWiki at:
http://inauspicious.org/files/screenshots/calender-improved.png

Gary

[ ga...@in... ][ GnuPG 85A8F78B ][ http://inauspicious.org/ ]