phpwiki-talk

Re: [Phpwiki-talk] Ampersand

[Klaus - G. L. <Le...@we...>]

Hello,
> > I have a question regarding international characters not in the wiki
> > character set. Since the ampersand gets escaped I am not able to
> > use ccharacter eentities. What was the reason for this design.. ?

> Offhand, I can't think of a reason why entities should be allowed.
> Can anyone else?
> 
> Note that currently the page data is stored as ISO-8859-1,
> so you can use any ISO-8859-1 character, as long as you can
> figure out how to type it in directly.  This handles all
> the western european accented and umlauted characters (=F9=FA=FB=FC)
> as well as a few funky things like =A7=BC=BD=BE=D7=A9=A5=AE=B0=B1=B5=B6
My question provides part of the answer, I asked because of
characters "not" in the wiki character set. But this is for future
use. My real reason for the question was that in a webboard
that I use we had difficulties with this. There had been users
with different computerplatforms and different local charsets
and the charcaters above 127 were different. I assume that
is a problem of the browser. To get this correct the browser
would have to translate the charecterset during input. This
seemed not to function. I have no experience with this
situation in phpwiki since at the moment all users of my wiki
use the same platform and the same character set. I asked
now because i wanted to be sure that future users could get
the correct characters into the wiki. I think if you wanted to
discuss music or language you would need many characters
that are not in ISO-8859-1.

> If we allowed entities, we'd want to convert ones representable
> in ISO-8859-1 to ISO-8859-1 upon page saving, since otherwise it
> would hinder searching.  (Searches for "H=E4schen" won't find
> the text "Häschen".)
This could mean that entities have to be allowed also in searches.
 
> Allowing entities would be a simple enough fix.  I'll do it
> if no one comes up with a reason not to.

Another unrelated question, if I try to answer a message from
the list, the address is that of the sender and not the list. Is it
recommend that I answer only to the person or should I answer
to the list.

Klaus Leiss

Re: [Phpwiki-talk] cvs log tag

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

On Sat, 28 Dec 2002 17:43:38 -0500 (EST)
Steve Wainstead <sw...@pa...> wrote:

> 
> I'm thinking of adding a block to the bottoms of all files in the form:
> 
> <?
> // $Log$
> ?>
> 
> What this would do is include the cvs log message every time a file is
> committed. I've found from work in the Real World that when a project is
> moved to a new cvs server, all the messages are lost.

... 

> If anyone objects please let me know. Below is a much longer explanation
> from the red bean cvs book.


... I'm catching up on mail ...

My feelings on this:

  o This is going to make the PhpWiki source bigger than it already is!
    It's already very big.  The .php files gets loaded/parsed every time
    a page is viewed --- though I doubt the log comments contribute much
    to the load time, they don't help either.

  o In other projects, I've always found a global ChangeLog to be
    much more useful.  I personally prefer the GNU-style, manually
    generated ChangeLog --- since then the whole log is tailored to
    be human readable.  One simply has to grep the file to find notes
    of interest.  (Of course, all the developers have update the
    ChangeLog, or else...)  An example would be:

====
 2003-02-20  Geoffrey T. Dairiki  <da...@da...>

	Have implemented the ability to cache marked up page text.
	(Had this been a real ChangeLog, I should have expounded
	a bit more here...)

	* lib/CachedMarkup.php: New file.
	* lib/main.php(main): Query-arg hook 'nocache' to disable markup cache.
	Use 'nocache=1' to disable reading the cache, 'nocache=purge'
	to clear the cache for the requested page.
	* lib/BlockParser.php: Changes for cached markup.
	Tweaks of list tightness logic.
 	* lib/display.php: Minor fixes for new cached markup.
	* lib/loadsave.php: ditto
	* lib/XmlRpcServer.php: ditto
	* lib/plugin/RecentChanges.php: ditto
	* lib/plugin/IncludePage.php: ditto
	* lib/plugin/UnfoldSubpages.php: ditto
	* lib/plugin/SiteMap.php: ditto
	* lib/plugin/OldStyleTable.php: ditto 


	* lib/stdlib.php(LinkBracketLinks): Moved to InlineParser.
	* lib/InlineParser.php: see above

	New class DebugTimer to help in execution profiling.
	* lib/main.php: Moved debug timing to prepend.php
	* lib/prepend.php(DebugTimer): New class.
	* lib/plugin/AllPages.php: Use DebugTimer for timing.
	* lib/plugin/AllUsers.php: ditto
	* themes/default/templates/debug.tmpl: ditto
====

    Using a manually generated global changelog like this makes
    working off-line on large changes easier.  Suppose I spend a
    couple days/week/months adding some big new feature to PhpWiki.
    When I go to check my changes in to CVS, I find I've touched
    nearly all of the files in the lib/ subdirectory.

    It's a big pain to check these in one at a time, and come up with
    diff each one to come up with useful CVS log entries for each one,
    so I'm likely to check them all in at once with some message like:
    "Big Change!  Added new XXX feature."

    If I'd just been keeping my local copy of ChangeLog up-to-date
    as I hacked, and if there were a global ChangeLog in CVS, all
    I have to do is merge the two and then the global ChangeLog is again
    meaningful...


Anyhow, my personal vote would be: no $Log$ in individual source files.
Move over to (enforced by public flogging) use of a GNU-style
global ChangeLog.

Re: [Phpwiki-talk] template php execution?

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

> Quick question:  Is there a way to execute php code from a template?

If you're using PhpWiki 1.3.x, yes.  You just put in the PHP code.
(Though be careful --- "you break it, you bought it..." :-)

> Or is there a way (what I really want) to include a flat html file at
> runtime?

Like this:
   <?php include("/path/to/your/file.html"); ?>


(If you're using PhpWiki 1.2.x, sorry, but the answers are no...)

[Phpwiki-talk] php warning?

[Johannes R. <jr...@we...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I got the following Warnings in my Wiki:

PHP Warnings
lib/config.php:145: Notice[8]: Object to string conversion
lib/config.php:145: Notice[1024]: Object

I'd experimented with the authorisations, but this i didn' get it work.

So if you've go some suggestions, i'll be a happy men...

Joe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+Vmi0nmAbbUgFSFgRAuusAJ0fYPjVdJ5KptayWaM6CykOppD7BwCeNMdF
G9ipAqfLcdEKg0GkNYl6PHE=3D
=3DDa91
-----END PGP SIGNATURE-----

Re: [Phpwiki-talk] Printed version : usage of phpwiki-printer.css

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

> Is there a way of having easily a version of a page for printing (for
> example, without the buttons for edit, diff...) ?

Telling your browser to use the "Printer" stylesheet is supposed to do
exactly that --- but I see that at the moment, that doesn't seem to be
work.

I guess your note should be considered a bug report...

Re: [Phpwiki-talk] Ampersand

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

> I have a question regarding international characters not in the wiki
> character set. Since the ampersand gets escaped I am not able to
> use ccharacter eentities. What was the reason for this design.. ?

This has been discussed before, but I don't remember the answer.

Offhand, I can't think of a reason why entities should be allowed.
Can anyone else?

Note that currently the page data is stored as ISO-8859-1,
so you can use any ISO-8859-1 character, as long as you can
figure out how to type it in directly.  This handles all
the western european accented and umlauted characters (=F9=FA=FB=FC)
as well as a few funky things like =A7=BC=BD=BE=D7=A9=A5=AE=B0=B1=B5=B6

If we allowed entities, we'd want to convert ones representable
in ISO-8859-1 to ISO-8859-1 upon page saving, since otherwise it
would hinder searching.  (Searches for "H=E4schen" won't find
the text "Häschen".)

Allowing entities would be a simple enough fix.  I'll do it
if no one comes up with a reason not to.

[Phpwiki-talk] template php execution?

[<je...@au...>]

Hi,

Quick question:  Is there a way to execute php code from a template?
Or is there a way (what I really want) to include a flat html file at
runtime?

Sorry if this is a repeat question.  I've searched the wiki, the
forum, and a quick search of this mail archive but didn't find it.

thanks in advance,
jeremy


-- 
Jeremy Kelley  <je...@au...>
Information Security Analyst

[Phpwiki-talk] "Wikishow like" in PhpWiki

[Jean-Philippe G. <jpg...@ou...>]

Hi,

Is there someone work on a "WikiShow" plugin ?
http://phpwiki.sourceforge.net/phpwiki/WikiShow

"The idea is that with just a few simple commands a page of text can
be turned into a slide show." WikiShow is actually a python script.


WikiShow Demo 

Source for presentation
http://emergent.brynmawr.edu/wiki/index.cgi/WikiShow
Presentation
http://emergent.brynmawr.edu/~dblank/wikishow/?show=WikiShow

-- 
Jean-Philippe Georget
jpg...@ou... - http://jpgeorget.ouvaton.org/

[Phpwiki-talk] Printed version : usage of phpwiki-printer.css

[Jean-Philippe G. <jpg...@ou...>]

Hi,


Is there a way of having easily a version of a page for printing (for
example, without the buttons for edit, diff...) ?

A simple button, in the top or bottom bar, could be great.


Perhaps, I can use phpwiki-printer.css too but I didn't understand how
use it.


Thanks for your suggestions.


-- 
Jean-Philippe Georget
jpg...@ou... - http://jpgeorget.ouvaton.org/

[Phpwiki-talk] Ampersand

[Leiss, Klaus-G. 3. S-PP-RD-E. <Kla...@he...>]

Hello,
I have a question regarding international characters not in the wiki
character set. Since the ampersand gets escaped I am not able to
use character entities. What was the reason for this design, is there
a sequrity reason for it. If not I would like to implement something
that enables me to use some.

Klaus Leiss

Re: [Phpwiki-talk] Speaking of breaking things. (was Re: xgettext problem (was ...))

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

Jeff Dairiki schrieb:
> All righty indeed.  I've just checked in the latest hacks.

Whow!
Now this thing should be fast enough.

Re: [Phpwiki-talk] Speaking of breaking things. (was Re: xgettext problem (was ...))

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

Jeff Dairiki schrieb:
> On Thu, 20 Feb 2003 08:34:11 +0100
> Reini Urban <ru...@x-...> wrote:
>>Please do so. Good stuff.

>>I'm also refactoring my UserAuth stuff, as promised years :) ago.
> 
> 
> Ooh. Very good.
> 
> I've a couple comments/suggestions, I suspect you might already have
> thought of these, but I'd thought I'd toss them out.
> 
> 1. Each of the authentication methods and means of storing/retrieving
>    user information (i.e. prefs, password, etc...) should be encapsulated
>    in an object.
> 
>    I.e. introduce a new virtual base class called AuthDB.  I, obviously
>    haven't thought this out too fully, but something like.
> 
>    // Return codes.  Note that you can check for success
>    // by casting to int:  if ((int)$db->checkPassword(...))...
>    define ('AUTHDB_OK', "1 OK");
>    define ('AUTHDB_BADUSER', "0 Bad User");
>    define ('AUTHDB_BADPASSWORD', "0 Bad Password");
> 
>    // AuthDB doesn't support the requested operation.
>    define ('AUTHDB_NOTSUPPORTED', "0 Not Supported");
>  
>    class AuthDB {
> 
>         // Get name of authentication method.
>         function getName() { return get_class($this); // or something ? }
> 
> 	// Returns AUTH_LEVEL, or one of
> AUTHDB_{BADUSER,BADPASSWORD,NOTSUPPORTED}
> 	//
> 	function checkPassword($userid, $password) { return AUTHDB_NOTSUPPORTED;
> }
>         function setPassword($userid, $oldpw, $newpw) { return
> AUTHDB_NOTSUPPORTED; }
> 
>         // ... this part is a little fuzzier as to exact API...
>         function createUser($userid, $user_data) { return
> AUTHDB_NOTSUPPORTED; }
>         function getUserData($userid) { return AUTHDB_NOTSUPPORTED; }
>         function updateUserData($userid, $user_ata) { return
> AUTHDB_NOTSUPPORTED; }
>         // ...
>    }
> 
>    There would be a subclass of AuthDB for each type of authentication.
>    (Including AuthDBAdmin (for authentication vs the admin name and pw
>    in index.php) and AuthDBBogo.)
> 
> 
>    Then, e.g. to check passwords, instead of giant nested ifs which need
>    to be adjusted every time someone wants to add a new authentication
> method:
> 
>    class WikiUser {
>      ...
>      function _pwcheck($user, $pw) {
>        global $AuthMethods;
>        foreach ($AuthMethods as $db) {
>             $authlevel = $db->checkPassword($user, $pw);
>     	    if ((int)$authlevel)
> 	        return $authlevel;
>        }
>        return WIKIAUTH_ANON;
>      }
>    } 
> 
> 
> 2. Probably we need to identify and handle two different kinds of prefs.
>    There are some which should definitely be storable in a cookie, e.g.
>    for anonymous users --- things like date-formatting preference,
>    and edit area size, (and default user name).
> 
>    Things like password and e-mail are more tightly associated with
>    an _authenticated_ user.  These, of course, should not be stored
>    in cookies... I think we should start calling them user_data
>    instead of prefs.
> 
>    Of course, users might want to store prefs as part of their user_data.
>    (It's unclear to me which should take precedence if prefs are available
>    both from a cookie and from $user_data['prefs']...)
> 
> 2a.When refactoring make sure that it's easy to drop back to only
>    allowing BOGO-authentication.   I had to comment out a lot of
>    code (and munge some templates pretty heavily) to get this to work
>    and look reasonably clean...
> 
>    Many wikis will want to remain (in the wiki tradition) open, with
>    no user registration.

Sure. Only optional.

> 2b.Please make it easy to disable the auto-generation of all the fancy
>    user sub-pages.  I can see where some might like them, but to me
>    they seem very non-wiki-ish...

ok.

> PS: Is the current user authentication code working at all?  I notice
>   there's   been a number of questions about it on the SourceForge forums.
>  
>   E.g. http://sourceforge.net/forum/message.php?msg_id=1889421   (and
>   others).   You might want to post a note over there to let people know
> the
>   status.  (I would do it, but I'm unsure of the status.)

Ok, I'll do.

The current status is that:
Works for me, but not in CVS (disabled there),
and just for my limited set of needed options:
mysql auth with a user table with password.

CREATE TABLE users (
   userid char(48) binary NOT NULL UNIQUE,
   passwd char(48) binary default '*',
   PRIMARY KEY (userid)
) TYPE=MyISAM;

but I will test with that now:
CREATE TABLE users (
   userid char(48) binary NOT NULL UNIQUE,
   passwd char(48) binary default '*',
   pref text NULL default '',
   PRIMARY KEY (userid)
) TYPE=MyISAM;

$DBAuthParams['auth_dsn'] = $DBParams['dsn'];
$DBAuthParams['pref_select'] = 'SELECT pref FROM users WHERE 
userid="$userid"';
$DBAuthParams['pref_update'] = 'UPDATE users SET pref="$pref_blob" WHERE 
userid="$userid"';
$DBParams['dbtype'] = 'SQL';

I'll rewrite it with the abstract base class AuthDB, as you suggested.
Of course the current status (bogo) will be the default auth method.

And I want to test it with phpnuke and other frameworks also
before I commit.
groups and page permissions later.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

[Phpwiki-talk] phpwiki as CMS module

[Rodolfo P. <ro...@pi...>]

Can you tell me if exist a document that explain how to
use/adapt/arrange phpwiki as a CMS module?

I know that phpwiki is the wiki engine for several CMS and I wish to add
one more.

-- 
Rodolfo Pilas <ro...@pi...>

Re: [Phpwiki-talk] Speaking of breaking things. (was Re: xgettext problem (was ...))

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

On Thu, 20 Feb 2003 08:59:32 -0800
Jeff Dairiki <da...@da...> wrote:

> On Thu, 20 Feb 2003 08:34:11 +0100
> Reini Urban <ru...@x-...> wrote:
> 
> > Please do so. Good stuff.
> 
> All righty.  Expect it later today.

All righty indeed.  I've just checked in the latest hacks.

The only thing I know for sure that will break is your InterWikiMap.

Now, the InterWikiMap has to have meta-data specifying that it is
of pagetype interwikimap.  The only way currently to set this meta-data
is by loading a page (e.g. from zip or pgsrc).

So if you should load the latest pgsrc/InterWikiMap (or just start
with a virgin wiki) your InterWikiMap should work again...

[Phpwiki-talk] Re: Probleme in localisation

[Jean-Philippe G. <jpg...@ou...>]

Jean-Philippe Georget <jpg...@ou...> a =E9crit :

> I trie to use PhpWiki on sourceforge.net with $LANG=3D"fr" but links,
> pages and HomePage are in english.
>=20
> I make these changes to index.php :
>=20
> line 419 :
>=20
[...]
>      if (!isset($LANG)) { $LANG =3D "fr"; }
>     =20
> and add these lines :
>=20
>      if (!defined('HOME_PAGE'))
>          define('HOME_PAGE', "Accueil");
>      if (!defined('DEFAULT_LANGUAGE'))
>           define('DEFAULT_LANGUAGE', 'fr');
>     =20
> To have french pages, I change=20
>=20
>         if (!defined('WIKI_PGSRC')) define('WIKI_PGSRC', 'pgsrc');
>=20
> into
>=20
>         if (!defined('WIKI_PGSRC')) define('WIKI_PGSRC', 'locale/fr/pgs=
rc');
>=20
>=20
>=20
> In lib/config.php, I comment :
>=20
>=20
>      if (!defined('HOME_PAGE'))
>          define('HOME_PAGE', _("HomePage"));
>      if (!defined('DEFAULT_LANGUAGE'))
>           define('DEFAULT_LANGUAGE', 'fr');
>=20
>=20
>=20
>=20
> Perhaps there is a more simple way to do this ?

Yes : don't use configurator.php and modify index.php directly.=20

--=20
Jean-Philippe Georget
jpg...@ou... - http://jpgeorget.ouvaton.org/

Re: [Phpwiki-talk] Speaking of breaking things. (was Re: xgettext problem (was ...))

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

On Thu, 20 Feb 2003 08:34:11 +0100
Reini Urban <ru...@x-...> wrote:

> Please do so. Good stuff.

All righty.  Expect it later today.

> I'm also refactoring my UserAuth stuff, as promised years :) ago.

Ooh. Very good.

I've a couple comments/suggestions, I suspect you might already have
thought of these, but I'd thought I'd toss them out.

1. Each of the authentication methods and means of storing/retrieving
   user information (i.e. prefs, password, etc...) should be encapsulated
   in an object.

   I.e. introduce a new virtual base class called AuthDB.  I, obviously
   haven't thought this out too fully, but something like.

   // Return codes.  Note that you can check for success
   // by casting to int:  if ((int)$db->checkPassword(...))...
   define ('AUTHDB_OK', "1 OK");
   define ('AUTHDB_BADUSER', "0 Bad User");
   define ('AUTHDB_BADPASSWORD', "0 Bad Password");

   // AuthDB doesn't support the requested operation.
   define ('AUTHDB_NOTSUPPORTED', "0 Not Supported");
 
   class AuthDB {

        // Get name of authentication method.
        function getName() { return get_class($this); // or something ? }

	// Returns AUTH_LEVEL, or one of
AUTHDB_{BADUSER,BADPASSWORD,NOTSUPPORTED}
	//
	function checkPassword($userid, $password) { return AUTHDB_NOTSUPPORTED;
}
        function setPassword($userid, $oldpw, $newpw) { return
AUTHDB_NOTSUPPORTED; }

        // ... this part is a little fuzzier as to exact API...
        function createUser($userid, $user_data) { return
AUTHDB_NOTSUPPORTED; }
        function getUserData($userid) { return AUTHDB_NOTSUPPORTED; }
        function updateUserData($userid, $user_ata) { return
AUTHDB_NOTSUPPORTED; }
        // ...
   }

   There would be a subclass of AuthDB for each type of authentication.
   (Including AuthDBAdmin (for authentication vs the admin name and pw
   in index.php) and AuthDBBogo.)


   Then, e.g. to check passwords, instead of giant nested ifs which need
   to be adjusted every time someone wants to add a new authentication
method:

   class WikiUser {
     ...
     function _pwcheck($user, $pw) {
       global $AuthMethods;
       foreach ($AuthMethods as $db) {
            $authlevel = $db->checkPassword($user, $pw);
    	    if ((int)$authlevel)
	        return $authlevel;
       }
       return WIKIAUTH_ANON;
     }
   } 


2. Probably we need to identify and handle two different kinds of prefs.
   There are some which should definitely be storable in a cookie, e.g.
   for anonymous users --- things like date-formatting preference,
   and edit area size, (and default user name).

   Things like password and e-mail are more tightly associated with
   an _authenticated_ user.  These, of course, should not be stored
   in cookies... I think we should start calling them user_data
   instead of prefs.

   Of course, users might want to store prefs as part of their user_data.
   (It's unclear to me which should take precedence if prefs are available
   both from a cookie and from $user_data['prefs']...)

2a.When refactoring make sure that it's easy to drop back to only
   allowing BOGO-authentication.   I had to comment out a lot of
   code (and munge some templates pretty heavily) to get this to work
   and look reasonably clean...

   Many wikis will want to remain (in the wiki tradition) open, with
   no user registration.

2b.Please make it easy to disable the auto-generation of all the fancy
   user sub-pages.  I can see where some might like them, but to me
   they seem very non-wiki-ish...
   

Whew... that's a load off my chest.  Sorry ... I didn't mean to
unload on you like that.  :-)


Jeff

PS: Is the current user authentication code working at all?  I notice
  there's   been a number of questions about it on the SourceForge forums.
 
  E.g. http://sourceforge.net/forum/message.php?msg_id=1889421   (and
  others).   You might want to post a note over there to let people know
the
  status.  (I would do it, but I'm unsure of the status.)

Re: [Phpwiki-talk] Speaking of breaking things. (was Re: xgettext problem (was ...))

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

Jeff Dairiki schrieb:
>>However, it appears there is another problem: xgettext (from 
>>locale/Makefile) is not extracting the string in this line of 
>>JavaScript from signin.tmpl:
>>
>>     document.write('&nbsp;<?= _("Sign in:") ?>');
>>
>>Hmm... anyone have any ideas to fix or work around this? 
> 
> 
> Oh.
> 
> A hack would be to do:
> 
>     <?php
>        $sign_in = _("Sign in:");
>     ?>
>     <!-- stuff -->
>         document.write('&nbsp;<?= $sign_in ?>');
> 
> 
> 
> 
> Speaking of breaking things...
> 
> I've been working on several fairly major changes/enhancements.
> 
>  o As promised years ago, I've just about gotten cached markup working.
>    (The transformed text of the most recent version of each page
>    is cached ... this results in a factor of 2-3 (sometimes more) speedup
>    on larger pages.
> 
>  o As a side effect (again, as promised years ago) this eliminates
>    the need for a separate ExtractWikiPageLinks().  (A really good thing).
> 
> This broke a lot of stuff and required fairly major changes to some 
> parts of the code:
> 
>  o I've severely refactored the stuff in PageType.php, also
> plugin/WikiBlog
>    has been refactored beyond recognition.
> 
>  o I'm sure I've broken lots of other things.
> 
> I'm about ready to check all this into CVS.  (Probably some time
> tomorrow...)
> 
> If anybody wants me to wait a bit before breaking the CVS code, now's
> the time to speak up!

Please do so. Good stuff.
I'm also refactoring my UserAuth stuff, as promised years :) ago.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: [Phpwiki-talk] Speaking of breaking things. (was Re: xgettext problem (was ...))

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

No objections from me at all to refactoring of PageType, I admit it was 
most hackish. I had some changes to WikiBlog but nothing special, 
instead I look forward to see what you've done with it :)

The html caching sounds very exciting too!

Carsten

On Wednesday, February 19, 2003, at 10:03  pm, Jeff Dairiki wrote:

> Speaking of breaking things...
>
> I've been working on several fairly major changes/enhancements.
>
>  o As promised years ago, I've just about gotten cached markup working.
>    (The transformed text of the most recent version of each page
>    is cached ... this results in a factor of 2-3 (sometimes more) 
> speedup
>    on larger pages.
>
>  o As a side effect (again, as promised years ago) this eliminates
>    the need for a separate ExtractWikiPageLinks().  (A really good 
> thing).
>
> This broke a lot of stuff and required fairly major changes to some
> parts of the code:
>
>  o I've severely refactored the stuff in PageType.php, also
> plugin/WikiBlog
>    has been refactored beyond recognition.
>
>  o I'm sure I've broken lots of other things.
>
> I'm about ready to check all this into CVS.  (Probably some time
> tomorrow...)
>
> If anybody wants me to wait a bit before breaking the CVS code, now's
> the time to speak up!
>
> Jeff

[Phpwiki-talk] Speaking of breaking things. (was Re: xgettext problem (was ...))

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

> However, it appears there is another problem: xgettext (from 
> locale/Makefile) is not extracting the string in this line of 
> JavaScript from signin.tmpl:
> 
>      document.write('&nbsp;<?= _("Sign in:") ?>');
> 
> Hmm... anyone have any ideas to fix or work around this? 

Oh.

A hack would be to do:

    <?php
       $sign_in = _("Sign in:");
    ?>
    <!-- stuff -->
        document.write('&nbsp;<?= $sign_in ?>');




Speaking of breaking things...

I've been working on several fairly major changes/enhancements.

 o As promised years ago, I've just about gotten cached markup working.
   (The transformed text of the most recent version of each page
   is cached ... this results in a factor of 2-3 (sometimes more) speedup
   on larger pages.

 o As a side effect (again, as promised years ago) this eliminates
   the need for a separate ExtractWikiPageLinks().  (A really good thing).

This broke a lot of stuff and required fairly major changes to some 
parts of the code:

 o I've severely refactored the stuff in PageType.php, also
plugin/WikiBlog
   has been refactored beyond recognition.

 o I'm sure I've broken lots of other things.

I'm about ready to check all this into CVS.  (Probably some time
tomorrow...)

If anybody wants me to wait a bit before breaking the CVS code, now's
the time to speak up!
 
Jeff

xgettext problem (was Re: [Phpwiki-talk] Diff to support french translation in themes/default/templates/signin.tmpl)

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

Thanks for the patch Jean-Philippe.


However, it appears there is another problem: xgettext (from 
locale/Makefile) is not extracting the string in this line of 
JavaScript from signin.tmpl:

     document.write('&nbsp;<?= _("Sign in:") ?>');

Hmm... anyone have any ideas to fix or work around this? 
(Jean-Philippe's patch only fixes fr/LC_MESSAGES/phpwiki.php, doesn't 
fix the fr.po and fr/LC_MESSAGES/phpwiki.mo files or other languages).

Carsten

On Wednesday, February 19, 2003, at 07:19  pm, Jean-Philippe Georget 
wrote:

> Hi,
>
>
> A minor diff for locale/fr/LC_MESSAGES/phpwiki.php to support last
> modification of themes/default/templates/signin.tmpl
>
>
> Hope that help.
>
>
> <phpwiki.php.diff>
>
>
>
> -- 
> Jean-Philippe Georget
> jpg...@ou... - http://jpgeorget.ouvaton.org/

[Phpwiki-talk] UserPreferences and UserHomePage/Preferences

[Jean-Philippe G. <jpg...@ou...>]

Hi,

I try to use the UserPreferences Plugin.

I created a user homepage JohnDoe. Then I created
[JohnDoe/Preferences] and edit <?plugin UserPreferences?> in it as I
understand in lib/plugin/UserPreferences.php.


I obtain this error :

  Error: The page with the UserPreferences plugin must be valid
  WikiWord or a Preferences subpage of the users HomePage. Sorry,
  UserPreferences cannot be saved.
  


Perhaps I misunderstood due to my poor english :-(


Can you explain me what's wrong with it ?


-- 
Jean-Philippe Georget
jpg...@ou... - http://jpgeorget.ouvaton.org/

Re: [Phpwiki-talk] Where are my popular nearby links ????

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

Hi Rob,

The "nearby links" feature is indeed no longer available since PhpWiki 
Classic.

In the current version of PhpWiki in lieu of having nearby links on 
every page, you probably coule use other new plugins to provide 
appropriate links on specific pages wherever needed. For one example, 
see the Contents section of the PhpWiki demo pages at 
<http://phpwiki.sourceforge.net/demo/en/PhpWikiDocumentation> (which 
dynamically generates "related" pages, embedded into the page itself).

I haven't heard of anyone else planning to do so, but with the new 
plugin API/mechanism it probably would be easy to add "nearby links" 
functionality back into PhpWiki again, and then just add that plugin 
into a page template.

Carsten

On Wednesday, February 12, 2003, at 04:00  am, Rob Coenen wrote:

> Hello all, I am copy + pasting a topic from the Wiki forum here, as 
> this
> particular topic has my intrest aswell, and there seems to be so low 
> traffic
> on the forum that I just want to try it this way:
> ====================================
>
> Hi
> I've installed the lastest version of phpwiki and at first I must say 
> that
> the design is really cool.
>
> Trouble is
> I've noticed that the "quick links" between the pages that are 
> "nearby" (5
> best incoming links, 5 best outgoing links, 5 most popular nearby) have
> disappeared in this version
>
> I do think it was the greatest features of phpwiki. It's the best way 
> for a
> user to browse the wiki : for example in a documentation, the "related
> topics" were made automatically !
>
> Is there a way to have this feature back in the newer version ??
>
> or must I go back to the phpwiki classic :-( ?

[Phpwiki-talk] phpWiki 1.3.4+ Apache 2.0.43 + MySQL 4.0.6 on W2k

[Tobias G. <tob...@ca...>]

Hello,

I've installed phpWiki on a W2k-machine with Apache 2.0.43 and MySQL
4.0.6. The changes I've done to the index.php are the following:

 if (!defined('WIKI_NAME')) define('WIKI_NAME', 'MyWiki');
 if (!defined('ADMIN_USER')) define('ADMIN_USER', "Administrator");
 if (!defined('ADMIN_PASSWD')) define('ADMIN_PASSWD', "1862187");
 'dbtype' => 'SQL',
 //'dbtype'   => 'dba',
 dsn' => 'mysql://wiki@localhost/wiki',
 ini_set('session.save_path', 'tmp');
 if (!defined('USE_PATH_INFO')) define('USE_PATH_INFO', false);

The I've created the tables and opend the /index.php.
So far everything worked as expected.

When I now go into the sandbox and click on edit, the edit page
appears, but ends with this invalid code fragment:


<script language="JavaScript1.3" type="text/javascript"></script>
--
function showOldMarkupRules(show) {
  if (document.getElementById) {
    if (!show) {
      document.getElementById('newMarkup').style.display="block";
      document.getElementById('oldMarkup').style.display="none";
    } else {
      document.getElementById('newMarkup').style.display="none";
      document.getElementById('oldMarkup').sty

When I make any changes to the sandbox and want to save or preview, it
just displays the old content again and ignores my changes.

Where do I have to search for the problem, that causes this?

Greetings,

Tobias

PS: Is it possible to set USE_PATH_INFO to true for Apache 2? I couldn't
find any settings in httpd.conf that would allow this.

[Phpwiki-talk] Olivia Sing

[Olivia <ol...@ao...>]

<HTML>
<HEAD>
<TITLE>Latina Ecstasy</TITLE>
<META HTTP-EQUIV="" CONTENT="text/html; charset=iso-8859-1">
</HEAD>
<BODY BGCOLOR=#FFFFFF background="http://mipagina.cantv.net/sexo69/latina/images/bg.jpg" leftmargin="0" topmargin="0">
<!-- ImageReady Slices (latinaecstasy_800_600_1.jpg) -->
<TABLE WIDTH=800 BORDER=0 CELLPADDING=0 CELLSPACING=0 align="center">
  <TR> 
    <TD> <a href="http://stats.allliquid.com/regclick.html?promo=4527&code=LE&section=&type=I&alter=&t=,"><IMG SRC="http://mipagina.cantv.net/sexo69/latina/images/spacer.gif" WIDTH=125 HEIGHT=1 border="0"></a></TD>
    <TD> <a href="http://stats.allliquid.com/regclick.html?promo=4527&code=LE&section=&type=I&alter=&t=,"><IMG SRC="http://mipagina.cantv.net/sexo69/latina/images/spacer.gif" WIDTH=75 HEIGHT=1 border="0"></a></TD>
    <TD> <a href="http://stats.allliquid.com/regclick.html?promo=4527&code=LE&section=&type=I&alter=&t=,"><IMG SRC="http://mipagina.cantv.net/sexo69/latina/images/spacer.gif" WIDTH=200 HEIGHT=1 border="0"></a></TD>
    <TD> <a href="http://stats.allliquid.com/regclick.html?promo=4527&code=LE&section=&type=I&alter=&t=,"><IMG SRC="http://mipagina.cantv.net/sexo69/latina/images/spacer.gif" WIDTH=31 HEIGHT=1 border="0"></a></TD>
    <TD> <a href="http://stats.allliquid.com/regclick.html?promo=4527&code=LE&section=&type=I&alter=&t=,"><IMG SRC="http://mipagina.cantv.net/sexo69/latina/images/spacer.gif" WIDTH=58 HEIGHT=1 border="0"></a></TD>
    <TD> <a href="http://stats.allliquid.com/regclick.html?promo=4527&code=LE&section=&type=I&alter=&t=,"><IMG SRC="http://mipagina.cantv.net/sexo69/latina/images/spacer.gif" WIDTH=111 HEIGHT=1 border="0"></a></TD>
    <TD> <a href="http://stats.allliquid.com/regclick.html?promo=4527&code=LE&section=&type=I&alter=&t=,"><IMG SRC="http://mipagina.cantv.net/sexo69/latina/images/spacer.gif" WIDTH=102 HEIGHT=1 border="0"></a></TD>
    <TD> <a href="http://stats.allliquid.com/regclick.html?promo=4527&code=LE&section=&type=I&alter=&t=,"><IMG SRC="http://mipagina.cantv.net/sexo69/latina/images/spacer.gif" WIDTH=98 HEIGHT=1 border="0"></a></TD>
    <TD></TD>
  </TR>
  <TR> 
    <TD COLSPAN=2> <a href="http://stats.allliquid.com/regclick.html?promo=4527&code=LE&section=&type=I&alter=&t=,"><IMG SRC="http://mipagina.cantv.net/sexo69/latina/images/latinaecstasy_800_600_1_01.jpg" WIDTH=200 HEIGHT=150 border="0"></a></TD>
    <TD> <a href="http://stats.allliquid.com/regclick.html?promo=4527&code=LE&section=&type=I&alter=&t=,"><IMG SRC="http://mipagina.cantv.net/sexo69/latina/images/latinaecstasy_800_600_1_02.jpg" WIDTH=200 HEIGHT=150 border="0"></a></TD>
    <TD COLSPAN=3> <a href="http://stats.allliquid.com/regclick.html?promo=4527&code=LE&section=&type=I&alter=&t=,"><IMG SRC="http://mipagina.cantv.net/sexo69/latina/images/latinaecstasy_800_600_1_03.jpg" WIDTH=200 HEIGHT=150 border="0"></a></TD>
    <TD COLSPAN=2> <a href="http://stats.allliquid.com/regclick.html?promo=4527&code=LE&section=&type=I&alter=&t=,"><IMG SRC="http://mipagina.cantv.net/sexo69/latina/images/latinaecstasy_800_600_1_04.jpg" WIDTH=200 HEIGHT=150 border="0"></a></TD>
    <TD> <IMG SRC="http://mipagina.cantv.net/sexo69/latina/images/spacer.gif" WIDTH=1 HEIGHT=150></TD>
  </TR>
  <TR> 
    <TD COLSPAN=2> <a href="http://stats.allliquid.com/regclick.html?promo=4527&code=LE&section=&type=I&alter=&t=,"><IMG SRC="http://mipagina.cantv.net/sexo69/latina/images/latinaecstasy_800_600_1_05.jpg" WIDTH=200 HEIGHT=150 border="0"></a></TD>
    <TD> <a href="http://stats.allliquid.com/regclick.html?promo=4527&code=LE&section=&type=I&alter=&t=,"><IMG SRC="http://mipagina.cantv.net/sexo69/latina/images/latinaecstasy_800_600_1_06.jpg" WIDTH=200 HEIGHT=150 border="0"></a></TD>
    <TD COLSPAN=3> <a href="http://stats.allliquid.com/regclick.html?promo=4527&code=LE&section=&type=I&alter=&t=,"><IMG SRC="http://mipagina.cantv.net/sexo69/latina/images/latinaecstasy_800_600_1_07.jpg" WIDTH=200 HEIGHT=150 border="0"></a></TD>
    <TD COLSPAN=2> <a href="http://stats.allliquid.com/regclick.html?promo=4527&code=LE&section=&type=I&alter=&t=,"><IMG SRC="http://mipagina.cantv.net/sexo69/latina/images/latinaecstasy_800_600_1_08.jpg" WIDTH=200 HEIGHT=150 border="0"></a></TD>
    <TD> <IMG SRC="http://mipagina.cantv.net/sexo69/latina/images/spacer.gif" WIDTH=1 HEIGHT=150></TD>
  </TR>
  <TR> 
    <TD COLSPAN=2 ROWSPAN=2> <a href="http://stats.allliquid.com/regclick.html?promo=4527&code=LE&section=&type=I&alter=&t=,"><IMG SRC="http://mipagina.cantv.net/sexo69/latina/images/latinaecstasy_800_600_1_09.jpg" WIDTH=200 HEIGHT=137 border="0"></a></TD>
    <TD ROWSPAN=2> <a href="http://stats.allliquid.com/regclick.html?promo=4527&code=LE&section=&type=I&alter=&t=,"><IMG SRC="http://mipagina.cantv.net/sexo69/latina/images/latinaecstasy_800_600_1_10.jpg" WIDTH=200 HEIGHT=137 border="0"></a></TD>
    <TD COLSPAN=3> <a href="http://stats.allliquid.com/regclick.html?promo=4527&code=LE&section=&type=I&alter=&t=,"><IMG SRC="http://mipagina.cantv.net/sexo69/latina/images/latinaecstasy_800_600_1_11.jpg" WIDTH=200 HEIGHT=102 border="0"></a></TD>
    <TD COLSPAN=2> <a href="http://stats.allliquid.com/regclick.html?promo=4527&code=LE&section=&type=I&alter=&t=,"><IMG SRC="http://mipagina.cantv.net/sexo69/latina/images/latinaecstasy_800_600_1_12.jpg" WIDTH=200 HEIGHT=102 border="0"></a></TD>
    <TD> <IMG SRC="http://mipagina.cantv.net/sexo69/latina/images/spacer.gif" WIDTH=1 HEIGHT=102></TD>
  </TR>
  <TR> 
    <TD COLSPAN=2> <a href="http://stats.allliquid.com/regclick.html?promo=4527&code=LE&section=&type=I&alter=&t=,"><IMG SRC="http://mipagina.cantv.net/sexo69/latina/images/latinaecstasy_800_600_1_13.jpg" WIDTH=89 HEIGHT=35 border="0"></a></TD>
    <TD COLSPAN=2 ROWSPAN=2> <a href="http://stats.allliquid.com/regclick.html?promo=4527&code=LE&section=&type=I&alter=&t=,"><IMG SRC="http://mipagina.cantv.net/sexo69/latina/images/latinaecstasy_800_600_1_14.jpg" WIDTH=213 HEIGHT=48 border="0"></a></TD>
    <TD ROWSPAN=2> <a href="http://stats.allliquid.com/regclick.html?promo=4527&code=LE&section=&type=I&alter=&t=,"><IMG SRC="http://mipagina.cantv.net/sexo69/latina/images/latinaecstasy_800_600_1_15.jpg" WIDTH=98 HEIGHT=48 border="0"></a></TD>
    <TD> <IMG SRC="http://mipagina.cantv.net/sexo69/latina/images/spacer.gif" WIDTH=1 HEIGHT=35></TD>
  </TR>
  <TR> 
    <TD> <a href="http://stats.allliquid.com/regclick.html?promo=4527&code=LE&section=&type=I&alter=&t=,"><IMG SRC="http://mipagina.cantv.net/sexo69/latina/images/latinaecstasy_800_600_1_16.jpg" WIDTH=125 HEIGHT=13 border="0"></a></TD>
    <TD COLSPAN=3 ROWSPAN=2> <a href="http://stats.allliquid.com/regclick.html?promo=4527&code=LE&section=&type=I&alter=&t=,"><IMG SRC="http://mipagina.cantv.net/sexo69/latina/images/latinaecstasy_800_600_1_17.jpg" WIDTH=306 HEIGHT=33 border="0"></a></TD>
    <TD> <a href="http://stats.allliquid.com/regclick.html?promo=4527&code=LE&section=&type=I&alter=&t=,"><IMG SRC="http://mipagina.cantv.net/sexo69/latina/images/latinaecstasy_800_600_1_18.jpg" WIDTH=58 HEIGHT=13 border="0"></a></TD>
    <TD> <IMG SRC="http://mipagina.cantv.net/sexo69/latina/images/spacer.gif" WIDTH=1 HEIGHT=13></TD>
  </TR>
  <TR> 
    <TD ROWSPAN=2> <a href="http://stats.allliquid.com/regclick.html?promo=4527&code=LE&section=&type=I&alter=&t=,"><IMG SRC="http://mipagina.cantv.net/sexo69/latina/images/latinaecstasy_800_600_1_19.jpg" WIDTH=125 HEIGHT=29 border="0"></a></TD>
    <TD COLSPAN=2 ROWSPAN=2> <a href="http://stats.allliquid.com/regclick.html?promo=4527&code=LE&section=&type=I&alter=&t=,"><IMG SRC="http://mipagina.cantv.net/sexo69/latina/images/latinaecstasy_800_600_1_20.jpg" WIDTH=169 HEIGHT=29 border="0"></a></TD>
    <TD COLSPAN=2 ROWSPAN=2> <a href="http://stats.allliquid.com/regclick.html?promo=4527&code=LE&section=&type=I&alter=&t=,"><IMG SRC="http://mipagina.cantv.net/sexo69/latina/images/latinaecstasy_800_600_1_21.jpg" WIDTH=200 HEIGHT=29 border="0"></a></TD>
    <TD> <IMG SRC="http://mipagina.cantv.net/sexo69/latina/images/spacer.gif" WIDTH=1 HEIGHT=20></TD>
  </TR>
  <TR> 
    <TD> <a href="http://stats.allliquid.com/regclick.html?promo=4527&code=LE&section=&type=I&alter=&t=,"><IMG SRC="http://mipagina.cantv.net/sexo69/latina/images/latinaecstasy_800_600_1_22.jpg" WIDTH=75 HEIGHT=9 border="0"></a></TD>
    <TD> <a href="http://stats.allliquid.com/regclick.html?promo=4527&code=LE&section=&type=I&alter=&t=,"><IMG SRC="http://mipagina.cantv.net/sexo69/latina/images/latinaecstasy_800_600_1_23.jpg" WIDTH=200 HEIGHT=9 border="0"></a></TD>
    <TD> <a href="http://stats.allliquid.com/regclick.html?promo=4527&code=LE&section=&type=I&alter=&t=,"><IMG SRC="http://mipagina.cantv.net/sexo69/latina/images/latinaecstasy_800_600_1_24.jpg" WIDTH=31 HEIGHT=9 border="0"></a></TD>
    <TD> <IMG SRC="http://mipagina.cantv.net/sexo69/latina/images/spacer.gif" WIDTH=1 HEIGHT=9></TD>
  </TR>
  <TR> 
    <TD COLSPAN=8><a href="http://stats.allliquid.com/regclick.html?promo=4527&code=LE&section=&type=I&alter=&t=,"></a> 
    </TD>
    <TD> <IMG SRC="http://mipagina.cantv.net/sexo69/latina/images/spacer.gif" WIDTH=1 HEIGHT=121></TD>
  </TR>
</TABLE>
<!-- End ImageReady Slices --><div align="center">
<table width="76%" border="0" align="center" cellpadding="0" cellspacing="0">
    <tr>
      <td><font size="1" face="Verdana, Arial, Helvetica, sans-serif">
        <div align="center">
          <p><font color="#666666" size="2">This mail is only for adult people 
            if you are under age please ignore this mail, and apologize us.</font></p>
          
        <p><font color="#666666">THIS MESSAGE IS BEING SENT IN COMPLIANCE WITH 
          PENDING EMAIL BILLS &amp; LAWS:<br>
          SECTION 301. PER SECTION, PARAGRAPH (a) (2) (c) of S. 1618. This message 
          is<br>
          not intended for residents in the State of WA, NV, CA &amp; VA. Screening 
          of<br>
          addresses has been done to the best of our technical ability. We honor 
          all<br>
          removal requests. </font></p>
      </div>
      </font> <p align="center"><font color="#666666" size="1" face="Verdana, Arial, Helvetica, sans-serif">You 
        are currently subscribed to receive our special emails. to unscribe,<br>
        please reply with Remove on your subject line.</font></p>
        </td>
    </tr>
  </table>
</BODY>
</HTML>

Re: [Phpwiki-talk] setButtonSeparator and images

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

Hi Aphid,

Try this:

     $Theme->setButtonSeparator(HTML::img(array('alt'=>"*", 
'src'=>"/bull.png")));

or

     $Theme->setButtonSeparator(HTML::raw('<img 
src="http://www.aphid.org/bull.png"'));

Carsten


On Sunday, February 16, 2003, at 09:31  pm, aphid wrote:

> On Sunday, February 16, 2003, at 06:21  PM, aphid wrote:
>
>> hey.. i'd like to use an image as the button separator, but if I 
>> change the function to read
>>
>> $Theme->setButtonSeparator("\n <img 
>> src='http://www.aphid.org/bull.png' ");
>>
>> it's coming through in the page source as
>
> clarification, it's coming through in the browser as literally '<img 
> src='http://www.aphid.org/bull.png>' (I forgot the closing bracket 
> above but having fixed it in my code has made no difference)
>
> cheers
> a