phpwiki-talk

[Phpwiki-talk] mysql config.ini something wrong

[peter p. <pe...@pe...>]

Hello!

I have mysql installed, but something wrong, can anyone help?

Fatal error: Cannot instantiate non-existent class: wikidb_dbt in
/Library/Tenon/WebServer/WebSites/www.apfel.at/phpwiki/lib/WikiDB.php on
line 100

What es the problem here?

Regards

Peter


;======================================================================
; Part Two: Database Selection
;======================================================================

; Select the database type:
;
;       SQL:   access one of several SQL databases using the PEAR DB
library.
;       ADODB: uses the ADODB library for data access.
;       dba: use one of the standard UNIX dbm libraries.
;       file: use a flat file database.
;       cvs: use a CVS server to store everything.
DATABASE_TYPE = dbt
   
; prefix for filenames or table names
;
; Currently you MUST EDIT THE SQL file too (in the schemas/
; directory because we aren't doing on the fly sql generation
; during the installation.
; Note: This prefix is NOT prepended to the default DBAUTH_
;       tables user, pref and member!
;DATABASE_PREFIX = phpwiki_

; For SQL based backends, specify the database as a DSN (Data Source Name),
; a kind of URL for databases.
;
; The most general form of a DSN looks like:
;
;       dbtype(dbsyntax)://username:password@protocol+hostspec/database
;
; For a MySQL database, the following should work:
;
mysql://usert:pass@host/databasename
;
; To connect over a unix socket, use something like
;
;       mysql://user:password@unix(/path/to/socket)/databasename
;
; Valid values for dbtype are mysql, pgsql, or sqlite.
;
;DATABASE_DSN = "mysql://guest@unix(/var/lib/mysql/mysql.sock)/test"

; A table to store session information.  Only needed by SQL backends.
;
; A word of warning - any prefix defined above will be prepended to whatever
; is given here.
DATABASE_SESSION_TABLE = session

; For the file and dba backends, this specifies where the data files will be
; located.  Ensure that the user that the webserver runs as has write access
; to this directory.
;
; WARNING: leaving this as the default of '/tmp' will almost guarantee that
; you'll lose your wiki data at some stage.
DATABASE_DIRECTORY = /tmp

; For the dba backend, this defines which DBA variant you wish to use.
;       gdbm - commonly available
;       db2 - Berkeley DB v2; not supported by modern versions of PHP
;       db3 - Berkeley DB v3; as per db2. The best on Windows
;       db4 - Berkeley DB v4; current version, however PHP has some issues
;               with it's db4 support.
;       dbm - Older dba handler; suffers from limits on the size of data
;               items
DATABASE_DBA_HANDLER = gdbm

; How long will the system wait for a database operation to complete?
; Specified in seconds.
DATABASE_TIMEOUT = 20

; The login code now uses PHP's session support. Usually, the default
; configuration of PHP is to store the session state information in
; /tmp. That probably will work fine, but fails e.g. on clustered
; servers where each server has their own distinct /tmp (this is the
; case on SourceForge's project web server.) You can specify an
; alternate directory in which to store state information like so
; (whatever user your httpd runs as must have read/write permission
; in this directory):
;SESSION_SAVE_PATH = some_other_directory

[Phpwiki-talk] Re: ldap patch...

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

John Cole schrieb:
> Reini,
>   Here is a patch for WikiUserNew that removes the partial request recieved
> errors.  Basically, I just moved the options before the bind call.  I also
> copied the options routine from the checkPass function to the userExits
> function, because it looked like you had changed one and not the other.

Your fix is appreciated and in. Of course you are right.

>   Now, I don't think this is related to the LDAP code, but phpWiki is
> crashing php/apache as soon as you log in now.  Logging in as the admin user
> works fine, but if you log in as a normal user (ldap on my system) I crash
> apache and get 'document contains no data'.  If I comment out the
> $this->_level = WIKIAUTH_USER; I'm ok, but unauthenticated, so it really
> looks like I'm exiting the LDAP code ok, but I don't know where to start
> looking from there ;-)
> 
>   I had this code working last week ok, but the current version crashes.
> Any suggestions?

hmm, not yet.
But I compiled now slapd by my own, and will soon be able to test it again.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

[Phpwiki-talk] ldap patch...

[John C. <joh...@ua...>]

Reini,
  Here is a patch for WikiUserNew that removes the partial request recieved
errors.  Basically, I just moved the options before the bind call.  I also
copied the options routine from the checkPass function to the userExits
function, because it looked like you had changed one and not the other.

  Now, I don't think this is related to the LDAP code, but phpWiki is
crashing php/apache as soon as you log in now.  Logging in as the admin user
works fine, but if you log in as a normal user (ldap on my system) I crash
apache and get 'document contains no data'.  If I comment out the
$this->_level = WIKIAUTH_USER; I'm ok, but unauthenticated, so it really
looks like I'm exiting the LDAP code ok, but I don't know where to start
looking from there ;-)

  I had this code working last week ok, but the current version crashes.
Any suggestions?

John Cole



Index: lib/WikiUserNew.php
===================================================================
RCS file: /cvsroot/phpwiki/phpwiki/lib/WikiUserNew.php,v
retrieving revision 1.86
diff -u -r1.86 WikiUserNew.php
--- lib/WikiUserNew.php	3 Jun 2004 18:06:29 -0000	1.86
+++ lib/WikiUserNew.php	4 Jun 2004 15:18:05 -0000
@@ -1949,6 +1949,13 @@
         }
 
         if ($ldap = ldap_connect(LDAP_AUTH_HOST)) { // must be a valid LDAP
server!
+            if (!empty($LDAP_SET_OPTION)) {
+                foreach ($LDAP_SET_OPTION as $key => $value) {
+                    if (is_string($key) and defined($key))
+                        $key = constant($key);
+                    ldap_set_option($ldap,$key,$value);
+                }
+            }
             if (defined('LDAP_AUTH_USER'))
                 if (defined('LDAP_AUTH_PASSWORD'))
                     // Windows Active Directory Server is strict
@@ -1957,13 +1964,6 @@
                     $r = @ldap_bind($ldap,LDAP_AUTH_USER); 
             else
                 $r = @ldap_bind($ldap); // this is an anonymous bind
-            if (!empty($LDAP_SET_OPTION)) {
-                foreach ($LDAP_SET_OPTION as $key => $value) {
-                    if (is_string($key) and defined($key))
-                        $key = constant($key);
-                    ldap_set_option($ldap,$key,$value);
-                }
-            }
             // Need to set the right root search information. see
../index.php
             $st_search = defined('LDAP_SEARCH_FIELD') 
                 ? LDAP_SEARCH_FIELD."=$userid"
@@ -2000,6 +2000,14 @@
             return WIKIAUTH_FORBIDDEN;
         }
         if ($ldap = ldap_connect(LDAP_AUTH_HOST)) { // must be a valid LDAP
server!
+            if (!empty($LDAP_SET_OPTION)) {
+                foreach ($LDAP_SET_OPTION as $key => $value) {
+                    if (is_string($key) and defined($key))
+                        $key = constant($key);
+                    ldap_set_option($ldap,$key,$value);
+                }
+            }
+
             if (defined('LDAP_AUTH_USER'))
                 if (defined('LDAP_AUTH_PASSWORD'))
                     // Windows Active Directory Server is strict
@@ -2008,11 +2016,7 @@
                     $r = @ldap_bind($ldap,LDAP_AUTH_USER); 
             else
                 $r = @ldap_bind($ldap); // this is an anonymous bind
-            if (!empty($LDAP_SET_OPTION)) {
-                foreach ($LDAP_SET_OPTION as $key => $value) {
-                    ldap_set_option($ldap,$key,$value);
-                }
-            }
+
             // Need to set the right root search information. see
../index.php
             $st_search = defined('LDAP_SEARCH_FIELD') 
                 ? LDAP_SEARCH_FIELD."=$userid"

Re: [Phpwiki-talk] Warning: LDAP security problem

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

Reini Urban schrieb:
> In this patch I only restricted '*'.
> 
> For the future we'll have to restrict the allowed username characters 
> for PassUsers, because I don't want to escape every possible special 
> character for every possible auth backend and platform.
> 
> I suggest to allow only
>   $userid =~ /^[\w.-@]\$?$/ and strlen($userid) < 32

I forced now this username in current CVS:
   $userid =~ /^[\w\.\-@]+$/ and strlen($userid) < 32
trailing "$" not.

> which allows all alphanumeric chars, all localized word chars,
> plus ".","-","@" and a trailing "$".
> [a-zA-Z0-9_-.] + [äüöèéáÀ...]
> 
> Should we ould be more strict any allow only POSIX'ly correct usernames? 
> There is not such an exact definition, but ...
> For IMAP, POP3 and FileAuth for example.
> LDAP dislikes * ! ( ) & \
> File dislikes also : and names longer than 31 chars.
> 
> I'm not sure about dots (i.e. in email). Certain cmdline unix tools bark 
> on dots.
> 
> adduser(8)
>   It is recommended that login names contain only lowercase charac-
>   ters and digits.  They may also contain uppercase characters,
>   non-leading hyphens, periods, and a trailing '$'.  Login names
>   may not be longer than 31 characters (see BUGS section of
>   setlogin(2)).
> 
> What about Samba, POSIX ACL's?
> I have to check http://www.wlug.org.nz/SambaNotes AND 
> http://www.wlug.org.nz/LDAPAuthentication
> 
> I also learned that with HttpAuth usernames are NOT case-sensitive.
> (not yet checked if it affects us)

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

[Phpwiki-talk] Warning: LDAP security problem

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

If you use LDAP Auth, please see attach following patch
https://sourceforge.net/tracker/index.php?func=detail&aid=966410&group_id=6121&atid=306121

It is already in CVS and will be in the upcoming 1.3.11 release.

Simple fix for a LDAP security problem, gaining unauthorized access
as any user, supplying '*' as username, iterating over all users
until the given password matches.

This type of security issue, called "LDAP injection," is not
currently well known.  The seminal paper on the topic is at:
http://www.spidynamics.com/whitepapers/LDAPinjection.pdf

Detected by Steve Christey, MITRE

----------------------------------

In this patch I only restricted '*'.

For the future we'll have to restrict the allowed username characters 
for PassUsers, because I don't want to escape every possible special 
character for every possible auth backend and platform.

I suggest to allow only
   $userid =~ /^[\w.-@]\$?$/ and strlen($userid) < 32
which allows all alphanumeric chars, all localized word chars,
plus ".","-","@" and a trailing "$".
[a-zA-Z0-9_-.] + [äüöèéáÀ...]

Should we ould be more strict any allow only POSIX'ly correct usernames? 
There is not such an exact definition, but ...
For IMAP, POP3 and FileAuth for example.
LDAP dislikes * ! ( ) & \
File dislikes also : and names longer than 31 chars.

I'm not sure about dots (i.e. in email). Certain cmdline unix tools bark 
on dots.

adduser(8)
   It is recommended that login names contain only lowercase charac-
   ters and digits.  They may also contain uppercase characters,
   non-leading hyphens, periods, and a trailing '$'.  Login names
   may not be longer than 31 characters (see BUGS section of
   setlogin(2)).

What about Samba, POSIX ACL's?
I have to check http://www.wlug.org.nz/SambaNotes AND 
http://www.wlug.org.nz/LDAPAuthentication

I also learned that with HttpAuth usernames are NOT case-sensitive.
(not yet checked if it affects us)
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: [Phpwiki-talk] More patches

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

Dan Frankowski schrieb:
> I don't remember which files changed, so I tar-ed up the whole thing again.
> See attached unit.tgz.

Such a lot of work todo! Still fighting with sidebar and edit_toolbar.

I'm also trying to add/change most of your wikilens-src.tgz 
(/lib/wikilens/...) stuff.

And I have a lot of questions, suggestions, but not today.
Tomorrow will be a good fresh day. and maybe anoncvs will be fixed by 
tomorrow.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: [Phpwiki-talk] pserver access to cvs on sourceforge...

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

John Cole schrieb:
> Does anyone know when pserver access to sourceforge will be restored for
> phpwiki?  I've been looking at Reini's changes and I'd like to get them a
> whirl.
> 
> The sf.net status page doesn't have much info on the subject, except that
> cvs pserver access is messed up for certain projects (among them the 'p'
> projects).

They sent out a new site status update mail yesterday, and the "full CVS 
restauration" was said to happen in the next 5 months.

Currently they are switching it to normal access for anonymous users 
without the 24hr lag between developer commit and anoncvs.
(nfs mounted probably, not rsync'ed as now)

shoud be at the Site Status update page.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

[Phpwiki-talk] More patches

[Dan F. <dfr...@cs...>]

Fix a couple sorting bugs, more unit tests.

Dan

===================================

More detail to an error message:

===================================

diff -b -u -r1.5 -r1.6
--- Theme.php   28 May 2004 20:15:56 -0000      1.5
+++ Theme.php   3 Jun 2004 16:40:04 -0000       1.6
@@ -379,7 +379,7 @@
             return $this->_default_theme->_findFile($file, $missing_okay);
         }
         else if (!$missing_okay) {
-            trigger_error("$file: not found", E_USER_NOTICE);
+            trigger_error("$file: not found, looked in $this->_theme", 
E_USER_NOTICE);
         }
         return false;
     }

===================================

Fix sorting by column name (e.g., "+pagename").
Fix sorting by pagename if page doesn't exist.

===================================

diff -b -u -r1.15 -r1.16
--- PageList.php        28 May 2004 16:07:11 -0000      1.15
+++ PageList.php        3 Jun 2004 16:43:45 -0000       1.16
@@ -1,4 +1,4 @@
-<?php rcs_id('$Id: PageList.php,v 1.15 2004/05/28 16:07:11 dfrankow Exp 
$');
+<?php rcs_id('$Id: PageList.php,v 1.16 2004/06/03 16:43:45 dfrankow Exp 
$');

 /**
  * List a number of pagenames, optionally as table with various columns.
@@ -479,16 +479,28 @@
             return WikiLink($page_handle, 'unknown');
     }

+    function _getPageNameFromCol($colval) {
+        $name = '';
+        if (is_a($colval, 'WikiDB_Page')) {
+            $name = $colval->getName();
+        }
+        else if (is_a($colval, 'XmlContent')) {
+            // Gotta sort by something
+            $name = $colval->asString();
+        }
+        else {
+            // colvala was of unexpected type
+            assert( false );
+        }
+        return $name;
+    }
+
     /**
      * Compare two pages for sorting.  See _PageList_Column::_compare.
      **/
     function _compare($colvala, $colvalb) {
-        assert($colvala, 'WikiDB_Page');
-        $contenta = $colvala->getContent();
-        $namea = $contenta[0];
-        assert($colvalb, 'WikiDB_Page');
-        $contentb = $colvalb->getContent();
-        $nameb = $contentb[0];
+        $namea = $this->_getPageNameFromCol($colvala);
+        $nameb = $this->_getPageNameFromCol($colvalb);
         return strcmp($namea, $nameb);
     }
 };
@@ -921,7 +933,7 @@
         if ($column == 'rating' and 
!$GLOBALS['request']->_user->isSignedIn())
             return false;

-        $this->addColumnObject($this->_types[$column]);
+        $this->addColumnObject($this->_types[$column], $column);

         return true;
     }
@@ -930,15 +942,19 @@
      * Add a column to this PageList, given a column object.
      *
      * @param $col object   An object derived from _PageList_Column.
+     * @param $typename string   The name of the column type, e.g. 
'pagename'
+     *                           If this is given, you can refer to the 
column
+     *                           to sort by name, e.g., "+pagename".  
Otherwise
+     *                           you must use column # (starting from 0).
      **/
-    function addColumnObject($col) {
+    function addColumnObject($col, $typename = false) {
         $heading = $col->getHeading();
         if (!empty($heading))
             $col->setHeading($heading);

         $this->_columns[] = $col;
         end($this->_columns);
-        $this->_columnsMap[$heading] = key($this->_columns);
+        $this->_columnsMap[$typename] = key($this->_columns);
     }

     /**

===================================

More unit tests changes. Here are things I remember:

Print a simple traceback for both broken assert() and error callback.
Get ALL errors reported, e.g. "function not found", parse errors, etc.

Add a real test for PageList sorting


===================================

I don't remember which files changed, so I tar-ed up the whole thing again.
See attached unit.tgz.

Re: [Phpwiki-talk] pserver access to cvs on sourceforge...

[Dan F. <dfr...@cs...>]

John Cole wrote:

>Does anyone know when pserver access to sourceforge will be restored for
>phpwiki?  I've been looking at Reini's changes and I'd like to get them a
>whirl.
>  
>

Me too. I have no info.

Dan

[Phpwiki-talk] pserver access to cvs on sourceforge...

[John C. <joh...@ua...>]

Does anyone know when pserver access to sourceforge will be restored for
phpwiki?  I've been looking at Reini's changes and I'd like to get them a
whirl.

The sf.net status page doesn't have much info on the subject, except that
cvs pserver access is messed up for certain projects (among them the 'p'
projects).

Thanks,

John Cole

Re: [Phpwiki-talk] assert ...

[Frederik De B. <fre...@pa...>]

I forgot to CC the list as well, so here's my description of "assert":

> I might have the wrong idea, but why are there numerous 'assert' calls 
> in the code, in things like function getRevisionBefore($version) in 
> WikiDB.php?

I'm quoting from the "Programming With Assertions" introduction here:

An assertion is a statement that enables you to test your assumptions 
about your program. For example, if you write a method that calculates 
the speed of a particle, you might assert that the calculated speed is 
less than the speed of light.

Each assertion contains a boolean expression that you believe will be 
true when the assertion executes. If it is not true, the system will 
throw an error. By verifying that the boolean expression is indeed 
true, the assertion confirms your assumptions about the behavior of 
your program, increasing your confidence that the program is free of 
errors.

Experience has shown that writing assertions while programming is one 
of the quickest and most effective ways to detect and correct bugs. As 
an added benefit, assertions serve to document the inner workings of 
your program, enhancing maintainability.

 > All that happens in the wiki is an unsightly error message (and no 
page template, etc) when it's triggered.

Assertions should look like big red warning signs to remind the 
programmer that something is very wrong. And again, they're not 
something the client will ever see.

A good read is "bug detection with PHP assertions". This article also 
mentions how to turn off assertions for production code, so that the 
user doesn't get to see the result of an assertion. Even better, the 
evaluation of assertions can be turned off completely, improving the 
speed of your application (although marginally).
http://www.sitepoint.com/article.php/1008

Frederik

P.S. The mentioned article, Programming with Assertions, can be found 
here:
http://java.sun.com/j2se/1.4.2/docs/guide/lang/assert.html

Re: [Phpwiki-talk] New Ploticus plugin

[Jim C. <ji...@in...>]

On Jun 3, 2004, at 9:13 PM, Reini Urban wrote:
> Malcolm Ross Kinsella Ryan schrieb:
>> Should we perhaps separate the development of plugins from the main 
>> wiki
>> engine in CVS?
>
> Why?
>
Other projects have done it, which isn't exactly a recommendation, but 
just an acknowledgement of the thinking.

The core phpwiki is *capable* of running plugins, and indeed needs to 
have a couple of nice examples to encourage people to get writing them. 
But is a plugin author necessarily "good enough" to be a phpwiki 
contributor? Not necessarily ... so perhaps they should have a 
different CVS tree?

Also, some of the more interesting plugins (like VisualWiki) have 
external dependancies on things like graphviz software, that the core 
phpwiki does not rely on at all.

If the plugins and wiki are packaged together, the packager either has 
to include (a reference to) all the external dependancies of the 
plugins (even if the end user never uses them), or has to allow 
"possibly-broken" plugins to be installed.

So we immediately have a good argument to separate out at least the 
external-dependancy plugins.
I think it's reasonable to consider separating out all the plugins - 
they are not core functionality of phpwiki, they are not needed in 
order for it to work fully, they are optional code.

You could still release a phpwiki+plugins package, as well as a 
phpwiki-without-plugins package. More choice for the system 
administrator.

-jim

Re: [Phpwiki-talk] Maintaining a shared bibtex file

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

Malcolm Ross Kinsella Ryan schrieb:
> I am using PhpWiki as a tool for a collaborative research project. Being
> CS researchers, we are interested in tracking references to academic papers,
> and the tool of choice is Bibtex (part of the LaTeX package).
> 
> I'd really like to find some way that we could include a Bibtex database
> as part of our wiki, so that we can collaboratively construct the database
> and refer to papers in it. Does anyone have a good idea how we might go
> about this? Are there any existing tools (wiki or non-wiki) that you'd
> recommend?
> 
> In general, suppose we want to keep a structured database of information
> as part of a wiki. Has anyone found a good way of doing this?

I'm working on this,
generating pages on the fly from sql queries with a phpwiki template, 
and supporting most of phpwiki machinery behind.

http://phpwiki.sourceforge.net/phpwiki/SqlWikiDbHookPlugin

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

Re: [Phpwiki-talk] New Ploticus plugin

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

Malcolm Ross Kinsella Ryan schrieb:
> On Wed, Jun 02, 2004 at 09:51:50PM +0200, Reini Urban wrote:
>>I commited now a new Ploticus plugin.
> 
> Should we perhaps separate the development of plugins from the main wiki
> engine in CVS?

Why?


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

[Phpwiki-talk] Maintaining a shared bibtex file

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

I am using PhpWiki as a tool for a collaborative research project. Being
CS researchers, we are interested in tracking references to academic papers,
and the tool of choice is Bibtex (part of the LaTeX package).

I'd really like to find some way that we could include a Bibtex database
as part of our wiki, so that we can collaboratively construct the database
and refer to papers in it. Does anyone have a good idea how we might go
about this? Are there any existing tools (wiki or non-wiki) that you'd
recommend?

In general, suppose we want to keep a structured database of information
as part of a wiki. Has anyone found a good way of doing this?

Malcolm

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

                         "Blessed are the peacemakers,
                    for they will be called children of God."    -- Matt 5:9

Re: [Phpwiki-talk] New Ploticus plugin

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

On Wed, Jun 02, 2004 at 09:51:50PM +0200, Reini Urban wrote:
> I commited now a new Ploticus plugin.

Should we perhaps separate the development of plugins from the main wiki
engine in CVS?

Malcolm

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

                           "Blessed are the merciful,
                          for they will be shown mercy."         -- Matt 5:7

Re: [Phpwiki-talk] feature request...

[Franois G. <fra...@fr...>]

Le 1/06/04 17:01, =AB=A0John Cole=A0=BB <joh...@ua...> a =E9crit=A0:

> Second, I have noticed a lot of word documents being shared on our wiki. =
 I
> feel that this somehow defeats the wikiness of our wiki ;-)  I'd like to
> have them convert the documents to wiki, but that is quite an undertaking=
.
> I found a html2wiki php script at http://www.cvsnt.org/striphtml.php
> <http://www.cvsnt.org/striphtml.php>  that Tony Hoyle (of CVSNT fame)
> modified.

There is a script under developement here :

http://publicooperation.com/tools/office2wiki.php

Re: [Phpwiki-talk] assert ...

[Jim C. <ji...@iN...>]

Reini Urban wrote:
> Dan Frankowski schrieb:
>> You didn't cc the list, so I do.
	Thanks Dan, you're right, I forgot to send to the list :-(

> Which phpwiki version? Thanks for the report.
	1.3.9
> 
> But I think found the error, which is fixed in current CVS.
> $backend->get_previous_version() returns false instead of 0, which hurts 
> getRevisionBefore().

	Excellent work, thanks for that :-)

-jim

[Phpwiki-talk] New Ploticus plugin

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

I commited now a new Ploticus plugin.

The Ploticus WikiPlugin passes all its arguments to the ploticus
binary and displays the result as PNG, GIF, EPS, SVG, SVGZ or SWF.
Ploticus is a free, GPL, non-interactive software package
for producing plots, charts, and graphics from data.

See http://ploticus.sourceforge.net/doc/welcome.html

Limitations:
- For windows you need either a gd library with GIF support or
   a ploticus with PNG support. This comes only with the cygwin
   built pl221win32cygmax.zip.
- We support only images supported by GD so far (PNG most likely).
   No EPS, PS, SVG, SVGZ or SWG support yet due to API limitations in
   ~WikiPluginCached. No technical problems, so you can expect it soon.

A PloticusSql plugin to use data from sql queries is planned also. 
Similar to SqlResult, just in graphic form.
For example to produce nice looking pagehit statistics or ratings 
statistics. I got this idea from mediawiki.

plugincache-config.php must be configured properly and the external 
ploticus binary must be installed and defined in the file.

The PloticusPlugin page will be setup tomorrow at the demo site.
I want to revive VisualWiki also then.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: [Phpwiki-talk] assert ...

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

Dan Frankowski schrieb:
> You didn't cc the list, so I do.
> Jim Cheetham wrote:
>> Thanks to both Dan and Frederik for confirming my thoughts about 
>> assert(), and expanding on them :-)
>>
>> With respect to turning these off in production, my question becomes :-
>>
>> Should phpwiki have active assert statements for production users? Can 
>> we turn them off with the equivalent of DEBUG = 0, or via .htaccess 
>> setting a php value?
> 
> Reini changed this in CVS so DEBUG=0 turns off assert()s.
> 
>> and
>>
>> Given that I've seen WikiDB getRevisionBefore($version) throw out an 
>> assert when submitting a page edit (on a dba=file wiki), does that 
>> indicate a problem that needs to be fixed, either in phpwiki or on my 
>> site?

Which phpwiki version? Thanks for the report.

But I think found the error, which is fixed in current CVS.
$backend->get_previous_version() returns false instead of 0, which hurts 
getRevisionBefore().

> Yes. Either in the code or in the assert.

For sure in phpwiki. asserts are so simple that they cannot be wrong.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: [Phpwiki-talk] feature request...

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

John Cole schrieb:
>>There us something much better around, called office2wiki or such. 
> 
> I found this and it does look good, but it also looks like they are going to
> write the next version in python :-)  This really would be a nice feature
> for corporate people who are absolutly stuck on word documents.  

Export to html and then use our new Html2Wiki converter (HtmlParser), 
which will be supported soon.
This will be a really good converter, and the only one.

The perl script I posted doesn't work yet good enough.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: [Phpwiki-talk] assert ...

[Dan F. <dfr...@cs...>]

You didn't cc the list, so I do.

Jim Cheetham wrote:

> Thanks to both Dan and Frederik for confirming my thoughts about 
> assert(), and expanding on them :-)
>
> With respect to turning these off in production, my question becomes :-
>
> Should phpwiki have active assert statements for production users? Can 
> we turn them off with the equivalent of DEBUG = 0, or via .htaccess 
> setting a php value?


Reini changed this in CVS so DEBUG=0 turns off assert()s.

> and
>
> Given that I've seen WikiDB getRevisionBefore($version) throw out an 
> assert when submitting a page edit (on a dba=file wiki), does that 
> indicate a problem that needs to be fixed, either in phpwiki or on my 
> site?


Yes. Either in the code or in the assert.

Dan

RE: [Phpwiki-talk] feature request...

[John C. <joh...@ua...>]

Alec,
  catdoc looks nice as does word2x, however most of the open source doc
converters look pretty long in the tooth ;-)  It seems that the comercial
converters are a lot better than the oss versions.

  The primary advantage of dealing with word documents is that you could
automatically save the images out to a place accessable to the webserver
(perhaps even give them a interwiki link ;-)

  I'm not sure how well these converters work with that, so it may be easier
to get a html2wiki converter like office2wiki working.  That also has the
advantage of being entirely in php.

  I've also found some php code that uses com to have word save as html,
which could then be fed to a html2wiki script, but that would only work on
windows systems :-)

John Cole

-----Original Message-----
From: Alec Thomas [mailto:li...@sw...]
Sent: Tuesday, June 01, 2004 10:21 AM
To: John Cole
Cc: php...@li...
Subject: Re: [Phpwiki-talk] feature request...


On Tue, Jun 01, 2004 at 10:01:12AM -0500, John Cole wrote:
> Second, I have noticed a lot of word documents being shared on our
> wiki.  I feel that this somehow defeats the wikiness of our wiki ;-)
> I'd like to have them convert the documents to wiki, but that is quite
> an undertaking.  I found a html2wiki php script at
> http://www.cvsnt.org/striphtml.php that Tony Hoyle (of CVSNT fame)
> modified.  This would be a nice plugin to have, as I could then tell
> people to convert their docs to html and use that plugin to convert
> the html to wiki.

Another alternative might be catdoc, along with some magic Wikification.

--
Evolution: Taking care of those too stupid to take care of themselves.

Re: [Phpwiki-talk] assert ...

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

Dan Frankowski schrieb:
> HOWEVER, you may not wish to see assert() output in your production 
> system. If that's true, you can turn them off. See the "assert.active" 
> setting of PHP. 

I added now the logic to assert only if DEBUG is non-false.

If you want to assert always (which is recommended) you have to put 
comments before the two lines in lib/ErrorManager.php:

if (DEBUG) assert_options (ASSERT_ACTIVE, 1);
else       assert_options (ASSERT_ACTIVE, 0);

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

Re: [Phpwiki-talk] assert ...

[Dan F. <dfr...@cs...>]

Jim Cheetham wrote:

> I might have the wrong idea, but why are there numerous 'assert' calls 
> in the code, in things like function getRevisionBefore($version) in 
> WikiDB.php?
>
> If I understand assert correctly, it throws an error if it's function 
> is not true ... ? All that happens in the wiki is an unsightly error 
> message (and no page template, etc) when it's triggered. I think this 
> one is triggered by (near)simultaneous edits, but they seem to work OK 
> when refreshing the page.
>
> If asserts are needed, can the user experience be improved somehow?



Jim,

assert()s are used to find programming errors. An assert() states what 
the programmer claims should be true for the code to run correctly. This 
is very useful, especially for large programs, programs written over 
time, and written by many different people. I highly encourage 
assert()s, even of "obvious" things (which turn out later not to be true!).

This is distinguished from an error condition (e.g, invalid user input, 
running out of disk space, etc.) that might happen even in a correctly 
functioning program, which should be handled by non-assert code (like if-s).

For more about PHP assert, see for example:

http://www.sitepoint.com/article/1008

HOWEVER, you may not wish to see assert() output in your production 
system. If that's true, you can turn them off. See the "assert.active" 
setting of PHP. For example:

http://www.sitepoint.com/article/bug-detection-php-assertions/3

Dan