[Phpwiki-talk] Fwd: RE: Trouble with phpwiki

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

----------  Forwarded Message  ----------
Subject: RE: Trouble with phpwiki
Date: Mon, 1 Jan 2001 13:02:08 -0800
From: "David LeBlanc" <wh...@oz...>
To: "Arno Hollosi" <aho...@in...>


Hi Arno;

My comments are intersperced below...

> -----Original Message-----
> From: Arno Hollosi [mailto:aho...@in...]
> Sent: Monday, January 01, 2001 2:24 AM
> To: David LeBlanc
> Cc: Steve Wainstead; php...@li...
> Subject: RE: Trouble with phpwiki
>
>
> David,
>
> > I've installed Apache 1.3.14, Php 4.04 and phpwiki 1.19 on Windows NT
>
> 1.19 has some nasty bugs. Try the nightly tarball instead.

Ok, will do!

> > The biggest problem imho is that there is no seed database, zip file =
or
> > flat (serialized) file to get one started.
>
> ??? If no FrontPage exists, files from pgsrc/ are *automatically*
> inserted
> into whatwever database you have chosen (dbm, mysql, flatfile, ...)
> If this didn't work for you, I'd appreciate if you could give as a more
> detailed bug report.

With the db type set to "file", and warnings set on, db_filesystem.php
 warns when it tries to unserialize files (db_flatfile.php line 51), and =
it
 brought up an empty "default" page (created on the fly I think). It also
 warns about a "no such file" .zip file too.

When I changed the db type to "mysql", it brought up a page that now had
 the "5 best links...." stuff at the bottom of the page, but it made no
 attempt to load pgsrc into the db. The db was created by hand and then b=
y
 using the schema script and pasting it into phpymsql admin tool.

Can you point me to the sources that do this autoloading please?

> > run your code before delivery with warnings enabled.
>
> I do. Not too long ago, I cleaned up a whole bunch of those warnings.
> Maybe, I didn't check with a fresh install.

A lot of warnings about undefineds: "id" and "hash" (this might be wrong,
i'm doing it from memory - see the other email I sent Steve).

> > There are some suspicious ones which I think makes it fail silently
> > when warnings are off.
>
> Example?

See Above

> > When loading the pages into mysql using the "edit this page" page's
> > Save button, mysql reported some syntax errors (loudly <g>) yet, when=
 I
> > went back and reloaded the base page and clicked on the link pointing
> > to the page i'd just entered, it was there! This behavior stopped aft=
er
> > about the 4th page loading.
>
> I guess this has to do with some SQL queries turning up an empty
> result at
> the beginning. Actually, this can only happen if you start with
> *no* pages
> in your db, whereas if the setup process works you have at least a doze=
n
> pages from pgsrc/ in your database.

It was complaing about a syntax error in the SQL statement. I notice that
the refs field in the wiki table ends up getting set to "N;" which looks =
a
bit odd.

> > It would be really nice, given the availability of the page sources, =
if
> > there was some sort of initial "load database/zip/flatfile" utility.
>
> Apart from the automatic load process (if no FrontPage exists), there's=
 a
> "load serialized pages" on the admin page. Or am I misunderstanding
> something here?

Well, I didn't know it was supposed to autoload - sorry :). It would be
 nice to expose the "load from text" that the autoload facility uses to
 install from pgsrc.

> > P.S. I tried locking a page (formatting rules), but phpwiki didn't se=
em
> > to honor that
>
> Could you describe exactly what you are doing and what the results are?
> Locking works for me.

I'll do that as soon as I can.

> > I don't see any bits in the wiki schema for page access control
> > do you do it some other way?
>
> Currently we distinguish only between two users: admin and everyone els=
e.
> Admin may edit locked pages, mortals may not (stored in 'flags',
> FLAG_PAGE_LOCKED is set). Reading is allowed for everyone. A more
> sophisticated user managament is currently not high priority.

By 'page access control', I was refering to locking - although, at some
point in the future, it would be nice to have admin/user access control.

> /Arno

One consequence of my having hand loaded the sql db seems to be that page=
s
aren't getting archived - "diff" always says the page isn't in the archiv=
e.

I hope nobody mistook my winging for lack of appreciation! PhpWiki is NEA=
T

:)

Happy New Year!!

Regards,

Dave

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