phpwiki-talk

Re: [Phpwiki-talk] page too big

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

click on EditText

Didier Bretin schrieb:
>   I'm with the 1.2.0 version. Apparently now my page RecentChanges is too big and I got
> the error:
> How can I do to empty this page ?
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

[Phpwiki-talk] page too big

[Didier B. <db...@in...>]

Hello,

  I'm with the 1.2.0 version. Apparently now my page RecentChanges is too big and I got
the error:

Warning: PostgreSQL query failed: ERROR: Tuple is too big: size 8152, max size 8140 in
/mnt/commun/local/phpwiki-1.2.0/lib/pgsql.php on line 145
Insert/update failed: ERROR: Tuple is too big: size 8152, max size 8140

How can I do to empty this page ?

Thanks.

Regards.
-- 
            .------------------------------------------------.
    .^.     | Didier Bretin, France | db...@in...    |
    /V\     |-----------------------| www.informactis.com    |
   // \\    |                       `------------------------|
  /(   )\   | Visit: http://www.fnh.org/                     |
   ^^-^^    `------------------------------------------------'

Re: [Phpwiki-talk] php-mode

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

Here it is! :-)

~swain

On Thu, 12 Apr 2001, Jon =C5slund wrote:

> On Wed, Apr 11, 2001 at 05:35:52PM -0400, Steve Wainstead wrote:
> >
> > If there are no objections I'd like to reformat the code to comply with
> > php-mode in Emacs.
>
> Where can I find this "php-mode"? :) Doesn't seem to be in FSF Emacs 20.7
>
> --
> ___\ Jon =C5slund
>
> _______________________________________________
> Phpwiki-talk mailing list
> Php...@li...
> http://lists.sourceforge.net/lists/listinfo/phpwiki-talk
>

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


;;; php-mode.el -- major mode for editing PHP source files

;; Author: Fred Yankowski <fc...@ac...>
;; Keywords: PHP, PHP3, languages
;; $Id: php-mode.el,v 1.24 2000/12/08 17:44:17 fred Exp $

;; php-mode.el is Copyright (c) 1999,2000 by Fred Yankowski <fc...@ac...>
;;
;;=09This is free software; you can redistribute it and/or modify
;;=09it under the terms of the GNU General Public License as
;;=09published by the Free Software Foundation; either version 2,
;;=09or (at your option) any later version.
;;
;;=09This is distributed in the hope that it will be useful, but
;;=09WITHOUT ANY WARRANTY; without even the implied warranty of
;;=09MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
;;=09GNU General Public License for more details.
;;
;;=09You should have received a copy of the GNU General Public
;;=09License as the file COPYING.  If not, write to the Free
;;=09Software Foundation, Inc., 59 Temple Place - Suite 330,
;;=09Boston, MA 02111-1307, USA.

;;; Commentary;
;;
;; PHP mode is a major mode for editing the PHP programming language
;; <www.php.net>.  It is mostly concerned with setting up syntax
;; coloring via the font-lock library.
;;
;; To use PHP mode, add this to your ~/.emacs file:
;;
;;=09(autoload 'php-mode "php-mode" "PHP editing mode" t)
;;=09(add-to-list 'auto-mode-alist '("\\.php3\\'" . php-mode))
;;
;; Repeat the second line for any other filename suffixes that you
;; want to associate with PHP mode.  Then, install this file in some
;; directory in your Emacs load-path and run byte-compile-file on it.
;; Voila'.
;;
;; If php-mode does not colorize the text of your PHP code, you may need
;; to tweak the supporting font-lock mode a bit.  Here is more code for
;; .emacs that demonstrates one approach:
;;
;;=09(cond (window-system
;;       (require 'font-lock)
;;       (setq font-lock-support-mode 'lazy-lock-mode)
;;       (setq font-lock-maximum-decoration t)
;;       (global-font-lock-mode t)
;;       ))
;;
;; The above configuration treats the entire file as being PHP code,
;; causing interspersed HTML code to be handled very poorly.  An
;; option that provides very satisfying results is to use php-mode in
;; conjuction with the Multiple Major Modes package.  Get that package
;; from mmm-mode.sourceforge.net, install it, and use something like
;; the following in your .emacs file to configure it:
;;
;;=09(require 'mmm-mode)
;;=09(setq mmm-global-mode 'maybe)
;;=09(mmm-add-mode-ext-class nil "\\.php3?\\'" 'html-php)
;;=09(mmm-add-classes
;;=09 '((html-php
;;=09    :submode php-mode
;;=09    :front "<\\?\\(php\\)?"
;;=09    :back "\\?>"
;;=09    )))
;;=09(autoload 'php-mode "php-mode" "PHP editing mode" t)
;;=09(add-to-list 'auto-mode-alist '("\\.php3?\\'" . sgml-html-mode))
;;
;; Note that .php files now have the PSGML/HTML mode as their major
;; mode and PHP mode as a submode applied by the MMM minor mode.  You
;; can force a file to get PHP mode as a submode by starting the file
;; with a line like this:
;;
;;=09<?php // -*- mmm-classes: html-php -*-
;;
;; For files with HTML and PHP code that generates some of the
;; top-level elements of the HTML document, the following convinces
;; PSGML to treat the HTML content as if it were in the context of the
;; BODY element of an HTML document:
;;
;;=09<?php // -*- sgml-parent-document: ("dummy.html" "html" "body" ()) -*-
;;
;; This depends on having a dummy.html file that contains just the
;; DOCTYPE element for the desired HTML document type.  See the PSGML
;; info file for more help.
;;
;; The font-coloring applied by the PSGML/HTML mode may collide with
;; the coloring applied by PHP mode.  I got around this by removing
;; the list element for 'pi' in the sgml-markup-faces value.

;; Xemacs users report that regexp-opt is not defined.
(eval-when-compile
  (unless (fboundp 'regexp-opt)
    (defun regexp-opt (strings paren)
      (let ((open-paren (if paren "\\(" ""))
=09    (close-paren (if paren "\\)" "")))
=09(concat open-paren
=09=09(mapconcat 'regexp-quote strings "\\|")
=09=09close-paren)))))

(defconst xemacsp (string-match "Lucid\\|XEmacs" emacs-version) "\
Non nil if using XEmacs.")

(let* ((php-keywords
=09(eval-when-compile
=09  (regexp-opt
=09   '("and" "break" "case" "continue" "default" "do" "echo"
=09     "else" "elseif" "endfor" "endif" "endswitch" "endwhile" "exit"
=09     "extends" "for" "global" "if" "include"
=09     "or" "require" "return" "static" "switch" "then"
=09     "var" "while" "xor") t)))
       ;; "class", "new" and "extends" get special treatment below

       (php-constants
=09(eval-when-compile
=09  (regexp-opt
=09   '("false" "true"
=09     "E_ERROR" "E_NOTICE" "E_PARSE" "E_WARNING" "E_ALL"
=09     "PHP_OS" "PHP_VERSION"
=09     "__LINE__" "__FILE__") t)))

       (php-types
=09(eval-when-compile
=09  (regexp-opt '("array" "bool" "char" "double" "float" "int"
=09=09=09 "integer" "long" "mixed" "object" "real"
=09=09=09 "string" "void") t)))
       )

  (defconst php-font-lock-keywords-1
   (list
    '("^[ \t]*\\(class\\)[ \t]*\\(\\sw+\\)?"
      (1 font-lock-keyword-face) (2 font-lock-function-name-face nil t))

    '("^[ \t]*\\(function\\)[ \t]*\\(\\sw+\\)?"
      (1 font-lock-keyword-face) (2 font-lock-function-name-face nil t))
    ))

  (defconst php-font-lock-keywords-2
   (append php-font-lock-keywords-1
    (list
     (concat "\\<\\(" php-keywords "\\)\\>")

     `(,(concat "\\<\\(" php-constants "\\)\\>")
       1 font-lock-constant-face)

     ;; handle several words specially, to include following word,
     ;; thereby excluding it from unknown-symbol checks later
     '("\\<\\(new\\|extends\\)\\s-+\\$?\\(\\sw+\\)"
       (1 font-lock-keyword-face) (2 default))

     ;; treat 'print' as keyword only when not used like a function name
     '("\\<print\\s-*(" . default)
     '("\\<print\\>" . font-lock-keyword-face)

     '("<\\?\\(php\\)?" . font-lock-constant-face)
     '("\\?>" . font-lock-constant-face)
     )))

  (defconst php-font-lock-keywords-3
   (append
    (list
     ;; warn about 'new FooBar()' -- empty parens are tempting but wrong
     '("\\<\\(new\\)\\s-+\\(\\sw+\\)\\((\\s-*)\\)"
       (1 font-lock-keyword-face) (2 default) (3 font-lock-warning-face))
     )
    php-font-lock-keywords-2
    (list
     ;'("</?\\sw+[^>]*>" . font-lock-constant-face) ; <word> or </word>

     ;; warn about '$' immediately after ->
     '("\\$\\sw+->\\s-*\\(\\$\\)\\(\\sw+\\)"
       (1 font-lock-warning-face) (2 default))

     ;; warn about $word.word -- it could be a valid concatenation,
     ;; but without any spaces we'll assume $word->word was meant.
     '("\\$\\sw+\\(\\.\\)\\sw"
       1 font-lock-warning-face)

     ;; exclude casts from bare-word treatment
     `(,(concat "(\\(" php-types "\\))")
       1 default)

     ;; Warn about bare symbols, those that don't follow '$' or precede
     ;; '('.  But first explicitly mark some words that are OK.
     '("->\\s-*\\sw+" . default)=09; -->word
     '("\\$\\sw+" . default)=09=09; $word
     '("\\<\\sw+\\s-*[[(]" . default)=09; word( or word[
     '("\\<[0-9]+" . default)=09=09; number (also matches word)
     '("\\<\\sw+\\>" . font-lock-warning-face)

     ;; Warn about =3D=3D> instead of =3D> (why do I *do* that?)
     '("=3D=3D+>" . font-lock-warning-face)
     ))))

(defconst php-font-lock-syntactic-keywords
  (if xemacsp nil
    ;; Mark shell-style comments.  font-lock handles this in a
    ;; separate pass from normal syntactic scanning (somehow), so we
    ;; get a chance to mark these in addition to C and C++ style
    ;; comments.  This only works in GNU Emacs, not Xemacs 21 which
    ;; seems to ignore this same code if we try to use it.
    (list
     ;; Mark _all_ # chars as being comment-start.  That will be
     ;; ignored when inside a quoted string.
     '("\\(\#\\)"
       (1 (11 . nil)))
     ;; Mark all newlines ending a line with # as being comment-end.
     ;; This causes a problem, premature end-of-comment, when '#'
     ;; appears inside a multiline C-style comment.  Oh well.
     '("#.*\\([\n]\\)"
       (1 (12 . nil)))
     )))

(define-derived-mode php-mode c-mode "PHP"
  "A major mode for editing PHP source code.

Key bindings:
\\{php-mode-map}"

  (setq comment-start "// "
=09comment-end   ""
=09comment-start-skip "// *")

  (defvar php-mode-syntax-table php-mode-syntax-table)

  (modify-syntax-entry ?_ "w" php-mode-syntax-table)
  ;; underscore considered part of word
  (modify-syntax-entry ?$ "." php-mode-syntax-table)
  ;; dollar-sign considered punctuation, not part of word

  (if xemacsp (progn
=09=09(modify-syntax-entry ?# "< b" php-mode-syntax-table)
=09=09(modify-syntax-entry ?\n "> b" php-mode-syntax-table)))
  ;; The above causes Xemacs to handle shell-style comments correctly,
  ;; but fails to work in GNU Emacs which fails to interpret \n as the
  ;; end of the comment.

  (make-local-variable 'font-lock-defaults)
  (setq font-lock-defaults
=09'((php-font-lock-keywords-1
=09   php-font-lock-keywords-2
=09   ;; Comment-out the next line if the font-coloring is too
=09   ;; extreme/ugly for you.
=09   php-font-lock-keywords-3
=09   )
=09  nil=09=09=09=09; KEYWORDS-ONLY
=09  T=09=09=09=09; CASE-FOLD
=09  nil=09=09=09=09; SYNTAX-ALIST
=09  nil=09=09=09=09; SYNTAX-BEGIN
=09  (font-lock-syntactic-keywords . php-font-lock-syntactic-keywords)))

  (make-local-variable 'require-final-newline)
  (setq require-final-newline  nil)
  (make-local-variable 'next-line-add-newlines)
  (setq next-line-add-newlines nil)
  ;; Will not force newline at end of file.  Such newlines can cause
  ;; trouble if the PHP file is included in another file before calls
  ;; to header() or cookie().
)


(unless (boundp 'default)
  (defvar default 'default))
;; Created "default" symbol for GNU Emacs so that both Xemacs and GNU
;; emacs can refer to the default face by a variable named "default".

(unless (boundp 'font-lock-keyword-face)
  (copy-face 'bold 'font-lock-keyword-face))
;; font-lock-keyword-face is sure to be valid now, assuming that the
;; bold face exists

(unless (boundp 'font-lock-constant-face)
  (copy-face 'font-lock-keyword-face 'font-lock-constant-face))
;; font-lock-constant-face now exists, which Xemacs doesn't seem to have
;; by default

(provide 'php-mode)

Re: [Phpwiki-talk] php-mode

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

>Where can I find this "php-mode"? :) Doesn't seem to be in FSF Emacs 20.=
7

   http://www.ontosys.com/reports/PHP.html

Re: [Phpwiki-talk] php-mode

[Jon <d9...@na...>]

On Wed, Apr 11, 2001 at 05:35:52PM -0400, Steve Wainstead wrote:
>=20
> If there are no objections I'd like to reformat the code to comply with
> php-mode in Emacs.

Where can I find this "php-mode"? :) Doesn't seem to be in FSF Emacs 20.7

--=20
___\ Jon =C5slund

Re: [Phpwiki-talk] php-mode

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

>If there are no objections I'd like to reformat the code to comply with
>php-mode in Emacs.

I think it's a fine idea.

>The downside to this is all the whitespace will change, which means it
>will ruin diff output from CVS at that point.

I don't know whether it's possible or not, but if you can configure
CVS to pass the '-b' flag to diff, that will cause diff to ignore most
of these changes.  (-b means "Ignore changes in the amount of white space".)

You can do this on an individual level by adding a line 'diff -b' to
your .cvsrc.   It would be nice to get the SF web-based CVS browser to
do this too though.

[Phpwiki-talk] php-mode

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

If there are no objections I'd like to reformat the code to comply with
php-mode in Emacs.

The downside to this is all the whitespace will change, which means it
will ruin diff output from CVS at that point.

However that's why we have alpha branches of the software :-)

speak up or put up...
~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

[Phpwiki-talk] Re: wiki is great-thanks

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

Thanks for the kind note! It's always encouraging to hear someone finds
PhpWiki useful!

Your revised TextFormattingRules is quite excellent.

cheers
Steve

On Wed, 11 Apr 2001, Mi...@Bl... wrote:

>
> I have recently  been working on my website which was created with your
> wikiwiki product. I got very excited about the possibilities and in wanting
> to document my learning I took the liberty of adding to the
> TextFormattingRules page.
>
> http://ezines.blumenthals.com/index.php?TextFormattingRules
>
> Thanks for a great product.
>
> Mike
>
>
>
>
>
>

---
                  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] idle thoughts ...

[Adam S. <la...@sp...>]

> This has been suggested many times, but I don't see any interest from
> the project developers, nor myself. It's not that I think it's a bad
> idea, it's just not an itch I have to scratch :-)

honestly i'm not that interested in it either (i don't like phpnuke), i
just figured it would have been requested and was curious about thoughts
:)

> The problem I see though is: look at c2.com's Wiki. It's as simple as
> can be. There's something easy to understand when all of the page
> content can be edited by the user.

to a certain extent i agree, it took me a long time to wrap my head around
wiki's ... which is kinda of baffling in retrospect because they are *so*
simple.

> When the Wiki is just a smaller part of a larger system, it tends to be a
> small section of the page you can edit. Since so very few people know or
> understand the Wiki concept, it will probably suffer from lack of user
> participation. That's my opinion at least.

what i was thinking of was a little more structured, and not really a true
wiki.  probably only people with a certain amount of karma (basically a
time investment to discourage random destruction) would be able to be
editors.

> However all of this gave me several thoughts (which is what makes
> playing with hypertext systems so fun!), one of which is: why not make
> the weblog in reverse? Instead of users posting new entries to the
> weblog, let the weblog be generated by user edits to pages. The
> WorseIsBetter implementation of this would be a list of page diffs,
> but with a little thinking this can be made more informative.

it would require very careful page editing, or rules to determine what
appeared in the weblog or you'd get a really dull weblog (today adam fixed
the spelling of "maintainence" ... again! :-).

maybe if you made a very heirarchical wiki then you could have things
appear when you create a new node?  so your wiki might look like:

section politics:
  sub-section copywrite:
    sub-section napster vs. riaa
      story today XXX happened
        discussion ...
in that model everytime a new story page was created something would
appear in the weblog.  or if a section or a sub-section was edited
significatly (which has to be judged somehow) it would be reposted.

this way you have your persistant data store built in.  and then you have
another wiki which basically acts as a glossary and allows miscelaneous
bits of information to be filled in in more true wiki style.

what i'm struggling with is how to inforce the heirarchy.  do you do it
with some form of sub-wiki's or do you somehow backend a weblog with a
wiki?

> I've had similar thoughts for some time now...

i'm not much of a coder (i hack :) but i've got a server with cycles to
spare and a t1.  wanna help :)

> In particular I thought this implementation was interesting:
> http://pikie.darktech.org/cgi/pikie?DevelopmentWebLog

yep i'm watching it pretty closely, it's still *very* simple at the moment
but it's pretty cool.  once there's some way of having true discussion
assiciated (better then ThreadMode) with it we're getting closer.

adam.

ps. sorry this is really pretty off topic but i think it's interesting so
hopefully others will too.

Re: [Phpwiki-talk] idle thoughts ...

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

>> second thing i think would be easy, but one of the tacks i'm thinking
>> about is using standard weblog rdf features available in a wiki.  what
>> would it take to make an rdf version of (for example) the RecentChanges
>> page so that a weblog could include it as a slashbox?
>
>In the newer code base I suspect it won't be all that hard, since
>RecentChanges is now machine-generated and not user-editable. (If I read
>Jeff's CVS comments correctly).

(Just to inject a dose of reality:)
No.  It's not that fancy yet.   The only changes so far are:

1. The _initial_ RecentChanges page is automatically generated (upon load-up
of a virgin wiki), rather than being read from pgsrc.

2. We've made RecentChanges locked by default, so that malicious
users can't edit it to hide their tracks. 

It would be nice to make the page dynamically generated.  When/if
that happens, it would also be easy/nice to be able to generate
RecentChanges in other formats, like RDF.   My personal reasons
for this, is that I'd like to see a unified recent changes page
which merges the recent changes from several different wikis.

Jeff

Re: [Phpwiki-talk] idle thoughts ...

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

Hi Adam, thanks for the thoughtful post...

On Fri, 6 Apr 2001, Adam Shand wrote:

> one of the things i've been looking around for and thinking about is
> integrating a wiki into a weblog.  though there has been a reasonable
> amount of talk about this the closest i've seen is drupals book module
> (which is brand spanking new).
>
> http://www.drop.org/module.php?mod=book

Neat! I've looked at kuro5hin before but didn't realize the users rate all
articles and that's how they bubble up to the top. Drupal looks to me
mostly like a PHP implementation of the Scoop system.

> i'm curious about two things.
>
> has any thought been given to making phpwiki work as a php-nuke module (or
> better imho a drupal module?).  i honestly have no idea what would be
> involved in this.

This has been suggested many times, but I don't see any interest from the
project developers, nor myself. It's not that I think it's a bad idea,
it's just not an itch I have to scratch :-)

The problem I see though is: look at c2.com's Wiki. It's as simple as can
be. There's something easy to understand when all of the page content can
be edited by the user.

When the Wiki is just a smaller part of a larger system, it tends to be a
small section of the page you can edit. Since so very few people know or
understand the Wiki concept, it will probably suffer from lack of user
participation. That's my opinion at least.

>
> second thing i think would be easy, but one of the tacks i'm thinking
> about is using standard weblog rdf features available in a wiki.  what
> would it take to make an rdf version of (for example) the RecentChanges
> page so that a weblog could include it as a slashbox?

In the newer code base I suspect it won't be all that hard, since
RecentChanges is now machine-generated and not user-editable. (If I read
Jeff's CVS comments correctly).

However all of this gave me several thoughts (which is what makes playing
with hypertext systems so fun!), one of which is: why not make the weblog
in reverse? Instead of users posting new entries to the weblog, let the
weblog be generated by user edits to pages. The WorseIsBetter
implementation of this would be a list of page diffs, but with a little
thinking this can be made more informative.

> basically what i want to do (this is still a very unfinished idea so bear
> with me :-) is have a weblog front end but use a wiki as a back end data
> store.  the problem with weblogs is that once a story is a couple weeks
> old (sometimes just a couple days old) it's pretty much dead.  wouldn't it
> be cool if information could be moved from a weblog (where discussion
> happens better then on a wiki) into a wiki where the thoughts can be
> maintained and refined over time.

I've had similar thoughts for some time now...


> if you're curious rusty of k5 put up some interesting thoughts on meatball
> wiki a while ago:
>
> http://www.usemod.com/cgi-bin/mb.pl?WikiLog

In particular I thought this implementation was interesting:

http://pikie.darktech.org/cgi/pikie?DevelopmentWebLog

~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

[Phpwiki-talk] idle thoughts ...

[Adam S. <la...@sp...>]

one of the things i've been looking around for and thinking about is
integrating a wiki into a weblog.  though there has been a reasonable
amount of talk about this the closest i've seen is drupals book module
(which is brand spanking new).

http://www.drop.org/module.php?mod=book

i'm curious about two things.

has any thought been given to making phpwiki work as a php-nuke module (or
better imho a drupal module?).  i honestly have no idea what would be
involved in this.

second thing i think would be easy, but one of the tacks i'm thinking
about is using standard weblog rdf features available in a wiki.  what
would it take to make an rdf version of (for example) the RecentChanges
page so that a weblog could include it as a slashbox?

basically what i want to do (this is still a very unfinished idea so bear
with me :-) is have a weblog front end but use a wiki as a back end data
store.  the problem with weblogs is that once a story is a couple weeks
old (sometimes just a couple days old) it's pretty much dead.  wouldn't it
be cool if information could be moved from a weblog (where discussion
happens better then on a wiki) into a wiki where the thoughts can be
maintained and refined over time.

if you're curious rusty of k5 put up some interesting thoughts on meatball
wiki a while ago:

http://www.usemod.com/cgi-bin/mb.pl?WikiLog

adam.

Re: [Phpwiki-talk] Re: Install Question

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

>i *think* the two are equivelent to apache, so it
>should just be a matter of patching phpwiki to understand the encoded
>version of "?" as a legit delimiter.


The escaping hides the special meaning of '?' as a separator
between the resource name ('index.php') and the query args ('NomicFaq').
So, the escaped version causes apache to look for a file called
'index.php?NomicFaq', which of course doesn't exist.

-----
Here's another solution: replace your old html by a CGI script which
issues the HTTP redirect.  Here's one way:

1. Edit FAQ.html, so that it contains one line:

<?php header("Location: /~nomicwiki/index.php?NomicFaq"); ?>

(You need to include 'http://www.nomic.net' only if you're redirecting
to a different HTTP server.)

2. Now you need to convince apache that FAQ.html is really a PHP script.
One way (assuming apache is configured to allow it) is to place the
following three lines in the '.htaccess' file in the same directory
as 'FAQ.html':

<Files FAQ.html>
 SetHandler application/x-httpd-php
</Files>

(If you're running PHP3, you might have to change to middle line to:
'SetHandler application/x-httpd-php3'.)

I thought initially, this would have the same problem as your
RedirectMatch solution (I thought apache would escape the '?' before
sending it out) --- but I've just tried it, and it works, at least on
my system.  


Jeff

PS.  If you wanted to get fancy, or if you had a lot of files that have
moved, I think you can do basically the same thing by writing a "404
error handler" script. You use something like:

 ErrorDocument 404 /error404.php

either in httpd.conf or .htaccess to get your script ('error404.php') run
whenever someone requests a non-existent file.

The requested URL is available to the script in the variable $REDIRECT_URL.
The script can then figure out the new URL (either systematically, or by
lookup table) and issue the redirect.  Or if no suitable redirect is found,
it can produce an error message.

Re: [Phpwiki-talk] Re: Install Question

[Adam S. <la...@sp...>]

> I am trying to redirect one of my web-pages to a page within my
> NomicWiki. I'd rather do this properly using Apache's RedirectMatch
> directive in the .htaccess file (rather than having one of those
> annoying "this page will refresh in 5 seconds" pages).

if you use a refresh time of 0 it's not noticable to the end user.  i use
this as a way of redirecting old pages that i want to work but don't want
to support anymore around my site.

> But Apache does some kind of encoding on this and sends me to the URL:
> http://www.nomic.net/~nomicwiki/index.php%3fNomicFaq
> which, of course, doesn't work.

yep this is standard.  i *think* the two are equivelent to apache, so it
should just be a matter of patching phpwiki to understand the encoded
version of "?" as a legit delimiter.  i believe that "3f" is just the
hexified ascii code for "?".

> Also, I notice that a number of the text formatting rules pages are
> out of date. The rules at the bottom of the edit page still recommend
> ''' for bold. The TextFormattingRules page has several mistakes.

side question ... i poked around nomicwiki and is the sitemap feature a
standard phpwiki feature?

adam.

Re: [Phpwiki-talk] Re: Install Question

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

This isn't exactly a PhpWiki question, but it relates, and perhaps you
will know the answer.

I am trying to redirect one of my web-pages to a page within my NomicWiki.
I'd rather do this properly using Apache's RedirectMatch directive in the
.htaccess file (rather than having one of those annoying "this page will 
refresh in 5 seconds" pages).

But the problem is this: The URL I want to redirect to is:

http://www.nomic.net/~nomicwiki/index.php?NomicFaq

So I have the directive:

RedirectMatch permanent FAQ.html http://www.nomic.net/~nomicwiki/index.php?NomicFaq

But Apache does some kind of encoding on this and sends me to the URL:

http://www.nomic.net/~nomicwiki/index.php%3fNomicFaq

which, of course, doesn't work.

I have scoured the Apache manuals but cannot find a way to prevent this.
Does anyone have any suggestions?

I have considered moving to the new PhpWiki with USE_PATH_INFO, so I
can redirect to http://www.nomic.net/~nomicwiki/index.php/NomicFaq instead,
but I am reluctant to use an alpha copy and upgrading looks like too much
fuss.

While I am on the topic of upgrading, would it be possible to provide a 
set of templates and style files that look as much as possible like the
old PhpWiki? I like the way v1.2 looks better than the new layout.

Also, I notice that a number of the text formatting rules pages are out of
date. The rules at the bottom of the edit page still recommend ''' for bold.
The TextFormattingRules page has several mistakes. 

Malcolm

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

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

Re: [Phpwiki-talk] Re: Install Question

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

Hi Carla,

>I'm not sure about the CGI wrapper configuration. I'll see if I can see how 
>that works, and try to determine if PHP was installed that way or not.

Try creating a short php script (called, say, 'phpinfo.php') consisting
of the following line:

<?php phpinfo(); ?>

This script (when browsed) will report all sorts of information about
the configuration of your PHP.


Then report back with the output of that script (or just give us the
URL so we can go look ourselves.)

Best Regards,
Jeff Dairiki
<da...@da...>

[Phpwiki-talk] Re: Install Question

[Carla S. <cs...@mu...>]

At 05:26 PM 4/5/2001 -0400, Steve Wainstead wrote:
> > goes into the database, the PageName shows up as an anchor, but clicking on
> > the link doesn't navigate to the page.
> >          See: http://www.munex.net/phpwiki
>
>So far I can't figure out why it does this. Is there something nonstandard
>with your PHP setup? Do you use the CGI wrapper thing, for example? Have

Well, this was to be my first foray into PHP. (I've been running a 
customized Perl wiki application for awhile, and was looking into other 
options.) I have a brand new Cobalt RAQ4 that came with PHP pre-installed 
-- current builds of Linux, Apache, etc. I haven't tweaked that bundled 
installation at all. And I didn't attempt to change the phpwiki files, 
beyond configuring for MySQL as the database and the admin login -- as per 
instructions. So I think it's a pretty clean installation.

I'm not sure about the CGI wrapper configuration. I'll see if I can see how 
that works, and try to determine if PHP was installed that way or not.

Thanks for the response, though. Let me know if you have any further 
insights, and I'll do likewise.

sincerely,


           Carla J. Shafer, President/CEO
           Munex, Inc.

... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...
Munex is an Application Service Provider (ASP)
and data warehousing service offering
enterprise-scale applications to municipal
governments across public and private networks.

Find out more at http://www.munex.net
The Municipal Information Exchange              Munex Inc
phone: 607 216-0906                             PO Box 361
fax: 708 575-8658                               307 Willow Avenue
ICQ: 6262998                                    Ithaca NY 14851-0361
... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...

[Phpwiki-talk] Re: Install Question

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

On Wed, 4 Apr 2001, Carla Shafer wrote:

> Hi Steve,
>
> You emailed me about a month ago in response to an error I was getting with
> my phpwiki installation, which I've since resolved. The problem was at my
> end, with my MySQL setup. Now the wiki app loads up nicely, but all the
> page links seem to return to FrontPage. Have you had this experience?

I've never seen this... all the links go to FrontPage. It's really weird.

> In the MySQL database, the "wiki" table has all the default page data (20
> pages I think). I noticed that the archive table only had a record for
> FrontPage, so I tried inserting duplicate records in that table as well,
> hoping that might fix the problem. But no luck.

No, that would have no effect for this problem... it has nothing to do
with the archive table.

> If I add a new page, I get the same situation, the page definition data
> goes into the database, the PageName shows up as an anchor, but clicking on
> the link doesn't navigate to the page.

>          See: http://www.munex.net/phpwiki
>
> I'm hoping you have a quick and easy answer. ;-)

So far I can't figure out why it does this. Is there something nonstandard
with your PHP setup? Do you use the CGI wrapper thing, for example? Have
you edited any of the files like display.php or transform.php? It looks
like you are using the 1.2 version of PhpWiki.

~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

[Phpwiki-talk] Re: Upgrade script for PhpWiki 1.0 -> 1.2

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

I just picked up on this again... you mentioned it previously but it went
under my radar: you're using the nightly build, which is alpha software!
Try installing 1.2 instead, which is stable and recommended:

http://download.sourceforge.net/phpwiki/phpwiki-1.2.0.tar.gz

I think your formatting problems and page editing problems will go away if
you use 1.2 instead. The nightly build has a radically different rendering
engine that doesn't support the old markup language; 1.2 does though.

~swain

On 1 Apr 2001, Gary Lawrence Murphy wrote:

> >>>>> "S" == Steve Wainstead <sw...@pa...> writes:
>
>     S> Can you point me to an example page?
>
>     S> On 31 Mar 2001, Gary Lawrence Murphy wrote:
>
>     >> The convertion was relatively painless, but one small question:
>     >> The page contents are being marked up with <pre> tags but the
>     >> line lengths are being translated as one paragraph per line
>     >> leading to huge page widths.  Is there an easy fix for this?
>
> The problem is the difference between tab-* (old syntax points) and
> just * (new syntax) the tab-*'s not converted in the update process
> become rendered as PRE content because (rightly so) the line begins
> with a whitespace.
>
> --
> Gary Lawrence Murphy <ga...@te...> TeleDynamics Communications Inc
> Business Innovations Through Open Source Systems: http://www.teledyn.com
> "Computers are useless.  They can only give you answers."(Pablo Picasso)
>

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

[Phpwiki-talk] Upgrade script for PhpWiki 1.0 -> 1.2

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

OK, this is a fine example of cut and paste programming, but it works OK
for the test sites I used. I set up brand new 1.0 and 1.2 sites, and
converted the 1.0 dbm files to 1.2 dbm files and it seems to work fine.

This should be integrated with the admin functionality; in fact in the
first version of the admin functionality it was (there is still a script
in the admin/ directory called wiki_port1_0.php) but it no longer works.

This script should be self explanatory; all you need to do is set the
variables at the beginning of the script that point to the DBM files, both
old and new. It will open the 1.0 file as read-only, for your peace of
mind ;-)

After you run the script you will have new DBM files; edit the config.php
file for your 1.2 installation to use them (I used the default names so
this should be easy).

~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

[Phpwiki-talk] gettext, at last

[Jan N. <ja...@gn...>]

Hi list,

At last, I found why my gettext isn't working.  Apparently, this is
needed for some newer gettext implementations.

Greetings,
Jan.

--- lib/config.php~	Fri Mar 30 23:02:44 2001
+++ lib/config.php	Fri Mar 30 23:01:16 2001
@@ -91,6 +91,7 @@
 else
 {
    putenv ("LANG=$LANG");
+   setlocale ("LC_ALL", "");
    bindtextdomain ("phpwiki", "./locale");
    textdomain ("phpwiki");
 }

-- 
Jan Nieuwenhuizen <ja...@gn...> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien       | http://www.lilypond.org

Re: [Phpwiki-talk] Question about diff?

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

Hi Toan,

Right now PhpWiki will only save the last version of the page. We are now
planning on adding the ability to keep multiple versions in the archive.

Cheers
~swain

On Fri, 30 Mar 2001, Toan wrote:

> Hi,
> My name is Toan Vo and I php programer.  I try to download your phpwiki
> web and set it up with mysql.  It's working fine but then my question
> is: when I change something on a page, it only keep 2 version: one is the
> original and one is the current version.  It doesn't keep 4 version if I
> change a page 4 times.  Is that you can control on setup or not?  And can
> where is the manual for the Administrator?
>
> Thank you.
>
> Toan
>
>
>
>
> _______________________________________________
> Phpwiki-talk mailing list
> Php...@li...
> http://lists.sourceforge.net/lists/listinfo/phpwiki-talk
>

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

[Phpwiki-talk] Question about diff?

[Toan <to...@ar...>]

Hi,
My name is Toan Vo and I php programer.  I try to download your phpwiki
web and set it up with mysql.  It's working fine but then my question
is: when I change something on a page, it only keep 2 version: one is the
original and one is the current version.  It doesn't keep 4 version if I
change a page 4 times.  Is that you can control on setup or not?  And can
where is the manual for the Administrator?

Thank you.

Toan

Re: [Phpwiki-talk] Wiki URLs

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

>http://phpwiki.sourceforge.net/alpha/index.php/PhpWiki
>
>I would like to be able to do this on my NomicWiki. Could you please explain
>how it was achieved?

The part of the URL after the CGI script name ('/PhpWiki' in the above
example) is available in the $PATH_INFO environment variable.

Note that with some minor tricks, you can also set up the latest
alpha version of PhpWiki to use URLs like:

  http://phpwiki.sourceforge.net/alpha/PhpWiki

There's more discussion on this topic at:

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


The easiest way to get this feature is probably to "upgrade" to
the alpha version.  There's a nightly snapshot at:
 ftp://phpwiki.sourceforge.net/pub/phpwiki/phpwiki.nightly.tar.gz

If you don't want to "upgrade", you can look at the code in the alpha
version to see how it's done.


(The alpha version has been pretty static for the past couple of weeks,
so if you grab a snapshot right now, it should be sort of "stable".)

Steve: Maybe there should be a alpha release?  (Also a 1.2.1 release? ---
but I guess maybe we should fix the case sensitivity in page-name bugs
first.)

[Phpwiki-talk] Wiki URLs

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

I notice that the alpha version of PhpWiki allows URLS like:

http://phpwiki.sourceforge.net/alpha/index.php/PhpWiki

instead of:

http://phpwiki.sourceforge.net/alpha/index.php?PhpWiki

I would like to be able to do this on my NomicWiki. Could you please explain
how it was achieved?

Malcolm

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

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