phpwiki-talk

Re: [Phpwiki-talk] latest build

[Arno H. <aho...@in...>]

> I have found the problem. In the function _iftoken in stdlib.php the
> removal of line based directives is done with
> But the brackets around $lineno and $lineyes are wrong. It should be

Aha. Are you using PHP3? I'm using PHP4 and the PHP4 manual says to put the 
'$' inside the brackets. I guess this is why I cannot see the problem. 
Fortunately, PHP4 also accepts the '$' outside the brackets which seems to 
be the PHP3 way.

> I don't know why you didn't notice anything. The problem is only visible
> for directives that are "false" and are not within a block directive that
> is "false". Perhaps you only checked pages where there are no such
> directives.

The directives are inside the browse.html template. So the directives occur 
on every page. Especially the ###IF ADMIN### stuff.

I've commited your change - thanks for spotting the error.

/Arno

Re: [Phpwiki-talk] latest build

[Jan H. <hi...@wi...>]

On Wed, Dec 06, 2000 at 09:30:28PM +0100, Arno Hollosi wrote:
> On Wednesday 06 December 2000 20:09, Steve Wainstead wrote:
> > Oh yes, I saw that too last night and forgot to report it.
> > sw
> >
> > On Wed, 6 Dec 2000, Jan Hidders wrote:
> > > I tried the latest nightly build (December 6) and now I see in my pages
> > > things like ³#IF ADMIN³# and ³#IF LOCK³#. But perhaps this is a matter
> > > of work in progress?
> 
> I cannot verify this. I just downloaded the latest tarball and did a clean 
> install and cannot find any of this.

I have found the problem. In the function _iftoken in stdlib.php the
removal of line based directives is done with

  	    $page = ereg_replace("{$lineno}[^\n]*\n", '', $page);
and

	    $page = ereg_replace("{$lineyes}[^\n]*\n", '', $page);

But the brackets around $lineno and $lineyes are wrong. It should be

  	    $page = ereg_replace("${lineno}[^\n]*\n", '', $page);
and

	    $page = ereg_replace("${lineyes}[^\n]*\n", '', $page);

I don't know why you didn't notice anything. The problem is only visible for
directives that are "false" and are not within a block directive that is
"false". Perhaps you only checked pages where there are no such directives.

-- Jan Hidders

Re: [Phpwiki-talk] latest build

[Arno H. <aho...@in...>]

On Wednesday 06 December 2000 20:09, Steve Wainstead wrote:
> Oh yes, I saw that too last night and forgot to report it.
> sw
>
> On Wed, 6 Dec 2000, Jan Hidders wrote:
> > I tried the latest nightly build (December 6) and now I see in my pages
> > things like ³#IF ADMIN³# and ³#IF LOCK³#. But perhaps this is a matter
> > of work in progress?

I cannot verify this. I just downloaded the latest tarball and did a clean 
install and cannot find any of this.

It looks like you are using old template files.
Read /templates/README for the new format of ###IF### directives if you use 
a custom-modified template.

Otherwise I suggest using the new template files.

/Arno

Re: [Phpwiki-talk] latest build

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

Oh yes, I saw that too last night and forgot to report it.
sw

On Wed, 6 Dec 2000, Jan Hidders wrote:

> I tried the latest nightly build (December 6) and now I see in my pages
> things like ³#IF ADMIN³# and ³#IF LOCK³#. But perhaps this is a matter of
> work in progress?
> 
> -- Jan Hidders
> 
> 
> 
> _______________________________________________
> Phpwiki-talk mailing list
> Php...@li...
> http://lists.sourceforge.net/mailman/listinfo/phpwiki-talk
> 

...............................ooo0000ooo.................................
   Hear FM quality freeform radio through the Internet: http://wcsb.org/
                     home page: www.wcsb.org/~swain 

Re: [Phpwiki-talk] translation (was: wiki with https)

[Arno H. <aho...@in...>]

> On Fri, 1 Dec 2000, Olivier Kaloudoff wrote:
> > ps: I can give you a french translation
> > for wiki in a few days, if you want.

Go ahead and send it in :o)

/Arno

[Phpwiki-talk] latest build

[Jan H. <hi...@wi...>]

I tried the latest nightly build (December 6) and now I see in my pages
things like ³#IF ADMIN³# and ³#IF LOCK³#. But perhaps this is a matter of
work in progress?

-- Jan Hidders

Re: [Phpwiki-talk] some questions

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

On Wed, 6 Dec 2000, Jan Hidders wrote:

> > This bug has been fixed since stdlib.php v1.12 from November 16th.
> > Are you sure you tested the latest build?
> 
> Oops. I didn't. My apologies. The latest nightly build in the FTP
> directroy seems to be the one of Nov. 5. But I will probably be able to get
> it by CVS.

Fixed. I removed a tmp/ directory that the script was using. Nightly
builds are available again, and I put a new tarball up.

> link names?". :-) But seriously, no, I have no concrete example of a useful
> link name with brackets in it. But then again, I am also not really sure
> that no-one is ever going to need one. 

I have been reading "Extreme Programming Explained" and "Pragmatic
Programmer," and both urge you to avoid adding things you think might be
needed in the future... when there is a compelling reason to add it, we
will; this includes "pure hack value" as well, so if I'm stuck home for a
few days with a cold, it might get added ;-)

sw

................................ooo0000ooo.................................
   Hear FM quality freeform radio through the Internet: http://wcsb.org/
                     home page: www.wcsb.org/~swain 

Re: [Phpwiki-talk] some questions

[Jan H. <hi...@wi...>]

On Wed, Dec 06, 2000 at 12:18:23PM +0100, Arno Hollosi wrote:
> 
> > > During my efforts to get this done I noticed a minor bug in the
> > > function ExtractWikiPageLinks. If you have something in your text like
> > > "[[not a link]" then the page name "[not a link" is extracted as a link
> > > name and turns up, for example, in MySQL in the table wikilinks. My
> > > patch also fixes this.
> >
> > Confirmed on my Postgresql installation... nice catch!
> 
> This bug has been fixed since stdlib.php v1.12 from November 16th.
> Are you sure you tested the latest build?

Oops. I didn't. My apologies. The latest nightly build in the FTP
directroy seems to be the one of Nov. 5. But I will probably be able to get
it by CVS.

> > > 3. Are square brackets in page names allowed?
> 
> Currently: no.
> And yes, any attempt to use "]" inside links has unpredicted consequences.

Well, a single "]" is predictable; it always closes the link. And a single
"[" does also what you would expect. Its when you use "]]" or "[[" that things
become funny. But this is besides the point.
 
> > Well, can you give some reasons why it should be allowed?

Well, in a FAQ I would expect link names like "Why can't I have ']'s in my
link names?". :-) But seriously, no, I have no concrete example of a useful
link name with brackets in it. But then again, I am also not really sure
that no-one is ever going to need one. 

> Me wonders too. You know, for my petproject "Sensei's Library" I have 
> modified it the following way. Bracketlinks are possible, but they have a 
> restricted regexp. Basically it boils down to that [some page] is equal to 
> SomePage or [yet another page] == YetAnotherPage. I.e. it is only used for 
> readability purposes. Well, ok I filter out some chars as well so that
> e.g. [Sensei's Library] == SenseisLibrary.

But wouldn't then the title of the page show up as "Senseis Library"?

> > > solve this I would suggest that closing brackets should also be
> > > escaped, i.e., ']' should be written as ']]' if it is not meant as an
> > That's logically consistent... What do you think Arno?
> 
> [..]
> 
> I assume that allowing those brackets causes more trouble for casual 
> visitors seeing and trying to recreate links like "cool [awesome] page".

Hm. Maybe, but if you are going to recreate something, you can always easily
check how the original was done. In fact, if I hadn't seen the example of
[[link name] I probably would have tried [[link name]] first.

> A straight-forward failure to use "]" is easier to understand. And don't 
> tell me it can be found in the manual somewhere. People don't read manuals.

In the edit page it now says 'escape "[" with "[["'. You could simply change
that into escape '"[" and "]" with "[[" and "]]"'. I don't think that is
really hard to understand.

And the way that things are currently implemented (replacing escaped things
with tokens) the standard example of "[[link name]" would still work. The
only thing that would really change is that "bla ]] bla"" will be
transformed to "bla ] bla". But how often do you write something like that?

The only two difficulties that I see are that
1. during transformation you have to take into account that link names may
   contain tokens
2. when extracting links you have to take into acount that link names may
   contain escaped symbols such as [[ and ]]

-- Jan Hidders

Re: [Phpwiki-talk] some questions

[Jan H. <hi...@wi...>]

On Tue, Dec 05, 2000 at 11:39:43PM -0500, Steve Wainstead wrote:
> On Wed, 6 Dec 2000, Jan Hidders wrote:
> >
> > 2. Is [link name|PageName] considered not WikiWiki?
> 
> It is now :-) Arno added this in the last few weeks, and if you try a
> nightly build you'll see it works. I just tested it.

Wonderfull! Thank you Arno, thank you Arno, thank you Arno :-).

-- Jan Hidders

Re: [Phpwiki-talk] Re: wiki with https

[Arno H. <aho...@in...>]

> > 	however, we tried an https
> > installation here at ynternet.org, and
> > wiki keeps sending urls matching
> > http:// ...

Maybe I'm missing something obvious, but why don't you just set the 
$ScriptURL to something like "https://ynternet.org/wiki/" ?
(assuming latest tarball)

/Arno

Re: [Phpwiki-talk] some questions

[Arno H. <aho...@in...>]

> > During my efforts to get this done I noticed a minor bug in the
> > function ExtractWikiPageLinks. If you have something in your text like
> > "[[not a link]" then the page name "[not a link" is extracted as a link
> > name and turns up, for example, in MySQL in the table wikilinks. My
> > patch also fixes this.
>
> Confirmed on my Postgresql installation... nice catch!

This bug has been fixed since stdlib.php v1.12 from November 16th.
Are you sure you tested the latest build?
If you are using an existing database there still might be some of those 
links in there - they should go away after loading/saving the page.

While verifying this, I discovered that I didn't include another bugfix I 
have had in my local wiki for some time. I have committed it now.
From the log:

:: fixed another bug in ExtractWikiPageLinks(): wiki-unknown-named was not
:: recognized and named wiki links had the wrong linktext inserted into the
:: wikilinks table

> > 3. Are square brackets in page names allowed?

Currently: no.
And yes, any attempt to use "]" inside links has unpredicted consequences.

> Well, can you give some reasons why it should be allowed?

Me wonders too. You know, for my petproject "Sensei's Library" I have 
modified it the following way. Bracketlinks are possible, but they have a 
restricted regexp. Basically it boils down to that [some page] is equal to 
SomePage or [yet another page] == YetAnotherPage. I.e. it is only used for 
readability purposes. Well, ok I filter out some chars as well so that
e.g. [Sensei's Library] == SenseisLibrary. The only thing you can do
inside brackets that you can't replicate with BumpyText is single words 
like [Link].

> > solve this I would suggest that closing brackets should also be
> > escaped, i.e., ']' should be written as ']]' if it is not meant as an
> That's logically consistent... What do you think Arno?

Logical, yes, but I still don't like it. I'm not too keen to include it, 
but of course I won't stay in the way of progress either ;)

I assume that allowing those brackets causes more trouble for casual 
visitors seeing and trying to recreate links like "cool [awesome] page".
A straight-forward failure to use "]" is easier to understand. And don't 
tell me it can be found in the manual somewhere. People don't read manuals.

/Arno

Re: [Phpwiki-talk] some questions

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

On Wed, 6 Dec 2000, Jan Hidders wrote:

> There are some questions I would like to ask about phpwiki but not before I
> have said that I have used it a little now and really like it, especially

Glad you like it!

> 1. What is the relationship between phpwiki and pwiki?

I don't think I've ever installed Pwiki... is that the purely OOD PHP
wiki? Oh, that's John Jorgensen's. I have installed that.

There's no formal connection but he was an early tester of PhpWiki last
December... he also let me keep the name PhpWiki. He was going to use it
but never released anything under that name. We haven't shared much code.
I recall a discussion on regexps to match links, which was and still is a
tricky thing to do.

> The projects look very similar to me, although pwiki seems heavier on
> features (not neccessarily a good thing). Are there plans for cooperation in
> the future?

No, not at this time.

> 2. Is [link name|PageName] considered not WikiWiki?

It is now :-) Arno added this in the last few weeks, and if you try a
nightly build you'll see it works. I just tested it.


> During my efforts to get this done I noticed a minor bug in the function
> ExtractWikiPageLinks. If you have something in your text like "[[not a
> link]" then the page name "[not a link" is extracted as a link name and
> turns up, for example, in MySQL in the table wikilinks. My patch also fixes
> this.

Confirmed on my Postgresql installation... nice catch!

> 3. Are square brackets in page names allowed?
> 
> If you try things like "[link[3]]" or "[ [[link]" or "[ a[[a]]a ]" you will
> see some funny symbols appearing in the output. Maybe this has something to
> do with tokenization inside page names that is not taken into account?

The funny symbols are the $FieldSeparator tokens we use as placeholders...
something pathological is happening here.

> The way that things are implemented now, you can never have a closing
> bracket inside a page name. I think that is an unnecessary restriction. To

Well, can you give some reasons why it should be allowed? I now regret
allowing [link] notation. I think a more flexible BumpyText pattern would
have served us better. I would never go back at this point of course, but
this touches on the larger issue of Wiki useability. If all the links are
consistently BumpyCaseLinks, I think the Wiki gains a little in
consistency and usability. Others disagree, and since I'm a nice guy we
have and will keep [bracket links]. :-)

> solve this I would suggest that closing brackets should also be escaped,
> i.e., ']' should be written as ']]' if it is not meant as an end of a page
> name. As far as I can see this is not very hard to implement with
> regular expressions. You can, for instance, recognize bracketed links
> because they begin with an uneven number of '['s and end with an uneven
> number of ']'s.

That's logically consistent... What do you think Arno?

thx Jan!
sw

...............................ooo0000ooo.................................
   Hear FM quality freeform radio through the Internet: http://wcsb.org/
                     home page: www.wcsb.org/~swain 

[Phpwiki-talk] some questions

[Jan H. <hi...@wi...>]

Hello Steve and everybody,

There are some questions I would like to ask about phpwiki but not before I
have said that I have used it a little now and really like it, especially
its simplicity and accessability. I have plans of using it to set up some
kind of FAQ / dictionary for database theory or even something with a
broader scope like www.foldoc.org.

So here are my questions:

1. What is the relationship between phpwiki and pwiki?

The projects look very similar to me, although pwiki seems heavier on
features (not neccessarily a good thing). Are there plans for cooperation in
the future?

2. Is [link name|PageName] considered not WikiWiki?

It is my opinion that this would be a very logical and useful extension; it
solves some problems such as unnatural WikiWikiNames and plurals. I foudn a
"patch" by Antti Kaihola but that doesn't work for the latest version. So I
made a new one for the latest version of phpwiki. Is anyone interested in
that or am I just making it harder for myself to migrate to the next
version? :-)

During my efforts to get this done I noticed a minor bug in the function
ExtractWikiPageLinks. If you have something in your text like "[[not a
link]" then the page name "[not a link" is extracted as a link name and
turns up, for example, in MySQL in the table wikilinks. My patch also fixes
this.

3. Are square brackets in page names allowed?

If you try things like "[link[3]]" or "[ [[link]" or "[ a[[a]]a ]" you will
see some funny symbols appearing in the output. Maybe this has something to
do with tokenization inside page names that is not taken into account?

The way that things are implemented now, you can never have a closing
bracket inside a page name. I think that is an unnecessary restriction. To
solve this I would suggest that closing brackets should also be escaped,
i.e., ']' should be written as ']]' if it is not meant as an end of a page
name. As far as I can see this is not very hard to implement with
regular expressions. You can, for instance, recognize bracketed links
because they begin with an uneven number of '['s and end with an uneven
number of ']'s.

Anyway, these were my questions. I hope you will find some time to answer
them.

Kind regards,

-- Jan Hidders

Re: [Phpwiki-talk] Re: wiki with https

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

> > This should be a simple fix, but what's the simplest? We can add another
> > config variable to let the admin decide between 'http' and 'https', but
> > there should be a way to let the Wiki decide this itself. Suggestions?
> 
> any way to use relative urls instead of absolute ones ?

Yes, but I'll have to track back and forth over my changes (which now number in
the thousands!) from the stock distro to find out what I did; I -think- I'm
using only relative URLs-- if not, I'm dynamically generating correct ones
using the environment variables that PHP has available.

If anyone wants to log in and steal the source code to NBTSWikiWiki, just email
me and I'll set up an account-- the server's welcome to logins from afar, so
don't be bashful. I keep meaning to clean up the code enough to check into an alternate CVS branch, so it's available, but I haven't gotten there yet.

Oh, by the way, I'll be checking in a new flatfile driver that's much happier
than the old one-- searches work and all that.

My biggest problem lately in keeping up with PhpWiki-release version is that I
prefer non-templating code; since the translation functions take well over five
seconds on this server for a long page, I prefer to be sending data to the
client for that whole time. (It has always seemed a shame to me to have a nice
language like PHP where the scripting is nicely embedded try as hard as it can
to make HTML separate again. I guess I prefer to have it there, and then give a
human editor the instructions "That's PHP; Don't touch it until you learn about
it. It's cool, though, so learn it..."); anyway, in the NBTSWikiWiki release is
some pretty slick code to flush output every 16 lines (since there's
expressions that can be applied to more than one line at a time for speed)...
the whole parser is -finally- beginning to be clean again, so maybe at some
date in the future, I'll check in an alternate module for wiki_transform, using
the (much more readable!) NBTSWiki markup.

(My goal in writing the markup was to have the markup make total sense in text
as well, using already-familiar conventions such as "-bold in  here-" and
/italic text like this/, and, of course, astrices as bullets.)

Anyway, this email is getting plenty long, and it's time for a break from wiki
code, seeing as I spent yesterday adding features and smoothing the parser
instead of working, so today, I write scripts for someone else!

g'day,
	Aredridel

Re: [Phpwiki-talk] FrontPage change

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

On line 14 in lib/display.php, change "FrontPage" to whatever you wish
("HomePage" might be good :-)

sw

On Sat, 2 Dec 2000, Yann Forget wrote:

> Hi,
> 
> Howto change the FrontPage ?
> 
> I don't like the name. It remember me
> a certain software which I hate	;-)
> 
> Yann
> _______________________________________________
> Phpwiki-talk mailing list
> Php...@li...
> http://lists.sourceforge.net/mailman/listinfo/phpwiki-talk
> 

...............................ooo0000ooo.................................
   Hear FM quality freeform radio through the Internet: http://wcsb.org/
                     home page: www.wcsb.org/~swain 

Re: [Phpwiki-talk] Re: bug

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

OK, I figured it out. This sh script you want to display contains lines
like this:

#######################################################

PhpWiki tries to interpret that as a line in a numbered list argument,
i.e. it wants to render this as:

   1. <no text here though>

In fact it wants to render this as a numbered list 49 levels deep! This
exceeds a hardcoded limit in the little stack class we use to track how
many levels deep we are in nested lists like <UL>, <OL>, and <DT>.

On line 327 in lib/stdlib.php, the limit is hardcoded to 10:

               if ($stack->cnt() > 10) {

I just thought noone would ever want to nest lists that deep... and that
assumption still holds true, since you don't want a numeric list, you want
a comment line!

This isn't quite a "bug" per se, more of a design limitation. What
troubles me is that it seems obvious and intuitive to paste code samples
into a Wiki like you did, but you don't want to render it in HTML, you
want to render it in <pre></pre> tags. Indenting every line is a pain in
the butt.

I'll think about how to add this. In fact I know how (token substitution)
but I don't know if we ever implemented this... it would probably work the
same way we handle URLs. (I'm rambling at this point, so...)

The way to deal with this is to indent with spaces like I mentioned
before.

cheers!
sw


On Sat, 2 Dec 2000, Steve Wainstead wrote:

> 
> As a temporary fix, if you indent all the lines in the file with a space,
> it will save OK, and it will render as well (as plain text, which for
> source code is probably what you want.
> 
> sw
> 
> ...............................ooo0000ooo.................................
>    Hear FM quality freeform radio through the Internet: http://wcsb.org/
>                      home page: www.wcsb.org/~swain 
> 
> _______________________________________________
> Phpwiki-talk mailing list
> Php...@li...
> http://lists.sourceforge.net/mailman/listinfo/phpwiki-talk
> 

..............................ooo0000ooo.................................
   Hear FM quality freeform radio through the Internet: http://wcsb.org/
                     home page: www.wcsb.org/~swain 

Re: [Phpwiki-talk] Re: bug

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

As a temporary fix, if you indent all the lines in the file with a space,
it will save OK, and it will render as well (as plain text, which for
source code is probably what you want.

sw

...............................ooo0000ooo.................................
   Hear FM quality freeform radio through the Internet: http://wcsb.org/
                     home page: www.wcsb.org/~swain 

Re: [Phpwiki-talk] Re: bug

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

Thanks, I get the same error you do (Stack bounds exceeded in
SetHTMLOutputMode). Most puzzling. The page is saved though.

I'll try to fix this today.

sw


On Sat, 2 Dec 2000, Yann Forget wrote:

> Steve Wainstead a écrit :
> > 
> > Yes, if you could send the page source, that would tell us a lot...
> 
> Here it is :
> 
> #!/bin/sh
> 
> #######################################################
> # syncmail_gore_ynternet_sn.sh
> #
> # version 0.01 (merci d'augmenter ce numero de version
> #               lors de toute modification, puis de 
> #               m'informer de la modif)
> #
> # le 23/11/2000 
> #
> #  ka...@yn...
> #  ra...@r4...
> #
> ########################################################
> #
> # But: permettre l'echange de mail:
> #       - de Dakar vers le monde (dakar_to_world()) 
> #       - de Lausanne (MX) vers Dakar
> #
> # Moyens:
> #       - gore.ynternet.sn recoit une ip dynamique,
> #         gnudip (gdipc.pl) la fixe dans le nameserver
> #         principal du domaine ynternet.sn    
> #       - 
> #
> # le TTL pour la zone ynternet.sn est de 60 (sec)
> # je prevois donc une marge de 60 sec en plus
> # apres quoi on peut faire le etrn pour lancer
> # l'envoi du mail depuis Lausanne vers ici (gore.ynternet.sn)
> #
> #
> # BUGS: le TTL est code ici, alors qu'il devrait etre
> #       recupere automatiquement ... le jour ou nous
> #       changerons ce parametre, ca va planter.
> 
> logs_gnudip=/var/log/gnudip.log
> logs_etrn=/var/log/etrn.log
> 
> function attente_connexion {
>         echo "attente connexion (45 sec)"
>         sleep 45            # beark
> }
> 
> function attente_ttl {
>         echo "attente expiration TTL (60+20 sec)"
>         sleep 80            # mouarf
> }
> 
> function mail_sortant {
>         
>     echo "declanchement envoi du mail sortant"
>     killall -ALRM qmail-send    # flush mqueue
> }
> 
> function mail_entrant {   # ne fonctionne pas
> 
>         echo "declanchement reception du mail entrant (Lausanne)"
>         echo -n "$(date) " >> $logs_etrn
>         /usr/bin/expect -f /root/scripts/etrn.expect \
>                 >> $logs_etrn \
>                 2>> $logs_etrn
> }
> 
> function adresse_ip {
> 
>         echo -n "mise a jour adresse ip"
>         localip=$(/sbin/ifconfig  \
>             | grep ppp0 -A 1| tail -1 \
>             | tr ' ' '\n' | grep addr\
>             | cut -d: -f2)
>         echo "($localip)"    
> 
>         echo -n "$(date) " >> $logs_gnudip
>         /root/scripts/gdipc.pl \
>                 >> $logs_gnudip \
>                 2>> $logs_gnudip
> }
> 
> 
> function monitoring() {
> 
>     echo -e "\n \
>             \n\n$(/usr/bin/nslookup gore.ynternet.sn)\n \
>             ETRN\n\n$(tail -8 $logs_gnudip) \
>             \n\n$(tail -8 $logs_etrn)" \
>             $(/sbin/ifconfig)\
>             | /usr/sbin/sendmail ka...@ka...            
> }
> 
> attente_connexion
> adresse_ip
> attente_ttl
> mail_sortant
> mail_entrant
> monitoring
> 

...............................ooo0000ooo.................................
   Hear FM quality freeform radio through the Internet: http://wcsb.org/
                     home page: www.wcsb.org/~swain 

[Phpwiki-talk] FrontPage change

[Yann F. <yan...@yn...>]

Hi,

Howto change the FrontPage ?

I don't like the name. It remember me
a certain software which I hate	;-)

Yann

Re: [Phpwiki-talk] Re: bug

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

Yes, if you could send the page source, that would tell us a lot...

thx
sw

On Fri, 1 Dec 2000, Yann Forget wrote:

> We have a bug when tring to put some
> code in a page :
> 
> >WikiFatalError
> 
> >Stack bounds exceeded in SetHTMLOutputMode 
> 
> I can send the code if necessary.
> 
> Yann
> _______________________________________________
> Phpwiki-talk mailing list
> Php...@li...
> http://lists.sourceforge.net/mailman/listinfo/phpwiki-talk
> 

...............................ooo0000ooo.................................
   Hear FM quality freeform radio through the Internet: http://wcsb.org/
                     home page: www.wcsb.org/~swain 

[Phpwiki-talk] Re: bug

[Yann F. <yan...@yn...>]

We have a bug when tring to put some
code in a page :

>WikiFatalError

>Stack bounds exceeded in SetHTMLOutputMode 

I can send the code if necessary.

Yann

[Phpwiki-talk] Re: wiki with https

[Olivier K. <ka...@ka...>]

> This should be a simple fix, but what's the simplest? We can add another
> config variable to let the admin decide between 'http' and 'https', but
> there should be a way to let the Wiki decide this itself. Suggestions?

any way to use relative urls instead of absolute ones ?

> sw
> 
> On Fri, 1 Dec 2000, Olivier Kaloudoff wrote:
> 
> > Hi !
> > 
> > 	I am very happy with wiki,
> > thank you, this is really a great tool.
> > 
> > 	however, we tried an https
> > installation here at ynternet.org, and
> > wiki keeps sending urls matching
> > http:// ...
> > 
> > 	SSL would be great to share 
> > a private, password protected wiki.
> > 
> > 	Do you plan some improvements
> > going this way ?
> > 
> > Best Regards,
> > 
> > Olivier Kaloudoff
> > ka...@yn...
> > 
> > ps: I can give you a french translation
> > for wiki in a few days, if you want.
> > 
> 
> ...............................ooo0000ooo.................................
>    Hear FM quality freeform radio through the Internet: http://wcsb.org/
>                      home page: www.wcsb.org/~swain 
> 
> 

Re: [Phpwiki-talk] KernelWIki and 1.2

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

On Thu, 30 Nov 2000, Arno Hollosi wrote:

> 
> Hi there,
> 
> I just found out that KernelWiki uses PhpWiki :o)
> See http://kernelbook.sourceforge.net/wiki/

Yes, I think that went up a few months ago. I hope it takes off!

> 
> Btw, how about releasing 1.2 soon? I don't think there are many technical 
> changes to be done, so why not wrap it up quickly, so that we can steam 
> ahead with 1.3.x?

Agreed... most of the deadlines I set in the task manager were the end of
November, and it's... oops... December! :-)


> Main work: updating the documentation. And provide a migration document for 
> those using 1.1.x (or even 1.0.x).

Most of the docs are up to date... the DBLIB.txt is out of date though.
I'd like to update the README to list what implementations are missing
features; MySQL and Postgresql are all up to date, mSQL and DBM lag
behind, and flat file is still alpha.

sw


...............................ooo0000ooo.................................
   Hear FM quality freeform radio through the Internet: http://wcsb.org/
                     home page: www.wcsb.org/~swain 

[Phpwiki-talk] Re: wiki with https

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

This should be a simple fix, but what's the simplest? We can add another
config variable to let the admin decide between 'http' and 'https', but
there should be a way to let the Wiki decide this itself. Suggestions?

sw

On Fri, 1 Dec 2000, Olivier Kaloudoff wrote:

> Hi !
> 
> 	I am very happy with wiki,
> thank you, this is really a great tool.
> 
> 	however, we tried an https
> installation here at ynternet.org, and
> wiki keeps sending urls matching
> http:// ...
> 
> 	SSL would be great to share 
> a private, password protected wiki.
> 
> 	Do you plan some improvements
> going this way ?
> 
> Best Regards,
> 
> Olivier Kaloudoff
> ka...@yn...
> 
> ps: I can give you a french translation
> for wiki in a few days, if you want.
> 

...............................ooo0000ooo.................................
   Hear FM quality freeform radio through the Internet: http://wcsb.org/
                     home page: www.wcsb.org/~swain 

[Phpwiki-talk] KernelWIki and 1.2

[Arno H. <aho...@in...>]

Hi there,

I just found out that KernelWiki uses PhpWiki :o)
See http://kernelbook.sourceforge.net/wiki/

Btw, how about releasing 1.2 soon? I don't think there are many technical 
changes to be done, so why not wrap it up quickly, so that we can steam 
ahead with 1.3.x?

Main work: updating the documentation. And provide a migration document for 
those using 1.1.x (or even 1.0.x).

/Arno