phpwiki-talk

[Phpwiki-talk] Announce: Installer patch

[electron <ele...@mg...>]

Keeping it short and sweet:

A postnuke inspired installer for phpWiki is here:

http://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D900056&group=
_id=3D612
1&atid=3D306121

The installer patches against the current CVS. Not ready for inclusion, =
but
it does work.

It should be mature in a few days.

-Jtp

Re: [Phpwiki-talk] Re: Fatal Error restoring from .zip file

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

Micki Kaufman schrieb:
> Using the latest dev code from CVS, checked out and installed well, but 
> it won't recognize a .zip file under 'Restoring'.
> 
> Using the same 'Upload File' method, I get a "'fatal PhpWiki Error' No 
> uploaded file to upload?" message.
> 
> Is this a known issue? Thanks so much, this build is looking GOOD!

No, thanks.
I'll fix it asap.

And I've found some other dumpfile problems:

* Dump to Directory: on WAMP (Windows) with the line-endings ending as 
\r\r\n. Which makes my XEmacs think it's a Mac textformat.

* Dump to XHTML:

AddingPages ... saved as AddingPages.html ... 7878 bytes written
...
Fatal error: Cannot redeclare class wikiplugin_backlinks in 
f:\prog\php\phpwiki-dev\phpwiki\lib\plugin\Backlinks.php on line 28

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

[Phpwiki-talk] Re: Phpwiki-talk digest, Vol 1 #911 - 7 msgs

[Micki K. <mic...@co...>]

Great, great - looking forward to checking it out!

Thanks for giving this some of your attention, Reini.

Micki


>Message: 3
>Date: Tue, 17 Feb 2004 13:03:15 +0100
>From: Reini Urban <ru...@x-...>
>To: php...@li...
>Subject: Re: [Phpwiki-talk] Re: Q: Can you condense multiple wiki pages into
>  one long nested page? (Martin Geisler)
>
>This is a multi-part message in MIME format.
>--------------050009070706080205020007
>Content-Type: text/plain; charset=us-ascii; format=flowed
>Content-Transfer-Encoding: 7bit
>
>Micki Kaufman schrieb:
>  > Reini also mentioned 'IncludeSiteMap'.
>  >
>  > The IncludeSiteMap plugin (which was a homegrown plugin for 1.3.4 that
>  > Cuthbert/DevNull Cat and I whipped up) allows you to use the same
>  > functionality as the 'SiteMap' plugin (a recursive, fwd/backward,
>  > indented 'BackLinks'), but to return each page's contents instead of the
>  > list of page names. Works great for my users, being able to generate
>  > 'Books' of pages for various CategoryWikiBadges, etc. Best of all, the
>  > 'transclusion-title' can be set to trigger a 'chapter' in a printed .pdf
>  > file, allowing you to have full joy between wiki and printable pdf
>  > structures like bookmarks and tables of contents.
>  >
>  > The plugin was crafted by Cuthbert Cat about a year ago, and I've sent
>  > Reini a copy for his analysis. To be honest, I've kept our install at
>  > 1.3.4 awaiting this plugin's consideration and would love to see this
>  > functionality added to the phpwiki code base.
>  >
>  > Also, Cuthbert - if you read the lists, can you give your 4 cents about
>  > IncludeSiteMap?
>
>I added IncludeSiteMap support to SiteMap on which its based on, to
>avoid code duplication. You can see it, when you look at the CVS version
>of SiteMap. (attached)
>The current problem is very simple and is now solved as in
>InterWikiSearch or PluginManager.


-- 

Micki
mailto:mic...@co...

[Phpwiki-talk] Re: Fatal Error restoring from .zip file

[Micki K. <mic...@co...>]

Hi folks.

Using the latest dev code from CVS, checked out and installed well, 
but it won't recognize a .zip file under 'Restoring'.

Using the same 'Upload File' method, I get a "'fatal PhpWiki Error' 
No uploaded file to upload?" message.

Is this a known issue? Thanks so much, this build is looking GOOD!

Micki
-- 

Micki
mailto:mic...@co...

Re: [Phpwiki-talk] Working on Windows??

[Stan B. <sb...@po...>]

Which phpWiki you are using?  I'm using 1.3.4 successfully for several 
months, everyday under Win2000 with apache+mysql+php.  Have you setup 
the admin. username and pasword in the index.php file?

Stan

Patrick Ouellet wrote:

>
> I setuped everything Apache+PHP
> I know its working perfectly.. I also have a phpbb2 website
> working on this web server.
>
> So I configured phpwiki to use MySQL
> If I hit phpwiki/index.php I can see the front page.. but thats it...
>
> Nothing else work.. if I hit phpwiki/admin.php
> I get an error: Set the administrator account and password first.
>
> Which I haven't been able to do as of this writing...
>
> Did someone actually have been able to make this work under Windows?
> Is there trick I should know of?
>
> Thank to everyone for help ;-)
>

[Phpwiki-talk] Working on Windows??

[Patrick O. <pou...@mi...>]

I setuped everything Apache+PHP
I know its working perfectly.. I also have a phpbb2 website
working on this web server.

So I configured phpwiki to use MySQL
If I hit phpwiki/index.php I can see the front page.. but thats it...

Nothing else work.. if I hit phpwiki/admin.php
I get an error: Set the administrator account and password first.

Which I haven't been able to do as of this writing...

Did someone actually have been able to make this work under Windows?
Is there trick I should know of?

Thank to everyone for help ;-)

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Patrick Ouellet - pou...@mi...
Administrateur des serveurs reseaux
Informatique - Poste 130
Microtec Technologies inc.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
"First they ignore you. Then they laugh at you.
Then they fight you. Then you win."
-Mahatma Gandhi
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Re: [Phpwiki-talk] Re: Q: Can you condense multiple wiki pages into one long nested page? (Martin Geisler)

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

Micki Kaufman schrieb:
> Reini also mentioned 'IncludeSiteMap'.
> 
> The IncludeSiteMap plugin (which was a homegrown plugin for 1.3.4 that 
> Cuthbert/DevNull Cat and I whipped up) allows you to use the same 
> functionality as the 'SiteMap' plugin (a recursive, fwd/backward, 
> indented 'BackLinks'), but to return each page's contents instead of the 
> list of page names. Works great for my users, being able to generate 
> 'Books' of pages for various CategoryWikiBadges, etc. Best of all, the 
> 'transclusion-title' can be set to trigger a 'chapter' in a printed .pdf 
> file, allowing you to have full joy between wiki and printable pdf 
> structures like bookmarks and tables of contents.
> 
> The plugin was crafted by Cuthbert Cat about a year ago, and I've sent 
> Reini a copy for his analysis. To be honest, I've kept our install at 
> 1.3.4 awaiting this plugin's consideration and would love to see this 
> functionality added to the phpwiki code base.
> 
> Also, Cuthbert - if you read the lists, can you give your 4 cents about 
> IncludeSiteMap?

I added IncludeSiteMap support to SiteMap on which its based on, to 
avoid code duplication. You can see it, when you look at the CVS version 
of SiteMap. (attached)
The current problem is very simple and is now solved as in 
InterWikiSearch or PluginManager.

Warning! The default usage of IncludeSiteMap would recursively include 
the WHOLE content of all your PhpWiki pages in one big page.
That may result in a MEGA html output. Just to make that clear.

Personally I don't buy that idea.
Maybe we should avoid the recursive nature (which is in fact IncludePage 
with multiple pages) or at least limit the recursion depth (reclimit) to 
1 or 2.

Well, I defined now the following default arguments to IncludeSiteMap:
   'includepages'   => 'words=50'
   'reclimit'       => 2,
The 'includepages' argument will be passed verbatim to IncludePage.
Direct usage of 'includepages' within SiteMap is forbidden, only from 
the child class IncludeSiteMap.

BTW: jeff, I had to fix almost all plugins, because a new basepage 
argument for ->run() was not defined and silently dropped.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

RE: [Phpwiki-talk] Q: Can you condense multiple wiki pages into one long nested page?

[Frank S. <fra...@rn...>]

> >>> "ru...@x-..." 02/15/04 21:59 >>>
> 
> Bob Apthorpe schrieb:
> > Forwarded from one of my users; is there an easy way to coallesce
> > multiple pages into a single page for easy viewing? I 
> vaguely recall a
> > plugin that might do this but I don't recall it off the top 
> of my head.
> 
> UnfoldSubpages does this and there's a IncludeSiteMap plugin 
> somewhere.
> (not yet in CVS)

As others have mentioned, the IncludePage plugin allows nice coalescing.

Take a look at http://roke.angband.za.org/frank/RealtimeTransportProtocol
for how I usually do this sort've stuff.

frank

[Phpwiki-talk] Re: Q: Can you condense multiple wiki pages into one long nested page? (Martin Geisler)

[Micki K. <mic...@co...>]

Reini and Martin are right - the UnfoldSubpages works great for pages 
you intentionally create as subpages. The IncludePage allows you to 
decide which pages you want, and have them all included in the 'main' 
wiki page, one plugin declaration per wiki page you include.

Reini also mentioned 'IncludeSiteMap'.

The IncludeSiteMap plugin (which was a homegrown plugin for 1.3.4 
that Cuthbert/DevNull Cat and I whipped up) allows you to use the 
same functionality as the 'SiteMap' plugin (a recursive, 
fwd/backward, indented 'BackLinks'), but to return each page's 
contents instead of the list of page names. Works great for my users, 
being able to generate 'Books' of pages for various 
CategoryWikiBadges, etc. Best of all, the 'transclusion-title' can be 
set to trigger a 'chapter' in a printed .pdf file, allowing you to 
have full joy between wiki and printable pdf structures like 
bookmarks and tables of contents.

The plugin was crafted by Cuthbert Cat about a year ago, and I've 
sent Reini a copy for his analysis. To be honest, I've kept our 
install at 1.3.4 awaiting this plugin's consideration and would love 
to see this functionality added to the phpwiki code base.

Also, Cuthbert - if you read the lists, can you give your 4 cents 
about IncludeSiteMap?

Thanks,
Micki

At 8:43 PM -0800 2/16/04, php...@li... wrote:
>Send Phpwiki-talk mailing list submissions to
>	php...@li...
>
>To subscribe or unsubscribe via the World Wide Web, visit
>	https://lists.sourceforge.net/lists/listinfo/phpwiki-talk
>or, via email, send a message with subject or body 'help' to
>	php...@li...
>
>You can reach the person managing the list at
>	php...@li...
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of Phpwiki-talk digest..."
>
>
>Today's Topics:
>
>    1. Re: Q: Can you condense multiple wiki pages into one long nested
>        page? (Martin Geisler)
>    2. mysql 4.1.0 bug alert (Reini Urban)
>
>--__--__--
>
>Message: 1
>To: php...@li...
>From: Martin Geisler <gim...@gi...>
>Date: Mon, 16 Feb 2004 12:13:09 +0100
>Subject: [Phpwiki-talk] Re: Q: Can you condense multiple wiki pages 
>into one long nested
>  page?
>
>Bob Apthorpe <apt...@cy...> writes:
>
>>  Hi,
>>
>>  Forwarded from one of my users; is there an easy way to coallesce
>>  multiple pages into a single page for easy viewing? I vaguely recall
>>  a plugin that might do this but I don't recall it off the top of my
>>  head.
>
>Yes, the IncludePage plugin does this for a single page, the
>UnfoldSubpages plugin can do it for all subpages for a particular
>page.
>
>--
>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.
>
>
>--__--__--
>
>Message: 2
>Date: Mon, 16 Feb 2004 13:56:23 +0100
>From: Reini Urban <ru...@x-...>
>To: php...@li...
>Subject: [Phpwiki-talk] mysql 4.1.0 bug alert
>
>Mysql 4.1.0-alpha has a problem with binary textfields.
>Confirmed at http://bugs.mysql.com/bug.php?id=1491
>
>Symptom & Reproduce:
>Every search will fail if the searchstring is not case-exact.
>e.g. Search for "find": "FindPage" will not be found.
>
>Workarounds:
>1.) Change the field attribute for pagename in table page
>      not to be "binary"
>    ALTER TABLE `page` CHANGE `pagename` `pagename` VARCHAR( 100 ) NOT NULL;
>
>2.) or install 4.1.1 (currently only from source), 5.x
>      or downgrade to 3.23.x or 4.0.
>      I downgraded to 4.0.18 and this worked ok.
>
>Besides one PhpWiki flaw which prevents the navbar FindPage to find the
>page "FindPage" with the string "find". Well, it finds it but after the
>redirect to FindPage it doesn't fill the searchstring into the plugin
>forms. Looks correct, but looks bad.
>--
>Reini Urban
>http://xarch.tu-graz.ac.at/home/rurban/
>
>
>
>
>--__--__--
>
>_______________________________________________
>Phpwiki-talk mailing list
>Php...@li...
>https://lists.sourceforge.net/lists/listinfo/phpwiki-talk
>
>
>End of Phpwiki-talk Digest


-- 

Micki
mailto:mic...@co...

[Phpwiki-talk] mysql 4.1.0 bug alert

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

Mysql 4.1.0-alpha has a problem with binary textfields.
Confirmed at http://bugs.mysql.com/bug.php?id=1491

Symptom & Reproduce:
Every search will fail if the searchstring is not case-exact.
e.g. Search for "find": "FindPage" will not be found.

Workarounds:
1.) Change the field attribute for pagename in table page
     not to be "binary"
   ALTER TABLE `page` CHANGE `pagename` `pagename` VARCHAR( 100 ) NOT NULL;

2.) or install 4.1.1 (currently only from source), 5.x
     or downgrade to 3.23.x or 4.0.
     I downgraded to 4.0.18 and this worked ok.

Besides one PhpWiki flaw which prevents the navbar FindPage to find the 
page "FindPage" with the string "find". Well, it finds it but after the 
redirect to FindPage it doesn't fill the searchstring into the plugin 
forms. Looks correct, but looks bad.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

[Phpwiki-talk] Re: Q: Can you condense multiple wiki pages into one long nested page?

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

Bob Apthorpe <apt...@cy...> writes:

> Hi,
>
> Forwarded from one of my users; is there an easy way to coallesce
> multiple pages into a single page for easy viewing? I vaguely recall
> a plugin that might do this but I don't recall it off the top of my
> head.

Yes, the IncludePage plugin does this for a single page, the
UnfoldSubpages plugin can do it for all subpages for a particular
page.

-- 
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] Re: htmlarea support (mozilla also!)

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

Oliver Betz schrieb:
> Reini Urban wrote:
>>>And if the client's browser doesn't support it? My preferred browser 
>>>is Opera at the moment because of the fast user interface.
>>
>>Opera is also supported, I forgot to write.
> 
> http://www.interactivetools.com/products/htmlarea/ states that the 
> beta version supports IE 5.5+ and Mozilla 1.3+. And in fact, it 
> didn't work with Opera 7.11 (didn't try 7.23) and IE5.0

newer operas should do it, as stated in the docs.

>>htmlarea has no requirements.
>>On an older browser it just uses the normal textarea field.
> 
> but with HTML markup, I guess? Otherwise phpwiki had to check for 
> htmlarea support and select what to present?

no, htmlarea already checks for supported browsers and if none is found 
just the wikiMarkup in the textarea is used.

with htmelarea-enabled I add the original wikimarkup in a hidden div tag 
after the textarea, so that htmlarea can switch betwween wysiwyg, raw 
html and wiki mode.

> I still don't need it, although I admit that it's cool. If I would 
> like to have functionality like this, I would set up a CMS, no wiki.

Initially I liked the UI and wanted to rewite htmlarea to support 
wikiformatting.
I can still do it with the tools inside htmlarea,
but then the wikiformat couldn't be rendered. no wysiwyg.
but still the most promising option for me.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: [Phpwiki-talk] Greetings: pnPhpWiki

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

electron schrieb:
> Reini Urban schrieb:
>>haven't I fixed this adodb limit bug recently in CVS?
>>anyway I added it, since it makes sense.
> 
> I didn't add it since it makes no sense. my adodb fix from last months 
> fixed the limit problem.
--
I fixed it in WikiDB/backend/ADODB.php:600
Id: ADODB.php,v 1.13 2004/02/12 14:11:35 rurban Exp

> I still get it inside pnPhpWiki. I'm on Version 1.12 of adodb.php. Error
> still pops up using either ADODB backend or pnADODB backend (custom backend
> that uses postnuke calls to adodb)

bad, bad, since I cannot reproduce it now. Jeff wanted the RecentChanges 
feature to not enable a limit per default. cannot you fix it elsewhere? 
in the adodb backend?

> I made an alpha release at http://noc.postnuke.com/projects/pnphpwiki/ which
> will reproduce the behavior if the patch isn't used.

ok, I'l try this.

> Divergent path:
> In playing with pnPhpWiki, PageHistory caused some intresting behavior with
> the way it uses urls.
> 
> Proposal: in stdlib, a useForm() or WikiForm() function be created that acts
> as a wrapper to HTML::<form>? I suggest this because of the need that all
> pages when phpwiki is run as a module need additional arguments (op,
> modload, etc) and when HTML::form is called in PageHistory, those postnuke
> required args should be hidden input elements, but are not.

a wrapper just for every form is hard. cannot you add a helper call to 
every POST form?

> The dirty solution is to hack PageHistory.php, the clean one is to
> encapsulate.
> 
> Also: in stdlib, a getDefaultArg() function that is called by WikiUrl() and
> proposed WikiForm()
> In standard phpwiki, this would return nothing, hackers like myself can dump
> my postnuke vars in there and have it work sitewide.

looks okay to me, since I need zend studio start_debug=1 also in all GET 
calls and for POST forms as hidden inputs.
but I think I already added such a url helper to stdlib. just cannot 
find it yet.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

RE: [Phpwiki-talk] 1.4 release?

[electron <ele...@mg...>]

Subject: Re: [Phpwiki-talk] 1.4 release?

Malcolm Ross Kinsella Ryan schrieb:
> I believe the deadline for releasing 1.4 was pushed back from =
Christmas
> to sometime in January (phpWiki's anniversary perhaps)? It's now =
halfway
> through Feb. Any word on when 1.4 might be released? Could this date=20
> be clearly recorded somewhere - like on the website - so we all know =
what
> we're expecting/aiming for? (And is there any online archive of this=20
> mailing list?)
>=20
> I'm bugging you about this as I think it is easy for Open Source =
proects
> to lose track of deadlines and the needs of "ordinary users". I love
phpWiki
> (I run one based on a much earlier release) but I really don't want to
have=20
> to deal with installing a developmental release. Can you _please_ =
settle=20
> on a stable release soon, and then focus on bug-fixes, rather than =
shiny=20
> new chrome?
>=20
> I wouldn't bother bothering you like this if I didn't believe that =
phpWiki
> has the potential to be a very useful product - if it ever gets out of =

> development.

----

Try and remember that most Open source stuff is also hobby based. What =
do
you need done?

-Jtp


----



I talked with Steve about this two weeks ago.


1.3.8 will be out very soon, as soon as some remaining bugs with
the new prefs and auth is fixed. Hopefully this week. ldap and file auth =

is not tested so far.

1.4.0 will have PagePermissions enabled for page listings also.
They are already enabled for normal operations. And they do work fine=20
for me, but are not fully tested yet.
The new admin plugins to administrate the new features must work also.

maybe for 1.4.0: I'm also working on a action=3Dupgrade feature to load=20
changed or new pgsrc pages for example. This will make upgrades e.g.=20
from 1.3.4 much easier.

----

Tack on Installation functions. I'll whip up something ala postnuke,
possibly an upgrade script too.=20

-Jtp

Re: [Phpwiki-talk] 1.4 release?

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

Malcolm Ross Kinsella Ryan schrieb:
> I believe the deadline for releasing 1.4 was pushed back from Christmas
> to sometime in January (phpWiki's anniversary perhaps)? It's now halfway
> through Feb. Any word on when 1.4 might be released? Could this date 
> be clearly recorded somewhere - like on the website - so we all know what
> we're expecting/aiming for? (And is there any online archive of this 
> mailing list?)
> 
> I'm bugging you about this as I think it is easy for Open Source proects
> to lose track of deadlines and the needs of "ordinary users". I love phpWiki
> (I run one based on a much earlier release) but I really don't want to have 
> to deal with installing a developmental release. Can you _please_ settle 
> on a stable release soon, and then focus on bug-fixes, rather than shiny 
> new chrome?
> 
> I wouldn't bother bothering you like this if I didn't believe that phpWiki
> has the potential to be a very useful product - if it ever gets out of 
> development.

I talked with Steve about this two weeks ago.

1.3.8 will be out very soon, as soon as some remaining bugs with
the new prefs and auth is fixed. Hopefully this week. ldap and file auth 
is not tested so far.

1.4.0 will have PagePermissions enabled for page listings also.
They are already enabled for normal operations. And they do work fine 
for me, but are not fully tested yet.
The new admin plugins to administrate the new features must work also.

maybe for 1.4.0: I'm also working on a action=upgrade feature to load 
changed or new pgsrc pages for example. This will make upgrades e.g. 
from 1.3.4 much easier.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

RE: [Phpwiki-talk] Newsgroup Message-ID links?

[electron <ele...@mg...>]

Hello All,

would it it be suitable/nice to pass Message-IDs to Google groups (as=20
a new link type)?

If so, it should be configurable - at the moment, Google accepts=20
requests like this:

http://groups.google.com/groups?selm=3D<Message-ID>

but who knows how long this service will be available...

Oliver
--=20
Oliver Betz, Muenchen


----

Using an API, we can defeat the "How long this service will be =
available" It
isn't going away, but the features might change. Enter an API.

Google has a beta API function:

http://groups.google.com/apis/

It only searches the web index, however. It should be watched, since
eventually the wiki could include news messages via SOAP via google.

State of API for Groups:

http://groups.google.com/apis/api_faq.html#ini2

(cry)

Peeking on google groups @ groups.google (twister!) it seems someone at =
MS
wants it, so we can hope, mm?

Thread:
http://groups.google.com/groups?dq=3D&hl=3Den&lr=3Dlang_en&ie=3DUTF-8&thr=
eadm=3D8b27cb
28.0401230936.69a98aab%40posting.google.com&prev=3D/groups%3Fdq%3D%26num%=
3D25%
26hl%3Den%26lr%3Dlang_en%26ie%3DUTF-8%26group%3Dgoogle.public.web-apis%26=
sta
rt%3D25

-Jtp

RE: [Phpwiki-talk] Greetings: pnPhpWiki

[electron <ele...@mg...>]

Reini Urban schrieb:
> haven't I fixed this adodb limit bug recently in CVS?
> anyway I added it, since it makes sense.

I didn't add it since it makes no sense. my adodb fix from last months=20
fixed the limit problem.


----

I still get it inside pnPhpWiki. I'm on Version 1.12 of adodb.php. Error
still pops up using either ADODB backend or pnADODB backend (custom =
backend
that uses postnuke calls to adodb)

I made an alpha release at http://noc.postnuke.com/projects/pnphpwiki/ =
which
will reproduce the behavior if the patch isn't used.

On a separate note: All you postnuke folks can d/l an alpha version of
pnPhpWiki @ the above url.

Divergent path:

In playing with pnPhpWiki, PageHistory caused some intresting behavior =
with
the way it uses urls.

Proposal: in stdlib, a useForm() or WikiForm() function be created that =
acts
as a wrapper to HTML::<form>? I suggest this because of the need that =
all
pages when phpwiki is run as a module need additional arguments (op,
modload, etc) and when HTML::form is called in PageHistory, those =
postnuke
required args should be hidden input elements, but are not.

The dirty solution is to hack PageHistory.php, the clean one is to
encapsulate.

Also: in stdlib, a getDefaultArg() function that is called by WikiUrl() =
and
proposed WikiForm()

In standard phpwiki, this would return nothing, hackers like myself can =
dump
my postnuke vars in there and have it work sitewide.

Thoughts?

-Jtp

[Phpwiki-talk] 1.4 release?

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

Dear phpwiki-developers,

I believe the deadline for releasing 1.4 was pushed back from Christmas
to sometime in January (phpWiki's anniversary perhaps)? It's now halfway
through Feb. Any word on when 1.4 might be released? Could this date 
be clearly recorded somewhere - like on the website - so we all know what
we're expecting/aiming for? (And is there any online archive of this 
mailing list?)

I'm bugging you about this as I think it is easy for Open Source proects
to lose track of deadlines and the needs of "ordinary users". I love phpWiki
(I run one based on a much earlier release) but I really don't want to have 
to deal with installing a developmental release. Can you _please_ settle 
on a stable release soon, and then focus on bug-fixes, rather than shiny 
new chrome?

I wouldn't bother bothering you like this if I didn't believe that phpWiki
has the potential to be a very useful product - if it ever gets out of 
development.

Malcolm

-- 
Malcolm Ryan - mal...@cs... - http://www.cse.unsw.edu.au/~malcolmr/

                         "Blessed are those who mourn,
                          for they will be comforted."          -- Matt 5:4

Re: [Phpwiki-talk] Re: htmlarea support (mozilla also!)

[Oliver B. <ob...@de...>]

Reini Urban wrote:

> > And if the client's browser doesn't support it? My preferred browser 
> > is Opera at the moment because of the fast user interface.
> 
> Opera is also supported, I forgot to write.

http://www.interactivetools.com/products/htmlarea/ states that the 
beta version supports IE 5.5+ and Mozilla 1.3+. And in fact, it 
didn't work with Opera 7.11 (didn't try 7.23) and IE5.0

[...]

> htmlarea has no requirements.
> On an older browser it just uses the normal textarea field.

but with HTML markup, I guess? Otherwise phpwiki had to check for 
htmlarea support and select what to present?

I still don't need it, although I admit that it's cool. If I would 
like to have functionality like this, I would set up a CMS, no wiki.

Oliver
-- 
Oliver Betz, Muenchen

[Phpwiki-talk] Newsgroup Message-ID links?

[Oliver B. <ob...@de...>]

Hello All,

would it it be suitable/nice to pass Message-IDs to Google groups (as 
a new link type)?

If so, it should be configurable - at the moment, Google accepts 
requests like this:

http://groups.google.com/groups?selm=<Message-ID>

but who knows how long this service will be available...

Oliver
-- 
Oliver Betz, Muenchen

Re: [Phpwiki-talk] Some problem with BackLinks

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

Alfredo Amontagna schrieb:
> BackLinks doesn't work for pages inside the OldStyleTable plugin.
> Please, try to go at http://www.linuxfan.it/mytest/TestMe .
> The first link into the table is FooBar .
> Try to open it and afterwards use the BackLinks button.
> You can see that is found only the instance in HomePage :-(
> Let me know if you can solve.

Ah, I see. This plugin args don't get parsed for wiki links.

That's now really something for Jeff, but let me see
what I can do with this.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: [Phpwiki-talk] Greetings: pnPhpWiki

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

Reini Urban schrieb:
> haven't I fixed this adodb limit bug recently in CVS?
> anyway I added it, since it makes sense.

I didn't add it since it makes no sense. my adodb fix from last months 
fixed the limit problem.

Re: [Phpwiki-talk] Greetings: pnPhpWiki

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

electron schrieb:
> My name is Jason. I run phpWiki as a postnuke module @ http://www.gs4.org.
> 
> I am in the process of updating lakka's PN module to 1.3.8pre.  Devel:
> http://www.gs4.org/dev . I'll eventually add it to noc.postnuke.com if they
> get their Gforge software in order. Maybe this can be a subproject of
> PhpWiki?

Fine, I tried this yesterday, but didn't finish it. (phpnuke-7.0, 
postnuke is much better, but i wanted to start with the worst)
I did the guiki-phpnuke module instead. much easier and looks better.

Note that with &frame=body argument hack you can display just the body 
(or any other template) and not the head, or better fix the head.tmpl.

> 1.) diff.php and diff3.php do not use the template system. This causes me to
> have to make some dirty hacks to those files. I may fix it as soon as I move
> pnPhpWiki to a post-alpha stage.

thanks.

> 2.) WikiUserNew.php gives me a real headache. Can this be better documented
> about who/what/when stuff gets called. For now I hacked WikiUser.php to use
> postnuke permissions. It works, but I figure WikiUserNew is the future?

Hmm, what's the problem? It doesn't do any output.
The real problem are the template and WikiLink and WikiUrl fixes.

For strict db auth against the nuke db set USER_AUTH_POLICY to "first-only"
and the $USER_AUTH_ORDER array to "Db" only.

> Squish:
> 1.) Added a patch to SourceForge to add a default limit for adodb and
> recentchanges. If limit isn't set it was just returning one item which is
> hardly useful.

haven't I fixed this adodb limit bug recently in CVS?
anyway I added it, since it makes sense.

> I'll lurk on SourceForge forums for a while and watch this list as well. I'm
> a big fan of adodb (what postnuke uses as well) and I'll see what we can do
> to migrate phpWiki off FETCH_ASSOC. Another note: The SourceForge
> pages/forums/etc. need cleaning, do you need a volunteer?

Agreed, FETCH_ASSOC is really annoying for the auth_sql staements.
I'd prefer MYSQL_NUM. Or do you need FETCH_BOTH?
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: [Phpwiki-talk] Q: Can you condense multiple wiki pages into one long nested page?

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

Bob Apthorpe schrieb:
> Forwarded from one of my users; is there an easy way to coallesce
> multiple pages into a single page for easy viewing? I vaguely recall a
> plugin that might do this but I don't recall it off the top of my head.

UnfoldSubpages does this and there's a IncludeSiteMap plugin somewhere.
(not yet in CVS)
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: [Phpwiki-talk] Re: htmlarea support (mozilla also!)

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

Oliver Betz schrieb:
> And if the client's browser doesn't support it? My preferred browser 
> is Opera at the moment because of the fast user interface.

Opera is also supported, I forgot to write.

>>On page type = wiki one can choose "Edit" or "Wysiwyg Edit".
>>This will bloat all pages, we will loose the wiki format once edited in 
>>the Wysiwyg editor, but the editor is really cool. I mean REALLY cool!
> 
> There are CMS with cool editors. But I don't want to use it - I like 
> the simple approach of Wiki, and to be able to access it with mimimum 
> requirements.

htmlarea has no requirements.
On an older browser it just uses the normal textarea field.

> So I wonder whether it's really _suitable_ to add a wysiwyg editor?

Htmlarea would be of course optional.
The question is if it should be selectable by the admin or by the user.
Or not enabled at all.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/