phpwiki-talk

Re: [Phpwiki-talk] No output on index.php

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

Martin Geisler schrieb:
> Good idea - that worked! I tracked the execution as far as to
> PearDB.php. It was the @require_once('DB.php'); statement that never
> returned - after I commented it out, everything worked again.
> 
> So it seams that the installation of Pear is broken at gimpster.com...
> it was very clever of you to provide a backup version of the DB class
> from Pear.

Even Sourcefroge has no uptodate pear/DB Class installation!

It was my fault. I added the default to try the system pear/DB version, 
and when this fails, the local version.
Seems that I have to add more checks (version compare?) and comments to 
this code. Or stick with our version. I know, we had this discussion 
before ....

My initial idea was that the pear version might eventually get updated, 
whilst the phpwiki version only about twice a year. Looks like most 
ISP's have a very old pear. And I understand. pear installation is a 
mess. I sent a feature request to the sf.net admins, and tested the 
update before locally. It didn't work there and it didn't work here on 
my machines.

Thanks for feedback.

BTW: The nightly CVS snapshot is currently very unstable.
UserAuthentication is in flux,
authorization (checking) is broken,
PagePermissions not yet added.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: [Phpwiki-talk] Better use of CVS

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

Jeff Dairiki schrieb:
> On Sat, 24 Aug 2002 17:19:52 -0400
> Steve Wainstead <sw...@pa...> wrote:
>>I have a modest proposal:
>>Tag code as usable with the cvs tag -F "tagname" option.
> 
> I don't know if others agree (they may well not), but
> my personal preference is that developers refrain
> from checking in known-to-be-non-functional code.
> 
> Personally, I have a personal PRCS repository set up which
> I use to track my edits as I'm working on larger changes.
> If modifications are made (by others) to the CVS code while
> I'm working, I can use my PRCS repository to merge the mods
> into my working files...
> Then, when I finally get everything (more or less) working,
> I check it in all at once, in an effort to leave the CVS
> is a broken state for as short a time as possible.
> 
> Still, having the demo/test wikis update from a tagged set
> is probably a good idea.
> 
> Another option is to only use the tag when the most recent
> version of the file is known broken.
>   cvs update -f -r WORKING_TEST
> Will update each file to the version tagged WORKING_TEST,
> if that tag exists for the file; otherwise it will update
> to the most recent version of the file.

It is a good idea to tag the stable from the unstable versions. My idea 
was to share my updates in flux with others to get immediate feedback on 
different setup's.
To attrack users to use this version I added some "cool" new features, 
before finishing the needed features.

Obviously a seperation between the new userauth and the latest additions 
and fixes which are independent would have been useful for you. But a 
lot of work for me. So I'm in a hurry to get it finished.

I'm for non-functional code, but I'm against broken code, of course.
But I can be persuaded.

This is my fault (as with the WikiUser typo lately). Normally I do an 
immediate cvs up on sf.net and check it. Thanks steve (and others) for 
fixing this.

> It might also be nice to make the test-wiki update script
> accessible/runnable by all the developers, so
> that when one makes changes he can immediately
> update the test wiki and check to see that it still works.
> 
> Maybe (via CVS scripts) this can even be done automatically,
> so that the test wiki is always in sync with CVS.

No need. A simple $ cvs up works for me.
Permissions are okay.

> Sorry to be so scattered.  I've not yet consumed enough
> coffee this Sunday morning...

And I didn't have my coffee this morning too. Thanks for reminding me.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: [Phpwiki-talk] No output on index.php

[Martin G. <gim...@gi...>]

Jeff Dairiki <da...@da...> writes:

> Hi Martin,
> 
> Oof.  I haven't a clue as to what your problem might be.
> It seems to be something that's causing a fundamental failure
> of PHP.   Have you checked your error_log?

No, I don't have access to the error_log as I don't have shell access
on the machine that hosts gimpster.com.
 
> If that doesn't show anything, then the next thing to do,
> I think, is to start adding temporary debugging print
> statements (starting at the top of index.php and working
> downwards and onwards through other php source) to determine
> how far things get before they crap out.

Good idea - that worked! I tracked the execution as far as to
PearDB.php. It was the @require_once('DB.php'); statement that never
returned - after I commented it out, everything worked again.

So it seams that the installation of Pear is broken at gimpster.com...
it was very clever of you to provide a backup version of the DB class
from Pear.

-- 
Martin Geisler                       My GnuPG Key: 0xF7F6B57B

See http://gimpster.com/ and http://phpweather.net/ for:
PHP Weather => Shows the current weather on your webpage and
PHP Shell   => A telnet-connection (almost :-) in a PHP page.

Re: [Phpwiki-talk] Better use of CVS

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

On Sat, 24 Aug 2002 17:19:52 -0400
Steve Wainstead <sw...@pa...> wrote:

> I have a modest proposal:
> 
> Tag code as usable with the cvs tag -F "tagname" option.

I don't know if others agree (they may well not), but
my personal preference is that developers refrain
from checking in known-to-be-non-functional code.

Personally, I have a personal PRCS repository set up which
I use to track my edits as I'm working on larger changes.
If modifications are made (by others) to the CVS code while
I'm working, I can use my PRCS repository to merge the mods
into my working files...
Then, when I finally get everything (more or less) working,
I check it in all at once, in an effort to leave the CVS
is a broken state for as short a time as possible.


Still, having the demo/test wikis update from a tagged set
is probably a good idea.

Another option is to only use the tag when the most recent
version of the file is known broken.
  cvs update -f -r WORKING_TEST
Will update each file to the version tagged WORKING_TEST,
if that tag exists for the file; otherwise it will update
to the most recent version of the file.



It might also be nice to make the test-wiki update script
accessible/runnable by all the developers, so
that when one makes changes he can immediately
update the test wiki and check to see that it still works.

Maybe (via CVS scripts) this can even be done automatically,
so that the test wiki is always in sync with CVS.

Sorry to be so scattered.  I've not yet consumed enough
coffee this Sunday morning...

Re: [Phpwiki-talk] No output on index.php

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

Hi Martin,

Oof.  I haven't a clue as to what your problem might be.
It seems to be something that's causing a fundamental failure
of PHP.   Have you checked your error_log?

If that doesn't show anything, then the next thing to do,
I think, is to start adding temporary debugging print
statements (starting at the top of index.php and working
downwards and onwards through other php source) to determine
how far things get before they crap out.

[Phpwiki-talk] No output on index.php

[Martin G. <gim...@gi...>]

Hi there!

I'm having a problem installing PhpWiki on my homepage at
gimpster.com, see

  http://gimpster.com/phpwiki/

I started by downloading and installing the latest CVS version (it has
so many cool features!) on my own machine running Apache and PHP
4.2.2. That worked flawlessly after I had changed the dba_handler. I
later changed it to use MySQL and that worked great too.

But things doesn't work on gimpster.com, I just get a blank page when
I try to view index.php after I've created the necessary tables in the
database. As you can see here, PHP version 4.2.2 is installed on
gimpster.com too:

  http://gimpster.com/info.php

The index.php file can be seen here:

  http://gimpster.com/showsource.php?file=/phpwiki/index.php

I've added a error_reporting(E_ALL) at the top to try and trigger
some sort of explanation, but it doesn't help at all.

Down in Part 2 I include my database password from an external file
and then set up the dsn. I haven't changed anything else.

Does anybody have a clue as to what can cause this behavior?

-- 
Martin Geisler                       My GnuPG Key: 0xF7F6B57B

See http://gimpster.com/ and http://phpweather.net/ for:
PHP Weather => Shows the current weather on your webpage and
PHP Shell   => A telnet-connection (almost :-) in a PHP page.

[Phpwiki-talk] Better use of CVS

[Steve W. <sw...@pa...>]

I have a modest proposal:

Tag code as usable with the cvs tag -F "tagname" option.

This means we could selectively update the demo site so it's less likely 
to be broken by bugs.  Currently the demo and test sites both do a 
checkout of the current files in CVS; for the test site, we don't mind 
if it gets broken since that's what it's there for. But to have the demo 
site down is egg on our faces.

For the cron job that updates the demo site, it would do a cvs update on 
the tag we choose.

The downside to this is it's one more hassle for the devloper. A more 
low tech solution is to disable the cron job entirely, and update the 
demo site by hand periodically when new functionality is ready.

~swain

[Phpwiki-talk] demo and test sites broken

[Steve W. <sw...@pa...>]

Demo is throwing an error because of WikiUser... I'm trying to fix the 
test site right now. It's giving a blank page.

http://phpwiki.sf.net/test/
http://phpwiki.sf.net/demo/

~swain

Re: [Phpwiki-talk] Email Notification question

[Steve W. <sw...@pa...>]

And to this thread I would add: Wikis are generally used for ad-hoc 
project documentation. This seems to be their killer application.

~swain

On Monday, August 19, 2002, at 12:10 PM, Aredridel wrote:

>>> A side note here: I do find it interesting that the Wiki isn't enough
>>> even for the hardcore Wiki lovers on this mailing list -- if it was
>>> enough, presumably the mailing list wouldn't be necessary, because
>>> you'd all be checking the Wiki regularly.
>
>>   Wiki is not designed as a groupware/messaging tool. It is designed to
>> give many people the ability to edit a document simultaneously, not
>> provide a forum for discussion.
>
> Wiki is odd in that it wasn't particularly designed for /any/ of it's
> uses.  On the other hand, it's simplicity of concept has made it better
> than a lot of solutions "designed" for a specific purpose.
>
> It has always been easy to say what Wiki is, though never with
> certainty that what you're saying is complete.  It's always been quite
> hard to say what it isn't.
>
>>   Would you use CVS to carry out a discussion? Would you use
>> Word/OpenOffice's "Track Changes" and "Merge Document" features to 
>> carry
>> out a discussion?
>
> Actually, CVS has turned into a discussion forum on the PLD Gnui/Linux
> distro system more than once... quite effective, having the discussed
> material so close at hand, and discussion as meta-data.
>
>>   The correct answer to both of these questions is "no". If you want a
>> discussion forum, use a tool that is designed for it (a web BBS, a 
>> mailing
>> list, etc). If you want different people on different networks to be 
>> able
>> to edit a document, use wiki.
>
> I rather disagree -- wikis make fantastic discussion tools, though with
> a few features added they are much more potent.
>
> That said, I also agree that I'd prefer a mailing list for discussion
> than a wiki -- I can answer email offline, and the queuing systems and
> batching of messages is far more sophisticated than Wiki.  Both are
> quite valid, but I quite prefer e-mail for discussion like this.
>
> Ari
>

[Phpwiki-talk] Fwd: Joining PHPWiki Team

[Steve W. <sw...@pa...>]

Welcome to Joby Walker, latest developer on the PhpWiki team. Joby has 
added subcategories in a private copy and is interested in porting it to 
the main tree. Happy hacking!

~swain

Begin forwarded message:

> From: Joby Walker <joby@u.washington.edu>
> Date: Wed Aug 21, 2002  01:51:13 PM US/Eastern
> To: Steve Wainstead <sw...@pa...>
> Subject: Re: Joining PHPWiki Team
>
> Were you going to add me as a developer?
>
> Souceforge account:  zorloc
>
> Thanks.
>
> jbw
>
> Steve Wainstead wrote:
>> If you have a sourceforge account, I can add you as a developer.
>> Also, if you could just make Pine a little easier to use with 
>> IMAP... ;-)
>> ~swain
>> Joby Walker wrote:
>>> Hello,
>>>
>>> I am currently using PhpWiki for a documentation project for the 
>>> University of Washington's Operations, using 1.3.3 so far.  I have 
>>> done some dev work to impliment some features required by our 
>>> project.  I would love to work with you guys to port them (in some 
>>> form) to the CVS tree and generally assist in the development of 
>>> PhpWiki.  I have both work and personal time which I already spend on 
>>> the project -- usually 6+ hours a day.
>>>
>>> Most of the work I have done so far is to impliment a new 
>>> categorization system.  Instead of using "Category____" pages, I have 
>>> added to the database (just PostgreSQL ... since that's all I use) 
>>> tables to store (sub)categories and the page links.  An infinite 
>>> level of subcategorization is possible.  Additionally pages can 
>>> belong to multiple categories.  Every categorized page has a link to 
>>> it's (sub)category and that (sub)categories parents, which links to 
>>> an Index page which using a DHTML tree you can dynamically browse the 
>>> entire tree.
>>>
>>> Let me know how I can participate.
>>>
>>> jbw
>>> ---------------------
>>> joby@u.washington.edu
>>> UCS Operations SSG
>>> University of Washington
>>>
>>>
>>>
>
>
>
>

[Phpwiki-talk] Ginseng Tea

[<gin...@16...>]

=3CBODY bgColor=3D#ffffff=3E
=3CDIV=3E=3CFONT size=3D2=3E
=3CP align=3Dcenter class=3DMsoNormal 
style=3D=22TEXT-ALIGN=3A center=3B mso-layout-grid-align=3A none=22=3E=3CIMG alt=3D=22=22 border=3D0 
hspace=3D0 src=3D=22http=3A=2F=2Fwww=2Ewldinfo=2Ecom=2FNAC=2Fginsengtea=2Fginsengn=2Egif=22=3E=3CIMG alt=3D=22=22 
border=3D0 hspace=3D0 
src=3D=22http=3A=2F=2Fwww=2Ewldinfo=2Ecom=2FNAC=2Fginsengtea=2Fginseng=2EPNG=22=3E=3CB=3E=3CSPAN 
style=3D=22FONT-SIZE=3A 10pt=3B mso-font-kerning=3A 0pt=22=3E=3C=3Fxml=3Anamespace prefix =3D o ns =3D 
=22urn=3Aschemas-microsoft-com=3Aoffice=3Aoffice=22 =2F=3E=3Co=3Ap=3E&nbsp=3B=3C=2Fo=3Ap=3E=3C=2FSPAN=3E=3C=2FB=3E=3C=2FP=3E
=3CP align=3Dcenter class=3DMsoNormal 
style=3D=22TEXT-ALIGN=3A center=3B mso-layout-grid-align=3A none=22=3E=3CB=3E=3CSPAN 
style=3D=22FONT-SIZE=3A 10pt=3B mso-font-kerning=3A 0pt=22=3EGINSENG-TEA=3C=2FSPAN=3E=3C=2FB=3E=3CSPAN 
style=3D=22FONT-FAMILY=3A SimSun=3B FONT-SIZE=3A 10pt=3B mso-font-kerning=3A 0pt=22=3E=3CBR=3E=3CSPAN 
style=3D=22mso-spacerun=3A yes=22=3E=3F=3C=2FSPAN=3E=3Co=3Ap=3E=3C=2Fo=3Ap=3E=3C=2FSPAN=3E=3C=2FP=3E
=3CP align=3Dleft class=3DMsoNormal 
style=3D=22TEXT-ALIGN=3A left=3B mso-layout-grid-align=3A none=22=3E=3CSPAN 
style=3D=22FONT-FAMILY=3A 'Courier New'=3B FONT-SIZE=3A 10pt=3B mso-font-kerning=3A 0pt=22=3EWant 
to feel energetic and youthful=3F Drink ginseng tea! Want to improve your blood 
sugar level=2C mental status=2C cholesterol level and blood pressure=3F Drink ginseng 
tea! Just want to feel better=3F Drink ginseng tea!=3Co=3Ap=3E=3C=2Fo=3Ap=3E=3C=2FSPAN=3E=3C=2FP=3E
=3CTABLE border=3D1 cellPadding=3D0 cellSpacing=3D0 class=3DMsoNormalTable height=3D1 
style=3D=22BORDER-BOTTOM=3A medium none=3B BORDER-COLLAPSE=3A collapse=3B BORDER-LEFT=3A medium none=3B BORDER-RIGHT=3A medium none=3B BORDER-TOP=3A medium none=3B mso-border-alt=3A solid windowtext =2E5pt=3B mso-padding-alt=3A 0in 5=2E4pt 0in 5=2E4pt=22 
width=3D665=3E
  =3CTBODY=3E
  =3CTR style=3D=22mso-yfti-irow=3A 0=3B mso-yfti-lastrow=3A yes=22=3E
    =3CTD height=3D1 
    style=3D=22BORDER-BOTTOM=3A windowtext 1pt solid=3B BORDER-LEFT=3A windowtext 1pt solid=3B BORDER-RIGHT=3A windowtext 1pt solid=3B BORDER-TOP=3A windowtext 1pt solid=3B PADDING-BOTTOM=3A 0in=3B PADDING-LEFT=3A 5=2E4pt=3B PADDING-RIGHT=3A 5=2E4pt=3B PADDING-TOP=3A 0in=3B WIDTH=3A 102px=3B mso-border-alt=3A solid windowtext =2E75pt=22 
    vAlign=3Dtop=3E
      =3CP align=3Dleft class=3DMsoNormal 
      style=3D=22TEXT-ALIGN=3A left=3B mso-layout-grid-align=3A none=22=3E=3CSPAN 
      style=3D=22FONT-FAMILY=3A 'Courier New'=3B FONT-SIZE=3A 10pt=3B mso-font-kerning=3A 0pt=22=3E=3Co=3Ap=3E&nbsp=3B=3C=2Fo=3Ap=3E=3C=2FSPAN=3E=3C=2FP=3E
      =3CP align=3Dleft class=3DMsoNormal 
      style=3D=22TEXT-ALIGN=3A left=3B mso-layout-grid-align=3A none=22=3E=3CIMG alt=3D=22=22 border=3D0 
      hspace=3D0 src=3D=22http=3A=2F=2Fwww=2Ewldinfo=2Ecom=2FNAC=2Fginsengtea=2Fleaf=2Egif=22=3E=3C=2FP=3E=3C=2FTD=3E
    =3CTD height=3D1 
    style=3D=22BORDER-BOTTOM=3A windowtext 1pt solid=3B BORDER-LEFT=3A medium none=3B BORDER-RIGHT=3A windowtext 1pt solid=3B BORDER-TOP=3A windowtext 1pt solid=3B PADDING-BOTTOM=3A 0in=3B PADDING-LEFT=3A 5=2E4pt=3B PADDING-RIGHT=3A 5=2E4pt=3B PADDING-TOP=3A 0in=3B WIDTH=3A 532px=3B mso-border-alt=3A solid windowtext =2E75pt=3B mso-border-left-alt=3A solid windowtext =2E75pt=22 
    vAlign=3Dtop=3E
      =3CP align=3Dleft class=3DMsoNormal 
      style=3D=22TEXT-ALIGN=3A left=3B mso-layout-grid-align=3A none=22=3E=3CB=3E=3CSPAN 
      style=3D=22FONT-FAMILY=3A 'Courier New'=3B FONT-SIZE=3A 10pt=3B mso-font-kerning=3A 0pt=22=3EPackage=3A 
      =3C=2FSPAN=3E=3C=2FB=3E=3CSPAN 
      style=3D=22FONT-FAMILY=3A 'Courier New'=3B FONT-SIZE=3A 10pt=3B mso-font-kerning=3A 0pt=22=3E100 
      bags per box =28paper or wooden=29=2E=3CSPAN style=3D=22mso-spacerun=3A yes=22=3E&nbsp=3B 
      =3C=2FSPAN=3E0=2E07oz =282g=29 x 100bags=2Fpaper box =3CB=3Eor=3C=2FB=3E 0=2E105oz =283g=29 X 
      100bags=2Fwooden box=2E =3C=2FSPAN=3E=3C=2FP=3E
      =3CP align=3Dleft class=3DMsoNormal 
      style=3D=22TEXT-ALIGN=3A left=3B mso-layout-grid-align=3A none=22=3E=3CB=3E=3CSPAN 
      style=3D=22FONT-FAMILY=3A 'Courier New'=3B FONT-SIZE=3A 7=2E5pt=3B mso-font-kerning=3A 0pt=22=3EDisclaimer=3CI=3E=3A 
      =3C=2FI=3E=3C=2FSPAN=3E=3C=2FB=3E=3CSPAN 
      style=3D=22FONT-FAMILY=3A 'Courier New'=3B FONT-SIZE=3A 7=2E5pt=3B mso-font-kerning=3A 0pt=22=3EThe 
      presentation here is for informational only and is not meant to substitute 
      for the advice from your physician or health care professional=2E=3CSPAN 
      style=3D=22mso-spacerun=3A yes=22=3E=3F =3C=2FSPAN=3ESince it=3Fs not been evaluated by FDA=2C 
      it is not intended to diagnose=2C treat=2C cure=2C or prevent any 
      disease=2E=3C=2FSPAN=3E=3C=2FP=3E
      =3CP align=3Dleft class=3DMsoNormal 
      style=3D=22TEXT-ALIGN=3A left=3B mso-layout-grid-align=3A none=22=3E=3CB=3E=3CFONT 
      color=3D#800080 face=3D=22Courier New=22 size=3D2=3EToll Free Number=3A=3C=2FFONT=3E=3CFONT 
      color=3D#800080 face=3D=22Arial Narrow=22 size=3D3=3E1-877-892-4948 =3C=2FFONT=3E=3C=2FB=3E=3C=2FP=3E
      =3CP align=3Dleft class=3DMsoNormal 
      style=3D=22TEXT-ALIGN=3A left=3B mso-layout-grid-align=3A none=22=3E&nbsp=3B=3C=2FP=3E
      =3CP align=3Dleft class=3DMsoNormal 
      style=3D=22TEXT-ALIGN=3A left=3B mso-layout-grid-align=3A none=22=3E&nbsp=3B=3C=2FP=3E=3C=2FTD=3E=3C=2FTR=3E=3C=2FTBODY=3E=3C=2FTABLE=3E
=3CP align=3Dleft class=3DMsoNormal 
style=3D=22TEXT-ALIGN=3A left=3B mso-layout-grid-align=3A none=22=3E=3CB=3E=3CSPAN 
style=3D=22FONT-FAMILY=3A 'Courier New'=3B FONT-SIZE=3A 10pt=3B mso-font-kerning=3A 0pt=22=3E=3Co=3Ap=3E&nbsp=3B=3C=2Fo=3Ap=3E=3C=2FSPAN=3E=3C=2FB=3E=3C=2FP=3E
=3CP align=3Dleft class=3DMsoNormal 
style=3D=22TEXT-ALIGN=3A left=3B mso-layout-grid-align=3A none=22=3E&nbsp=3B=3C=2FP=3E
=3CP align=3Dleft class=3DMsoNormal 
style=3D=22TEXT-ALIGN=3A left=3B mso-layout-grid-align=3A none=22=3E=3CSPAN 
class=3DSpellE=3E=3CB=3E=3CU=3E=3CSPAN 
style=3D=22COLOR=3A blue=3B FONT-FAMILY=3A 'Courier New'=3B FONT-SIZE=3A 12pt=3B mso-font-kerning=3A 0pt=22=3E=3CSPAN 
class=3DGramE=3E=3CSPAN 
style=3D=22FONT-SIZE=3A 10pt=3B TEXT-DECORATION=3A none=3B text-underline=3A none=22=3EDON=3FT=3C=2FSPAN=3E=3C=2FSPAN=3E=3C=2FSPAN=3E=3C=2FU=3E=3C=2FB=3E=3C=2FSPAN=3E=3CSPAN 
style=3D=22FONT-FAMILY=3A 'Courier New'=3B FONT-SIZE=3A 10pt=3B mso-font-kerning=3A 0pt=22=3E=3CB=3E=3CFONT 
color=3D#0000ff=3E REPLY TO THIS E-MAIL DIRECTLY=3C=2FFONT=3E=3C=2FB=3E=2E To order=2C simply 
complete the order form below and =3CFONT color=3D#800080=3Efax it back to 
1-772-673-7969=3C=2FFONT=3E=2E Make sure to give your email address so that we can send 
you a receipt=2E We prefer the payment by =3CFONT color=3D#800080=3E=3CB=3E=3CSPAN 
class=3DSpellE=3E=3CA href=3D=22http=3A=2F=2Fwww=2Epaypal=2Ecom=2F=22 
target=3D=5Fblank=3EPaypal=3C=2FA=3E--=3C=2FSPAN=3E=3C=2FB=3E=3C=2FFONT=3EID is =3CFONT 
color=3D#800080=3E=3CB=3Efreshmeadow=40etang=2Ecom=3C=2FB=3E=2E=3C=2FFONT=3E If ordering more than one 
box=2C please fax your request for pricing &amp=3B shipping=2E =3Co=3Ap=3E=3C=2Fo=3Ap=3E=3C=2FSPAN=3E=3C=2FP=3E
=3CP align=3Dleft class=3DMsoNormal 
style=3D=22TEXT-ALIGN=3A left=3B mso-layout-grid-align=3A none=22=3E=3CSPAN 
style=3D=22FONT-FAMILY=3A 'Courier New'=3B FONT-SIZE=3A 10pt=3B mso-font-kerning=3A 0pt=22=3E=3Co=3Ap=3E&nbsp=3B=3C=2Fo=3Ap=3E=3C=2FSPAN=3E=3C=2FP=3E
=3CP align=3Dleft class=3DMsoNormal 
style=3D=22TEXT-ALIGN=3A left=3B mso-layout-grid-align=3A none=22=3E=3CB=3E=3CSPAN 
style=3D=22FONT-FAMILY=3A 'Courier New'=3B FONT-SIZE=3A 10pt=3B mso-font-kerning=3A 0pt=22=3EORDER 
FORM=3C=2FSPAN=3E=3C=2FB=3E=3CSPAN 
style=3D=22FONT-FAMILY=3A 'Courier New'=3B FONT-SIZE=3A 10pt=3B mso-font-kerning=3A 0pt=22=3E 
=3Co=3Ap=3E=3C=2Fo=3Ap=3E=3C=2FSPAN=3E=3C=2FP=3E
=3CP align=3Dleft class=3DMsoNormal 
style=3D=22TEXT-ALIGN=3A left=3B mso-layout-grid-align=3A none=22=3E=3CSPAN 
style=3D=22FONT-FAMILY=3A 'Courier New'=3B FONT-SIZE=3A 10pt=3B mso-font-kerning=3A 0pt=22=3EFull 
Name=3CSPAN class=3DGramE=3E=3A=5F=3C=2FSPAN=3E=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F Email 
Address=3A=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=3Co=3Ap=3E=3C=2Fo=3Ap=3E=3C=2FSPAN=3E=3C=2FP=3E
=3CP align=3Dleft class=3DMsoNormal 
style=3D=22TEXT-ALIGN=3A left=3B mso-layout-grid-align=3A none=22=3E=3CSPAN class=3DSpellE=3E=3CSPAN 
style=3D=22FONT-FAMILY=3A 'Courier New'=3B FONT-SIZE=3A 10pt=3B mso-font-kerning=3A 0pt=22=3ETel=3CSPAN 
class=3DGramE=3E=3A=5F=3C=2FSPAN=3E=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5FFax=3C=2FSPAN=3E=3C=2FSPAN=3E=3CSPAN 
style=3D=22FONT-FAMILY=3A 'Courier New'=3B FONT-SIZE=3A 10pt=3B mso-font-kerning=3A 0pt=22=3E=3A=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F 
=3Co=3Ap=3E=3C=2Fo=3Ap=3E=3C=2FSPAN=3E=3C=2FP=3E
=3CP align=3Dleft class=3DMsoNormal 
style=3D=22TEXT-ALIGN=3A left=3B mso-layout-grid-align=3A none=22=3E=3CSPAN 
style=3D=22FONT-FAMILY=3A 'Courier New'=3B FONT-SIZE=3A 10pt=3B mso-font-kerning=3A 0pt=22=3EShipping 
Address=3CSPAN class=3DGramE=3E=3A=5F=3C=2FSPAN=3E=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F City=3A=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F 
State=2F=3CSPAN class=3DSpellE=3EProvince=3A=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5FZIP=3C=2FSPAN=3E=2FPostal=3A=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F 
Country=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F =3Co=3Ap=3E=3C=2Fo=3Ap=3E=3C=2FSPAN=3E=3C=2FP=3E
=3CP align=3Dleft class=3DMsoNormal 
style=3D=22TEXT-ALIGN=3A left=3B mso-layout-grid-align=3A none=22=3E=3CSPAN 
style=3D=22FONT-FAMILY=3A 'Courier New'=3B FONT-SIZE=3A 10pt=3B mso-font-kerning=3A 0pt=22=3E=3Co=3Ap=3E&nbsp=3B=3C=2Fo=3Ap=3E=3C=2FSPAN=3E=3C=2FP=3E
=3CP align=3Dleft class=3DMsoNormal 
style=3D=22TEXT-ALIGN=3A left=3B mso-layout-grid-align=3A none=22=3E=3CB=3E=3CSPAN 
style=3D=22FONT-FAMILY=3A 'Courier New'=3B FONT-SIZE=3A 10pt=3B mso-font-kerning=3A 0pt=22=3EPRICE=3C=2FSPAN=3E=3C=2FB=3E=3CSPAN 
style=3D=22FONT-FAMILY=3A 'Courier New'=3B FONT-SIZE=3A 10pt=3B mso-font-kerning=3A 0pt=22=3E=3A =5B=5D 
0=2E07ozx100bags=2Fpaper box $25=2E95 =5B=5D 0=2E105ozx100bags=2Fwooden box $ 
31=2E95=3Co=3Ap=3E=3C=2Fo=3Ap=3E=3C=2FSPAN=3E=3C=2FP=3E
=3CP align=3Dleft class=3DMsoNormal 
style=3D=22TEXT-ALIGN=3A left=3B mso-layout-grid-align=3A none=22=3E=3CSPAN 
style=3D=22FONT-FAMILY=3A 'Courier New'=3B FONT-SIZE=3A 10pt=3B mso-font-kerning=3A 0pt=22=3E=3CSPAN 
style=3D=22mso-spacerun=3A yes=22=3E=3F=3C=2FSPAN=3E=3Co=3Ap=3E=3C=2Fo=3Ap=3E=3C=2FSPAN=3E=3C=2FP=3E
=3CP align=3Dleft class=3DMsoNormal 
style=3D=22TEXT-ALIGN=3A left=3B mso-layout-grid-align=3A none=22=3E=3CB=3E=3CSPAN 
style=3D=22FONT-FAMILY=3A 'Courier New'=3B FONT-SIZE=3A 10pt=3B mso-font-kerning=3A 0pt=22=3ESHIPPING 
OPTIONS=3C=2FSPAN=3E=3C=2FB=3E=3CSPAN 
style=3D=22FONT-FAMILY=3A 'Courier New'=3B FONT-SIZE=3A 10pt=3B mso-font-kerning=3A 0pt=22=3E=3A =5B=5D 
Priority Mail =281-2 weeks=29 $6 =5B=5D Express Mail $15=3Co=3Ap=3E=3C=2Fo=3Ap=3E=3C=2FSPAN=3E=3C=2FP=3E
=3CP align=3Dleft class=3DMsoNormal 
style=3D=22TEXT-ALIGN=3A left=3B mso-layout-grid-align=3A none=22=3E=3CSPAN 
style=3D=22FONT-FAMILY=3A 'Courier New'=3B FONT-SIZE=3A 10pt=3B mso-font-kerning=3A 0pt=22=3ETOTAL 
AMOUNT=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F =3Co=3Ap=3E=3C=2Fo=3Ap=3E=3C=2FSPAN=3E=3C=2FP=3E
=3CP align=3Dleft class=3DMsoNormal 
style=3D=22TEXT-ALIGN=3A left=3B mso-layout-grid-align=3A none=22=3E=3CSPAN 
style=3D=22FONT-FAMILY=3A 'Courier New'=3B FONT-SIZE=3A 10pt=3B mso-font-kerning=3A 0pt=22=3E=3Co=3Ap=3E&nbsp=3B=3C=2Fo=3Ap=3E=3C=2FSPAN=3E=3C=2FP=3E
=3CP align=3Dleft class=3DMsoNormal 
style=3D=22TEXT-ALIGN=3A left=3B mso-layout-grid-align=3A none=22=3E=3CB=3E=3CSPAN 
style=3D=22FONT-FAMILY=3A 'Courier New'=3B FONT-SIZE=3A 10pt=3B mso-font-kerning=3A 0pt=22=3ES 
&amp=3B H=3A =3C=2FSPAN=3E=3C=2FB=3E=3CSPAN 
style=3D=22FONT-FAMILY=3A 'Courier New'=3B FONT-SIZE=3A 10pt=3B mso-font-kerning=3A 0pt=22=3EShipping 
to PO Box will be delivered by U=2ES=2E mail only=2E For int=3Fl orders=2C please fax 
request to 1-772-673-7969=2E For California residents=2C the sales tax of 8=2E25% 
applies=2E All duties and taxes for international orders are the responsibilities 
of recipients=2E =3C=2FSPAN=3E=3C=2FP=3E
=3CP align=3Dleft class=3DMsoNormal 
style=3D=22TEXT-ALIGN=3A left=3B mso-layout-grid-align=3A none=22=3E&nbsp=3B=3C=2FP=3E
=3CP align=3Dleft class=3DMsoNormal 
style=3D=22TEXT-ALIGN=3A left=3B mso-layout-grid-align=3A none=22=3E=3CSPAN 
style=3D=22FONT-FAMILY=3A 'Courier New'=3B mso-font-kerning=3A 0pt=22=3ETo be removed=2C please 
=3CU=3E=3CSPAN style=3D=22COLOR=3A blue=22=3E=3CA 
href=3D=22mailto=3Aginsengremove=40163=2Ecom=22=3Emailto=3Aginsengremove=40163=2Ecom=3C=2FA=3E 
=3C=2FSPAN=3E=3C=2FU=3Ewith =22=3CB=3Eremove=3C=2FB=3E=22 in subject line=2E=3Co=3Ap=3E=3C=2Fo=3Ap=3E=3C=2FSPAN=3E=3C=2FP=3E
=3CP class=3DMsoNormal=3E=3CSPAN class=3DMsoHyperlink=3E=3CSPAN 
style=3D=22FONT-FAMILY=3A 'Courier New'=3B mso-font-kerning=3A 0pt=22=3E=3Co=3Ap=3E=3CSPAN 
style=3D=22TEXT-DECORATION=3A none=22=3E&nbsp=3B=3C=2FSPAN=3E=3C=2Fo=3Ap=3E=3C=2FSPAN=3E=3C=2FSPAN=3E=3C=2FP=3E
=3CP class=3DMsoNormal=3E=3CSPAN class=3DMsoHyperlink=3E=3CSPAN 
style=3D=22FONT-FAMILY=3A 'Courier New'=3B mso-font-kerning=3A 0pt=22=3E=3Co=3Ap=3E=3CSPAN 
style=3D=22TEXT-DECORATION=3A none=22=3E=3C=2FSPAN=3E=3C=2Fo=3Ap=3E=3C=2FSPAN=3E=3C=2FSPAN=3E&nbsp=3B=3C=2FP=3E
=3CP class=3DMsoNormal=3E=3CSPAN class=3DMsoHyperlink=3E=3CSPAN 
style=3D=22FONT-FAMILY=3A 'Courier New'=3B mso-font-kerning=3A 0pt=22=3E=3Co=3Ap=3E=3CSPAN 
style=3D=22TEXT-DECORATION=3A none=22=3E=3C=2FSPAN=3E=3C=2Fo=3Ap=3E=3C=2FSPAN=3E=3C=2FSPAN=3E&nbsp=3B=3C=2FP=3E=3C=2FFONT=3E=3C=2FDIV=3E=3C=2FBODY=3E

[Phpwiki-talk] backlinks for page names that end in a number

[Cliff B. <cb...@ac...>]

I am having trouble getting backlinks to work with page names that end in=
 a=20
number.  Ex: [EG2]

Has anyone else seen this problem?

Thanks,
Cliff

Re: [Phpwiki-talk] Results of trying Jeff's suggestions

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

On Thu, 22 Aug 2002 11:41:45 -0400
xi...@yi... wrote:

> Parse error: parse error, unexpected ';', expecting T_OLD_FUNCTION or 
> T_FUNCTION or T_VAR or '}' 
> in /home/mysite/public_html/wiki/04/lib/WikiUser.php on line 165
> 
> Fatal error: Cannot instantiate non-existent class: wikiuser 
> in /home/mysite/public_html/wiki/04/lib/main.php on line 139  

That all just means there's a syntax error in WikiUser.php
somewhere.  (Presumably the part just changed.)
Send me (privately --- not on list) a copy of your WikiUser.php,
and I'll see if I can spot the problem.


> ----
> 
> Now, in main.php there are the lines:
> 
>             case 'edit':
>                 if (defined('REQUIRE_SIGNIN_BEFORE_EDIT') && 
> REQUIRE_SIGNIN_BEFORE_EDIT)
>                     return WIKIAUTH_BOGO;
>                 return WIKIAUTH_ANON;
>                 // return WIKIAUTH_BOGO;
> 
> ----
> 
> and I was wondering if maybe something needs to be added there to 
> include another instance (maybe 'return WIKIAUTH_USER;' ?)...

The method which those lines are in is responsible for reporting
the minimum level of authentication (or authority) neede to perform
a given action.  The section of code you've quoted above says:
if REQUIRE_SIGNIN_BEFORE_EDIT has been set, then users must have
authenticated themselves at least to the bogo-login level (any
authentication level higher than that --- either _USER or _ADMIN ---
is okay too.); and if REQUIRE_SIGNIN_... has not been set, then
anyone can perform action 'edit'.  (WIKIAUTH_ANON is the lowest
authentication level.)


Your current problem is (only) the syntax error in WikiUser.php
around line 165.

[Phpwiki-talk] Results of trying Jeff's suggestions

[<xi...@yi...>]

Thank you, Jeff, for putting out the code so quickly for allowing BOGO 
login along with restricted user and admin. That part of it worked 
great, so far as I can tell.

The second part (adding a password for the BOGO login) kept generating 
this error message:

Parse error: parse error, unexpected ';', expecting T_OLD_FUNCTION or 
T_FUNCTION or T_VAR or '}' 
in /home/mysite/public_html/wiki/04/lib/WikiUser.php on line 165

Fatal error: Cannot instantiate non-existent class: wikiuser 
in /home/mysite/public_html/wiki/04/lib/main.php on line 139  

----

Now, in main.php there are the lines:

            case 'edit':
                if (defined('REQUIRE_SIGNIN_BEFORE_EDIT') && 
REQUIRE_SIGNIN_BEFORE_EDIT)
                    return WIKIAUTH_BOGO;
                return WIKIAUTH_ANON;
                // return WIKIAUTH_BOGO;

----

and I was wondering if maybe something needs to be added there to 
include another instance (maybe 'return WIKIAUTH_USER;' ?) but just 
putting that line in didn't seem to help and of course I was uncertain 
exactly how or where (or whether) to do this. Maybe I needed to 
uncomment the 'return WIKIAUTH_BOGO;' (then again, there are two of 
them...)?? I didn't try that.

So if you can clue me in on what needs to be done to make this 
(passworded BOGO, with restricted user, admin and a side order of 
fries) happen, it will be much appreciated.

You guys are great, and it is really exciting seeing this take shape. 
Thanks again!       

-----------------------------------------------------
http://eo.yifan.net
Free POP3/Web Email, File Manager, Calendar and Address Book

Re: [Phpwiki-talk] Simple security revisited

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

> I now have one wiki set up with one user and one admin, and 
> another set up with the admin and BOGO login enabled. The next thing I 
> am wondering is: A) can BOGO login be enabled in the case where there 
> is one authorized user in addition to the admin (to create a sort of 
> super-user whose ID cannot be spoofed by the BOGO users)?

Yes. Here's the untested instructions:

in lib/WikiUser.php, change _pwcheck to:

      function _pwcheck ($userid, $passwd) {
          global $WikiNameRegexp;
         
          if (!empty($userid) && $userid == ADMIN_USER) {
              if (!empty($passwd) && $passwd == ADMIN_PASSWD)
                  return WIKIAUTH_ADMIN;
              return false;
          }
          elseif (!empty($userid) && $userid == RESTRICTED_USER) {
              if (!empty($passwd) && $passwd == RESTRICTED_PASSWD)
                  return WIKIAUTH_USER;
              return false;
          }
          elseif (ALLOW_BOGO_LOGIN
                  && preg_match('/\A' . $WikiNameRegexp . '\z/', $userid))
{
              return WIKIAUTH_BOGO;
          }
          return false;
      }

(The first elseif clause is the only part which differs from
the stock PhpWiki code.)  This change will work for all three
cases outlined above, if in the case where there is no restricted
user, one sets RESTRICTED_USER and RESTRICTED to false.

Then, if you want to allow BOGO logins (as well as admin and
password-verified user) to edit pages, restore lib/main.php
to stock code (and set REQUIRE_SIGNIN_BEFORE_EDIT in index.php).


> B) I can also see a use for John's suggestion: allowing a sort of BOGO 
> login where one password (known to the group) will work with any 
> WikiWord user name, so that each group member's posts can be tied to 
> their user name.

Untested changes again:

Add to index.php somewhere:
  define('BOGO_PASSWORD', '<the universal password>');

Then change the last elseif clause in the above version of
WikiUser::_pwcheck() to:

          elseif (ALLOW_BOGO_LOGIN
                  && preg_match('/\A' . $WikiNameRegexp . '\z/', $userid))
{
              if (!empty($passwd) && $passwd == BOGO_PASSWD)
                  return WIKIAUTH_BOGO;
              return false;
          }

This makes it so bogo-logins are only accepted if accompanied
by the BOGO_PASSWORD.

Did that work?

[Phpwiki-talk] Simple security revisited

[<xi...@yi...>]

1) Re: the graphics, for those of you who expressed an interest: I will 
be tweaking the buttons and making them available soon. I agree with 
Jeff that it is a good idea to keep gifs in the default template. Old 
browsers are, unfortunately, still with us...

2) Thanks again to Jeff and John for the code to create one authorized 
user. I now have one wiki set up with one user and one admin, and 
another set up with the admin and BOGO login enabled. The next thing I 
am wondering is: A) can BOGO login be enabled in the case where there 
is one authorized user in addition to the admin (to create a sort of 
super-user whose ID cannot be spoofed by the BOGO users)?

John's instructions to create an authorized user:

* Open index.php
* Find: define('ADMIN_USER', "admin");
* Add two new lines under the ADMIN_PASSWD line:

  define('RESTRICTED_USER', "user");
  define('RESTRICTED_PASSWD', "test");

* Now open lib/WikiUser.php
* Scroll to the end and replace the whole of the _pwcheck function with 
this:

     function _pwcheck ($userid, $passwd) {
         global $WikiNameRegexp;
        
         if (!empty($userid) && $userid == ADMIN_USER) {
             if (!empty($passwd) && $passwd == ADMIN_PASSWD)
                 return WIKIAUTH_ADMIN;
             return false;
         }
         elseif (!empty($userid) && $userid == RESTRICTED_USER) {
             if (!empty($passwd) && $passwd == RESTRICTED_PASSWD)
                 return WIKIAUTH_USER;
         }
         return false;
     }

* Finally open lib/main.php
* Halfway down you'll find this:

             case 'edit':
                 if (defined('REQUIRE_SIGNIN_BEFORE_EDIT') && 
REQUIRE_SIGNIN_BEFORE_EDIT)
                     return WIKIAUTH_BOGO;
                 return WIKIAUTH_ANON;

Replace it with this:

             case 'edit':
                 return WIKIAUTH_USER;


I think that should do it.

John.
-- 

This seems to eliminate the BOGO option, and I was wondering if there 
is a way to keep it without messing up the admin and authuser functions.

B) I can also see a use for John's suggestion: allowing a sort of BOGO 
login where one password (known to the group) will work with any 
WikiWord user name, so that each group member's posts can be tied to 
their user name. I realize that this is getting closer to just having 
full authentication capability for all users, but it is a nice 
intermediate step for simple groups where there is a fair amount of 
trust and cooperation (and it would also make it possible for the 
password to be changed from time to time as needed -- something to 
consider if the membership of the group changes dramatically, or if 
members are leaving periodically and thus should "lose" posting ability 
upon departure).

Thanks, as always, for any help or advice on this. The more I work with 
this application, the more possibilities I see and the more I want to 
promote its use for groups of all types.
       

-----------------------------------------------------
http://eo.yifan.net
Free POP3/Web Email, File Manager, Calendar and Address Book

[Phpwiki-talk] new WikiAdminRemove plugin

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

There's a new administrative plugin to remove multiple pages.
http://phpwiki.sourceforge.net/demo/en/PhpWikiAdministration/Remove

In the CVS or tommorows nightly snapshot.
Note that this plugin must be in a subpage of "PhpWikiAdministration".
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

[Phpwiki-talk] Re: [phpwiki-checkins] CVS: phpwiki/themes/default/templates body.tmpl,1.27,1.28 debug.tmpl,1.4,1.5

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

On Tue, 20 Aug 2002 09:15:28 -0700
Reini Urban <ru...@us...> wrote:

> In directory usw-pr-cvs1:/tmp/cvs-serv24414/templates
> 
> Modified Files:
> 	body.tmpl debug.tmpl 
> Log Message:
> replaced gif with png versions


Hi Reini,

I just happened to look at this php-checkin message (I've pretty much
ignored them for the past several months).

I'm not sure what the current status is regarding gif vs png icons
in PhpWiki, but I think I would vote to keep the default theme,
at least, compatible with older non-png browsers.  That means
either we need the smarts to serve png or gif according to browser
capability, or just use gifs only.  (I vote for gifs only.)

I know (I think) there are PNGs in the fancier themes, and I think
that's okay, but I think we ought to put a fair amount of effort into
keeping the default theme as multi-browser compatible as possible.

OTOH, if the valid XHTML icon is broken, I guess it's no big deal.

Keep up the good work!

Re: [Phpwiki-talk] Email Notification question

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

> > A side note here: I do find it interesting that the Wiki isn't enough
> > even for the hardcore Wiki lovers on this mailing list -- if it was
> > enough, presumably the mailing list wouldn't be necessary, because
> > you'd all be checking the Wiki regularly.

>   Wiki is not designed as a groupware/messaging tool. It is designed to
> give many people the ability to edit a document simultaneously, not
> provide a forum for discussion.=20

Wiki is odd in that it wasn't particularly designed for /any/ of it's
uses.  On the other hand, it's simplicity of concept has made it better
than a lot of solutions "designed" for a specific purpose.

It has always been easy to say what Wiki is, though never with
certainty that what you're saying is complete.  It's always been quite
hard to say what it isn't.

>   Would you use CVS to carry out a discussion? Would you use
> Word/OpenOffice's "Track Changes" and "Merge Document" features to carry
> out a discussion?

Actually, CVS has turned into a discussion forum on the PLD Gnui/Linux
distro system more than once... quite effective, having the discussed
material so close at hand, and discussion as meta-data.

>   The correct answer to both of these questions is "no". If you want a
> discussion forum, use a tool that is designed for it (a web BBS, a mailing
> list, etc). If you want different people on different networks to be able
> to edit a document, use wiki.=20

I rather disagree -- wikis make fantastic discussion tools, though with
a few features added they are much more potent.

That said, I also agree that I'd prefer a mailing list for discussion
than a wiki -- I can answer email offline, and the queuing systems and
batching of messages is far more sophisticated than Wiki.  Both are
quite valid, but I quite prefer e-mail for discussion like this.

Ari

Re: [Phpwiki-talk] Email Notification question

[Evan H. <hu...@ne...>]

On Sun, 18 Aug 2002, Robert Orenstein wrote:
...
> A side note here: I do find it interesting that the Wiki isn't enough
> even for the hardcore Wiki lovers on this mailing list -- if it was
> enough, presumably the mailing list wouldn't be necessary, because
> you'd all be checking the Wiki regularly. When I started writing this
> message, I had a choice of posting it on the Wiki or sending out email --
> I chose email because it was the only way I had of guaranteeing that
> the people I wanted to see the message, WOULD see the message! I'd like
> to ask those of you who send email to this list: why do you send the
> email instead of posting to the Wiki? Is it for the reasons I've given
> above, or is there something else going on? It does seem to me that
> if EmailNotification were available, this mailing list could cease
> to exist.

  Wiki is not designed as a groupware/messaging tool. It is designed to
give many people the ability to edit a document simultaneously, not
provide a forum for discussion. 

  Would you use CVS to carry out a discussion? Would you use
Word/OpenOffice's "Track Changes" and "Merge Document" features to carry
out a discussion?

  The correct answer to both of these questions is "no". If you want a
discussion forum, use a tool that is designed for it (a web BBS, a mailing
list, etc). If you want different people on different networks to be able
to edit a document, use wiki. 

e

Re: [Phpwiki-talk] Email Notification question

[Evan H. <hu...@ne...>]

On Sun, 18 Aug 2002, Robert Orenstein wrote:
> Here's a short version of my longer question: is EmailNotification
> going to be implemented anytime soon? If not, I'll probably wind up
> trying to write the code myself for our site, but if someone else
> is working on it, and if it'll be available shortly, I'll probably
> hold off.

 I'm in the process of implementing a notification feature. I'm adding a
"subscribe" button to the bottom of each page (by the user login
box) that, when clicked, adds an entered email address to a notification
list for the page. 

 The notification list for the page is stored as part of the page's
meta-data. 


 There are a couple of problems with this approach:

  1. A user has to subscribe to page. There's no way of subscribing to
page creation/deletion or a general modification to a page. 
  2. If a user changes their email address, they must manually modify
every page they've subscribed to. 


  Eventually, once user profiles have been added, I'd like to store the
list of pages each user cares about in the profile (this will cause a
performance hit as every user is iterated over at save time, but that's
life). 

e

[Phpwiki-talk] TitleSearch problem fixed

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

I fixed the TitleSearch problem with USE_PATH_INFO false, as described 
in http://www.reflections.co.nz/wiki/IE-GetMethodBug.htm
It was a phpwiki problem, unrelated to any browser or server.
Should be in tommorrow's nightly tarball and in the current CVS soon.

I also updated the templates to use the constant "HOME_PAGE" instead of 
"HomePage", which violates common naming schemes.
Custom templates have to be updated accordingly.

   cd themes
   find . -name \*.tmpl -exec \
     perl -pi~ -e's/([^ ])HomePage/$1HOME_PAGE/g' \{\} \;

-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: [Phpwiki-talk] Email Notification question

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

John Kershaw schrieb:
> http://phpwiki.sourceforge.net/phpwiki/EmailNotificationHack
> Caveat: Reini does the serious stuff, I'm just a hacker, as in "hack n 
> slash"!

Caveat: Jeff does the serious stuff. I'm just another hacker with CVS 
access.

Re: [Phpwiki-talk] Email Notification question

[John K. <jo...@ke...>]

>admin-only there were some patches.

I added this EmailNotificationHack and use it for my ten wikis. It 
just mails me (and possibly one or two other admins) whenever a page 
is changed or deleted.

http://phpwiki.sourceforge.net/phpwiki/EmailNotificationHack

John.

Caveat: Reini does the serious stuff, I'm just a hacker, as in "hack n slash"!
-- 
------------------------------------
     0113 2289316 / 07944 755613
jo...@ke... / www.kershaw.org
  AOL johnkershaw / Y! john_m_kershaw
------------------------------------

Re: [Phpwiki-talk] ImageLinks revisited

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

Willie Dresler Leiva schrieb:
> On Sat, 17 Aug 2002, Reini Urban wrote:
>>BTW: I changed my local VisualWiki somewhat. The default cache_dir param 
>>on windows was broken. I'll send you a patch sooner or later.
>>I also improved the help page and simplified the valid image extensions.
>>
>>Something like this for the start:
>>
>>--- ./lib/plugincache-config.php~	2002-03-10 09:54:16.000000000 +0000
> 
> I didn't find this file on my PhpWiki installation. Is the filename correct?

It's a patch on http://phpwiki.sourceforge.net/phpwiki/VisualWiki
and in the nightly phpwiki snapshot.
   http://phpwiki.sf.net/nightly/phpwiki.nightly.tar.gz
In the alpha demo not yet (pear cache issues), but it's in the works.
   http://phpwiki.sourceforge.net/demo/en/VisualWiki

-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/