phpwiki-talk

RE: [Phpwiki-talk] Situation update - Setup Diagnostics

[Giovanni M. <Gio...@re...>]

Hi All

> Carsten Klapp wrote:
> 
> > Which one is Joby Walker's config scheme, is that the one with 
> > config-dist.php, config-user.php etc.? I like that system 
> too... (the configurator & old index.php are so huge now and 
> getting tough to maintain.)

Relating to PHPWiki configuration, I'd like to put in a plea for some
setup diagnostics. These would be relatively straightforward to
implement but save days of time if you make errors.

I'm thinking of a "Debug-directories" variable which will print out all
File system and URL paths. I had MAJOR difficulty setting up PHPWiki
1.3.3 on an IIS server (a prior Apache setup was trivial) because I was
confused about whether the directory names should be D:\\home\\xxxx or
D:/home/xxxx and where the paths are partial, whether or not there
should be trailing slashes ... and what the USE_PATH_INFO variable did
or was used for.

Eventually it turned to be that the "USE_PATH_INFO" wouldn't work (on
our IIS setup), setting this to false and it all worked, but it took
days to narrow it down ...

All of this sounds trivial **IF** you know/understand the setup
documentation. I'd set up all the directories (I thought) correctly and
yet it couldn't find the files - but I could see them in the directory I
THOUGHT I'd specified. Obviously it was either looking somewhere else or
the permissions were wrong but finding out which was extremely
difficult.

PHPWiki is now so complex that it's seriously non-trivial to figure out
what's going on.

So how about a switch that:

 1) print out all final paths defined in the Config files
    - especially important if a path has been assembled out 
    of several partial parts

 2) Write test file to each directory that should be writable. 
    This is to validate that the permissions are OK.

Point 2 was a killer recently - I was starting to write an Image
uploader for PHP (yes I know some exist) and the file upload just hung.
It turned out that the PHP upload temp directory wasn't writable but
phpinfo() looked fine, nothing complained, it just hung. As I was
unfamiliar with handling file uploads, it took a while to figure out it
wasn't my scripting/html.

The point of all this is that the simplest of errors can be quite
difficult to diagnose if you're working with incomplete
information/understanding. Some Diagnostics up front can be VERY
helpful.

phpInfo() is invaluable when getting PHP going, how about a "status
dump" for PHPWiki?

What do you think?
Giovanni

Re: [Phpwiki-talk] Long-term ideas

[<la...@us...>]

I just found a link that I was looking for -  see http://www.usemod.com/cgi-
bin/mb.pl?WikiXmlDtd

Quoting Matti Airas <ma...@ik...>:

> Has there been any discussion whether PhpWiki should be converted to use
> 
> internally an XML-based page format and to render the pages on-screen 
> using XSL transforms? That would be great in the sense that after that 
> it would be awfully easy to interface PhpWiki with other tools 
> (outputting pages in Docbook/LaTeX/WAP/XHTML basic/whatever, parsing the
> 
> pages easily with external tools etc.). I suppose it would also make 
> things such as optional Java applet -based wysiwyg editors easier to 
> implement.
> 
> Apache::AxKit wiki, while very simplistic, has taken this approach. Of 
> course, the drawback would be increased reliance on complex external 
> libraries, and it would probably require a more or less complete rewrite
> 
> of PhpWiki.
> 
> Do you think I'm just blinded by fancy acronyms, or would it make sense?
> 
> m.
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:
> With Great Power, Comes Great Responsibility 
> Learn to use your power at OSDN's High Performance Computing Channel
> http://hpc.devchannel.org/
> _______________________________________________
> Phpwiki-talk mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwiki-talk
> 

Re: [Phpwiki-talk] Long-term ideas

[<la...@us...>]

Openwiki (http://www.openwiki.com/) generates pages in XML and uses XSLT for 
display purposes.

I think there is something to be said for storing pages in a semi-rendered 
format, which could be XML.  That way, a lot of the parsing work is done when 
the page is stored, not when it is retrieved, which would result in faster 
rendering times.


Quoting Matti Airas <ma...@ik...>:

> Has there been any discussion whether PhpWiki should be converted to use
> 
> internally an XML-based page format and to render the pages on-screen 
> using XSL transforms? That would be great in the sense that after that 
> it would be awfully easy to interface PhpWiki with other tools 
> (outputting pages in Docbook/LaTeX/WAP/XHTML basic/whatever, parsing the
> 
> pages easily with external tools etc.). I suppose it would also make 
> things such as optional Java applet -based wysiwyg editors easier to 
> implement.
> 
> Apache::AxKit wiki, while very simplistic, has taken this approach. Of 
> course, the drawback would be increased reliance on complex external 
> libraries, and it would probably require a more or less complete rewrite
> 
> of PhpWiki.
> 
> Do you think I'm just blinded by fancy acronyms, or would it make sense?
> 
> m.
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:
> With Great Power, Comes Great Responsibility 
> Learn to use your power at OSDN's High Performance Computing Channel
> http://hpc.devchannel.org/
> _______________________________________________
> Phpwiki-talk mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwiki-talk
> 

Re: [Phpwiki-talk] Long-term ideas

[Matti A. <ma...@ik...>]

Reini Urban wrote:

> easier. we use internally the wiki-format, during the output step we use 
> jeff's XmlElement library which is able to dump as valid XML or HTML.
> 
> e.g. you can save as HTML or XML and convert to other formats externally.

Hmm... Is there an XML output format already defined (and implemented)? 
If so, it indeed might be simple enough to access those pages via 
XML-RPC and make a proxy for the portable output formats (I might be 
interested in implementing a WAP or XHTML basic interface so that 
PhpWiki sites could be accessed via new mobile phones)...

m.

Re: [Phpwiki-talk] Long-term ideas

[Tony L. <la...@is...>]

On Mon, 16 Dec 2002, Reini Urban wrote:

> easier. we use internally the wiki-format, during the output step we use 
> jeff's XmlElement library which is able to dump as valid XML or HTML.

I hope you put WikiBlog among the long-term ideas. 
Or, if it has already been established, just clearer 
documentation would be sufficient. 

I have been here: 
http://phpwiki.sourceforge.net/demo/en/WikiBlog
and added lib/plugin/Wikiblog and that bit of code in /lib/WikiDB.php .
But I couldn't figure out what else is needed to get that effect. 
Other SubPages code, perhaps? 

Thanks!


-- 
Tony Laszlo
http://www.issho.org/laszlo.html

Re: [Phpwiki-talk] Long-term ideas

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

Matti Airas schrieb:
> Has there been any discussion whether PhpWiki should be converted to use 
> internally an XML-based page format and to render the pages on-screen 
> using XSL transforms? That would be great in the sense that after that 
> it would be awfully easy to interface PhpWiki with other tools 
> (outputting pages in Docbook/LaTeX/WAP/XHTML basic/whatever, parsing the 
> pages easily with external tools etc.). I suppose it would also make 
> things such as optional Java applet -based wysiwyg editors easier to 
> implement.

easier. we use internally the wiki-format, during the output step we use 
jeff's XmlElement library which is able to dump as valid XML or HTML.

e.g. you can save as HTML or XML and convert to other formats externally.


BTW: I recently rewrote jeff's HtmlElement library in a simple and 
reusable manner. just functions, no classes, in a syntax similar to 
perl's CGI (not HTML::Element)

http://xarch.tu-graz.ac.at/home/rurban/software/html-lib.phps
http://xarch.tu-graz.ac.at/home/rurban/software/html-lib.php.gz

for example:
   echo html_tr(html_td(array(colspan=>$colspan),NBSP));
   echo html_tr(array(valign=>"top"),
			 html_td(array(align => "right"),
  html_img(array(src=>"img/icon_ampel_rot.gif",alt => "Fehler", width => 
"20", height => "20")), NBSP, NBSP),
			 html_td(array(colspan => $colspan-1), html_div(array('class' => 
$arr['type']),$msg)));

[Phpwiki-talk] Long-term ideas

[Matti A. <ma...@ik...>]

Has there been any discussion whether PhpWiki should be converted to use 
internally an XML-based page format and to render the pages on-screen 
using XSL transforms? That would be great in the sense that after that 
it would be awfully easy to interface PhpWiki with other tools 
(outputting pages in Docbook/LaTeX/WAP/XHTML basic/whatever, parsing the 
pages easily with external tools etc.). I suppose it would also make 
things such as optional Java applet -based wysiwyg editors easier to 
implement.

Apache::AxKit wiki, while very simplistic, has taken this approach. Of 
course, the drawback would be increased reliance on complex external 
libraries, and it would probably require a more or less complete rewrite 
of PhpWiki.

Do you think I'm just blinded by fancy acronyms, or would it make sense?

m.

Re: [Phpwiki-talk] Situation update

[Matti A. <ma...@ik...>]

Carsten Klapp wrote:

> Which one is Joby Walker's config scheme, is that the one with 
> config-dist.php, config-user.php etc.? I like that system too... (the 
> configurator & old index.php are so huge now and getting tough to 
> maintain.)

Yes, that's the one. However, I have to take my words back slightly. 
IMHO the current implementation is not quite there yet. I found out 
there is *more* work in using the split configuration files at the 
moment. To know what to edit, one has to read config-dist.php, and copy 
the relevant parts from that file to config-user.php (and also be able 
to do basic PHP editing, such as to remove "if (!defined(...)) pieces). 
Furthermore, there are plenty of associative arrays used in the 
configuration files, and it may not be obvious to everyone how to 
override settings from within them.

Maybe all user-editable configuration parameters should be simple 
variables, and the comments should reside in config-user.php. After 
requiring both of these config-files, there could be a 
lib/config-parser.php, which would then parse the set configuration for 
correctness and mangle it to structures more suitable for internal use. 
Or something...

m.

Re: [Phpwiki-talk] Situation update

[Matti A. <ma...@ik...>]

la...@us... wrote:

> The only change I would be tempted to make before release is a cosmetic one - 
> change the "Use new markup" checkbox to "Use old markup" checkbox, and clear it 
> by default.  I don't have the access here to be able to do that though, so if 
> others agree, please could someone check it in?

I can do that today or tomorrow. I'm anyway about to make a patch to put 
the back the old text formatting rules and enable my DHTML thingy in the 
edit screen (if that's still ok), so I can do that as well. Not that big 
change anyway. ;-)

Cheers,

m.

Re: [Phpwiki-talk] Situation update

[Carsten K. <car...@us...>]

I'll agree with Lawrence's suggestions to use "Use old markup" and 
upgrade the main PhpWiki site.

Which one is Joby Walker's config scheme, is that the one with 
config-dist.php, config-user.php etc.? I like that system too... (the 
configurator & old index.php are so huge now and getting tough to 
maintain.)

ck

On Monday, December 16, 2002, at 06:54  am, 
<la...@us...> wrote:

> Fine with me.  I am afraid that the bits I have been working on will 
> not be
> finished for a while, as I have spent the last couple of weeks in bed
> with 'flu, so don't wait for anything from me.
>
> The only change I would be tempted to make before release is a 
> cosmetic one -
> change the "Use new markup" checkbox to "Use old markup" checkbox, and 
> clear it
> by default.  I don't have the access here to be able to do that 
> though, so if
> others agree, please could someone check it in?
>
> I agree with Jeff that we should release more often.
>
> I am a bit confused now as to the purpose of the test wiki, the demo 
> wiki, the
> newmarkup wiki etc.  I think that the current cvs version (ie the 
> forthcomng
> release ;-)) is stable enough to be used on the SF site.
>
> Lawrence
>
-- 
Carsten Klapp
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GE d-@+ s+:- a C+++@(---) UB+++ P+>++ L+>++ E>++ W-(++) N-(+) o? K? 
!w----
O M+(++) V? PS+ PE-(--) Y+ PGP+>++ t+@ 5 X+@ R tv+(-) b+ DI++ D-
G e(+) h(---) r y z?
------END GEEK CODE BLOCK------

Re: [Phpwiki-talk] Situation update

[<la...@us...>]

Fine with me.  I am afraid that the bits I have been working on will not be 
finished for a while, as I have spent the last couple of weeks in bed 
with 'flu, so don't wait for anything from me.

The only change I would be tempted to make before release is a cosmetic one - 
change the "Use new markup" checkbox to "Use old markup" checkbox, and clear it 
by default.  I don't have the access here to be able to do that though, so if 
others agree, please could someone check it in?

I agree with Jeff that we should release more often.

I am a bit confused now as to the purpose of the test wiki, the demo wiki, the 
newmarkup wiki etc.  I think that the current cvs version (ie the forthcomng 
release ;-)) is stable enough to be used on the SF site.

Lawrence
Quoting Steve Wainstead <sw...@pa...>:

> On Sat, 14 Dec 2002, Matti Airas wrote:
> 
> > Are there any plans for the next PhpWiki release? It's been a while
> even
> > since the previous development branch release... How about fixing the
> > worst outstanding bugs, updating documentation and releasing a new
> > intermediate development release? And while at it, I'd love to see
> Joby
> > Walker's new config scheme to be officially adopted - it's so much
> > clearer than the one in use at the moment.
> >
> > I can participate in updating the documentation (and other stuff as
> > well, although they may not be that obvious to me).
> 
> I'm ready to do the work needed to do the actual release -- the press
> release, the tarball uploaded to SourceForge, posting to Freshmeat, all
> that stuff. I can download and test a fresh tarball from the nightly
> build
> and make sure the casual user should be able to install it with no
> problems, on dbm and MySQL at least.
> 
> This will be a few hour's work, but I can't do it until commits are in
> and
> people give me the nod. I'll start work on editing down the ChangeLog
> into
> a new feature list, and post it here.
> 
> Jeff said a long time ago that we should have frequent releases, and I
> think I have an idea on how to make that happen (less fanfare, just
> upload
> the tarball and that's that).
> 
> ~swain
> 
> 
> ---
>                   http://www.panix.com/~swain/
> "Without music to decorate it, time is just a bunch of boring
> production deadlines or dates by which bills must be paid."
>                      -- Frank Zappa
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:
> With Great Power, Comes Great Responsibility 
> Learn to use your power at OSDN's High Performance Computing Channel
> http://hpc.devchannel.org/
> _______________________________________________
> Phpwiki-talk mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwiki-talk
> 

RE: [Phpwiki-talk] Action page

[Ted V. <te...@jo...>]

Thanks Carsten!

I get the picture now. It works. Maybe one should refine the existing
documentation about this point.

Regards,
Ted

-----Oorspronkelijk bericht-----
Van: php...@li...
[mailto:php...@li...]Namens Carsten Klapp
Verzonden: zaterdag 14 december 2002 22:39
Aan: Ted Vinke
CC: php...@li...
Onderwerp: Re: [Phpwiki-talk] Action page


Hi Ted,

A page named "TerugLinks" must also exist, did you create one yet? Edit
"BackLinks" and copy the contents, translate it but make sure _not_ to
translate the plugin line: "<?plugin BackLinks...".

Carsten

On Saturday, December 14, 2002, at 02:33  pm, Ted Vinke wrote:

> Thanks for the response!
>
> However, when I perform the translations and do the "make" stuff as you
> described, everything gets translated allright, but the url e.g.
> BackLinks
> refers to (?action=BackLinks) gets also translated to
> ?action=TerugLinks (in
> Dutch).
>
> The result is the error: TerugLinks does not appear to be an 'action
> page'.
>
> Somehow the process doesn't seem to update these actions and doesn't
> understand that the translated TerugLinks should execute thr action
> (page)
> originally associated with the word 'BackLinks'.
>
> Any ideas?



-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
_______________________________________________
Phpwiki-talk mailing list
Php...@li...
https://lists.sourceforge.net/lists/listinfo/phpwiki-talk

Re: [Phpwiki-talk] Incorrect Date and Time Display on

[z2d2 <z2...@ea...>]

I located the source of the problem. The day and hours aren't
displaying because the themeinfo.php files still contain %e for
the day and %l for the hours. If you change the %e to %d and %l
(small L) to %I (capital i), then it works fine on IIS. Small L
isn't on the list of recognized specifiers. I'm surprised that
one works for anyone.

For your records, IIS recognizes all specifiers for the date
function. It does NOT recognize these for strftime: %C, %D, %e,
%g, %G, %h, %n, %r,%R, %t, %T, %u, and %V. Recommend a comment be
added to the documentation telling IIS users to avoid them. The
other ones work okay.

On a different subject, the graphics for phpwiki look very
professionally done. But...yes, I'm inserting a but here....some
(not all) have a gray border around them in IE 6. They look great
in NS 6, NS 4.7, and Opera 6 but IE doesn't render some of them
correctly. I'm bringing this up because IE is the predominantly
used browser today. About 90% of the people use it.  Whatever the
difference is now this browser doesn't like it.

Re: [Phpwiki-talk] Incorrect Date and Time Display on W2000 IIS

[z2d2 <z2...@ea...>]

Re: From: Reini Urban <ru...@x-...>
Subject: Re: [Phpwiki-talk] Incorrect Date and Time Display on
W2000 IIS

Can you explain why you think strftime is better??  They both
return the same results of formatting the date and time.  I'd
like to know what you see is the major difference in the two.

I can't find setenv in the manual to see what arguments it
takes. There's an apache_setenv listed but no explanation about
the arguments.  It probably only works on apache.  There's also a
putenv, which I've tried before, but couldn't get it to work
because my host has safe-mode enabled.

If you must use strftime, I'll play around with it some more and
see if I can figure out why exactly the day and hours aren't
displaying with it.  I think anyone with IIS 5 is running into
this same problem because it was previously reported here:
http://phpwiki.sourceforge.net/phpwiki/?KnownBugs   (scroll down
towards the bottom). He posted a workaround but I submitted what
I thought was a better fix.


Re: From: php...@cl...
Subject: [Phpwiki-talk] Deleting any page deletes homepage

I ran into the exact same bug.  Luckily, the software said
someone was editing my homepage (even though no one was) so it
wasn't deleted.  The page name is not being passed so it defaults
to the homepage. Inserting a hidden field like Oliver suggested
fixes it.


Re: From: Matti Airas <ma...@ik...>
Subject: [Phpwiki-talk] Situation update

"How about fixing the worst outstanding bugs, updating
documentation and releasing a new intermediate development
release?"

Yes, please do.  Anyone who has to run with a config of
USE_PATH_INFO=false hits into big bugs which doesn't give a very
good first impression of the software.  It takes a lot of time
hunting down whether each has been previously reported and fixed.
On some CVS files with fixes, you have to figure out which
version to download because new features have been added to later
ones which aren't defined in 1.3.3.

Don't get me wrong.  I think the software is nicely written, but
the major bugs are leaving newbies fumbling around.

[Phpwiki-talk] HIDE_TOOLBARS

[Sandy M. <mat...@bt...>]

In trying to customise PHPWiki I have come across HIDE_TOOLBARS in
browse.tmpl. The name indicates that this would hide the toolbars in
certain circumstances.
 
What are these circumstances and where is HIDE_TOOLBARS defined?
 
I am trying to customise the Hawiian template and can't find anything
here, nor can I find any reference in index.php.
 
I am running version 1.3.3
 
Thank you fro your help.

Re: [Phpwiki-talk] Action page

[Carsten K. <car...@us...>]

Hi Ted,

A page named "TerugLinks" must also exist, did you create one yet? Edit 
"BackLinks" and copy the contents, translate it but make sure _not_ to 
translate the plugin line: "<?plugin BackLinks...".

Carsten

On Saturday, December 14, 2002, at 02:33  pm, Ted Vinke wrote:

> Thanks for the response!
>
> However, when I perform the translations and do the "make" stuff as you
> described, everything gets translated allright, but the url e.g. 
> BackLinks
> refers to (?action=BackLinks) gets also translated to 
> ?action=TerugLinks (in
> Dutch).
>
> The result is the error: TerugLinks does not appear to be an 'action 
> page'.
>
> Somehow the process doesn't seem to update these actions and doesn't
> understand that the translated TerugLinks should execute thr action 
> (page)
> originally associated with the word 'BackLinks'.
>
> Any ideas?

Re: [Phpwiki-talk] Situation update

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

On Sat, 14 Dec 2002, Matti Airas wrote:

> Are there any plans for the next PhpWiki release? It's been a while even
> since the previous development branch release... How about fixing the
> worst outstanding bugs, updating documentation and releasing a new
> intermediate development release? And while at it, I'd love to see Joby
> Walker's new config scheme to be officially adopted - it's so much
> clearer than the one in use at the moment.
>
> I can participate in updating the documentation (and other stuff as
> well, although they may not be that obvious to me).

I'm ready to do the work needed to do the actual release -- the press
release, the tarball uploaded to SourceForge, posting to Freshmeat, all
that stuff. I can download and test a fresh tarball from the nightly build
and make sure the casual user should be able to install it with no
problems, on dbm and MySQL at least.

This will be a few hour's work, but I can't do it until commits are in and
people give me the nod. I'll start work on editing down the ChangeLog into
a new feature list, and post it here.

Jeff said a long time ago that we should have frequent releases, and I
think I have an idea on how to make that happen (less fanfare, just upload
the tarball and that's that).

~swain


---
                  http://www.panix.com/~swain/
"Without music to decorate it, time is just a bunch of boring
production deadlines or dates by which bills must be paid."
                     -- Frank Zappa

RE: [Phpwiki-talk] Action page

[Ted V. <te...@jo...>]

Thanks for the response!

However, when I perform the translations and do the "make" stuff as you
described, everything gets translated allright, but the url e.g. BackLinks
refers to (?action=BackLinks) gets also translated to ?action=TerugLinks (in
Dutch).

The result is the error: TerugLinks does not appear to be an 'action page'.

Somehow the process doesn't seem to update these actions and doesn't
understand that the translated TerugLinks should execute thr action (page)
originally associated with the word 'BackLinks'.

Any ideas?

-----Oorspronkelijk bericht-----
Van: Carsten Klapp [mailto:car...@us...]
Verzonden: vrijdag 13 december 2002 22:47
Aan: Ted Vinke
CC: php...@li...
Onderwerp: Re: [Phpwiki-talk] Action page


Hi Ted,

All the Dutch translations go into the file: wiki/locale/po/nl.po ,
PhpWiki and all the templates are written in english then gettext looks
up the translations in the .mo files.

First: edit wiki/locale/po/nl.po

Next: rebuild the mo files (requires gettext to be installed)

cd wiki/locale
make dep
make

And please feel welcome to share any translations you add or correct. ;)

Carsten

On Friday, December 13, 2002, at 09:59  am, Ted Vinke wrote:

> Hi,
>  
> after I have translated words like "LikePages" to Dutch ("NetZoals"),
> the url it's referring to also changes from
> ThuisPagina?action=LikePages to ThuisPagina?action=NetZoals which ends
> up in two PHP warnings at the bottom of the page:
>  
> lib/main.php:430: Notice[1024]: NetZoals: Does not appear to be an
> 'action page'
>
> lib/main.php:411: Notice[1024]: NetZoals: Unknown action
>
> However in the default distribution a few buttons already have been
> translated e.g. the "Edit" button has already been translated to
> "Verander", which works ok. The Edit button *is* in my native
> language, but still refers to the original ?action=edit url.
>
> Does anyone know where I can change these 'action pages' and/or get
> the translated buttons still refer to their original url or get the
> new translated urls to work as action pages?
>
> Regards,
> Ted
>

Re: [Phpwiki-talk] Deleting any page deletes homepage

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

php...@cl...m wrote:

> I just hit quite a serious bug in PhpWiki 1.3.3. When I attempted to
> delete a page that I created, the confirmation message asked whether
> to delete EventPhotos, I said yes and it deleted HomePage instead.

Look at the thread "Bug fix for removepage.php" starting 2002-10-10 
in the list archives:

http://sourceforge.net/mailarchive/forum.php?thread_id=1206940&forum_id=4517

maybe that's the reason.

Oliver

[Phpwiki-talk] Situation update

[Matti A. <ma...@ik...>]

Hi, folks.

I had to put PhpWiki a bit on the backburner for a while to make the 
last struggle to finish my Master's. Now that it's done (and I've had a 
few days of well-earned do-nothing relaxation), I'm ready to catch up on 
PhpWiki development.

Going through my mailing-list backlog I noticed that Martin Geisler had 
already included my new TextFormattingRules. That's great! However, I 
suspect there will be a big hassle if the old formatting rules are no 
longer anywhere to be found. Would it be OK to rename the old 
TextFormattingRules to (obviously!) OldTextFormattingRules and use the 
DHTML gimmick I made to provide the synopsis for either version? If so, 
I can make a patch for that.

Are there any plans for the next PhpWiki release? It's been a while even 
since the previous development branch release... How about fixing the 
worst outstanding bugs, updating documentation and releasing a new 
intermediate development release? And while at it, I'd love to see Joby 
Walker's new config scheme to be officially adopted - it's so much 
clearer than the one in use at the moment.

I can participate in updating the documentation (and other stuff as 
well, although they may not be that obvious to me).

Cheers,

mairas

[Phpwiki-talk] Deleting any page deletes homepage

[<php...@cl...>]

I just hit quite a serious bug in PhpWiki 1.3.3. When I attempted
to delete a page that I created, the confirmation message asked
whether to delete EventPhotos, I said yes and it deleted HomePage
instead. Then because HomePage was deleted the virgin wiki was
loaded from pgsrc so deleting my changes to the default Wiki
pages. For the pages other than HomePage the previous version could
be restored using PageHistory, however for HomePage the PageHistory
was lost so I had to restore from my browser cache.

I am using the db2 dba_handler.

There seems to be two bugs here:
1) Deleting any page causes the HomePage to be deleted. Clearly
 this should not happen.

2) If the HomePage is deleted (and perhaps if the HomePage is empty)
 then the virgin Wiki is loaded. I think it would be better to only
 load the virgin Wiki pages for thos pages which do not exist, so
 as to not replace any existing ones.

Does anyone know if these bugs have been fixed in a later version
or if there is a workaround.

Please let me know if there is any more information you require.

Thank you,
Steven Murdoch.

[Phpwiki-talk] Here we are .......

[CMax E. <in...@cm...>]

eu.CMAX.com       =20
          =20
                             =20
                             =20
                =20
                             =20
                             =20
                =20
          =20
          =20
                      =20
                      =20
                      =20
          =20
          =20
                      =20
                      =20
                      =20
                      =20
                      =20
                      =20
                =20
                 =20
                   =20
                      =20
          =20
          =20
                      =20
                      =20
          =20
          =20
                      =20
          =20
          =20
     =20

Re: [Phpwiki-talk] Incorrect Date and Time Display on W2000 IIS

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

z2d2 schrieb:
> Recommend changing from using php's strftime to the date function
> which I believe works fine cross platform.

We've already been there, strftime is better than date.
Will setenv LANG fix this strftime problem?

I know only of an %e problem under windows, I use entirely "%x %X", 
which do works fine on windows an linux.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

[Phpwiki-talk] Just tried phpwiki

[Giancarlo <gia...@na...>]

Hi
I just tried phpwiki, and really think it's cool.
There is some magic in the way a link is created and linked in one go.

Now I have some question.
I read that the regex should accept [AI] preceeding an uparcase letter 
in the WikiWord.  I tried to add AIOE (as needed in italian), with no 
success. I think the regex is broken somehow because neither the 
original [AI] was caught.
And then there are two regexp, one in the index.php file, and the other 
is in the Splitwords function in stdlib. I suppose the first is for 
parsing WikiWords in te text, the second is for showing them. But then, 
shouldn't the [AI] stuff be present in the index.php regex too?

Condidered that in italian E means 'and', O means 'or', I is the 
masc.plural article, A means 'at', Not to have them in a WikiWord makes 
thing quite difficult.

The 'Di' 'De' stuff was easy to eliminate, though..

Thanks
Gian

Re: [Phpwiki-talk] Action page

[Carsten K. <car...@us...>]

Hi Ted,

All the Dutch translations go into the file: wiki/locale/po/nl.po ,=20
PhpWiki and all the templates are written in english then gettext looks=20=

up the translations in the .mo files.

First: edit wiki/locale/po/nl.po

Next: rebuild the mo files (requires gettext to be installed)

cd wiki/locale
make dep
make

And please feel welcome to share any translations you add or correct. ;)

Carsten

On Friday, December 13, 2002, at 09:59  am, Ted Vinke wrote:

> Hi,
> =A0
> after I have translated words like "LikePages" to Dutch ("NetZoals"),=20=

> the url it's referring to also changes from=20
> ThuisPagina?action=3DLikePages to ThuisPagina?action=3DNetZoals which =
ends=20
> up in two PHP warnings at the bottom of the page:
> =A0
> lib/main.php:430: Notice[1024]:=A0NetZoals: Does not appear to be an=20=

> 'action page'
>
> lib/main.php:411: Notice[1024]:=A0NetZoals: Unknown action
>
> However in the default distribution a few buttons already have been=20
> translated e.g. the "Edit" button has already been translated to=20
> "Verander", which works ok. The Edit button *is* in my native=20
> language, but still refers to the original ?action=3Dedit url.
>
> Does anyone know where I can change these 'action pages' and/or get=20
> the translated buttons still refer to their original url or get the=20
> new translated urls to work as action pages?
>
> Regards,
> Ted
>