Re: [Phpwiki-talk] Re: WLUG Wiki <-> phpWiki

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

> OK. My first attempt at doing this was going to take the following form
>
> 1) Install vanilla phpwiki 1.3.11_rc3
> 2) Export (zip dump) from current WLUG wiki
> 3) Import via zip dump into phpwiki 1.3.11_rc3
> 4) Attempt to port all our modifications / plugins forward to 1.3.11_rc3
> such that they are in a state to be potentially forwarded upstream.

good, just CVS HEAD would be better.

> I've run into a few problems however.
>
> I'm doing all of the following on a Debian Sarge system using the
> packaged Apache2 and PHP4 binaries.
>
> * To get phpwiki to run, I had to modify my include path to point
> directly to the PEAR dir inside the phpwiki source. Not doing this
> caused an error about a redeclared DB class, presumably a conflict
> between my system PEAR and phpwiki's PEAR. Is this a known problem on
> Debian Sarge?

I don't know for Debian, because we don't care for specific distros, but
if the installed system pear DB is too old it is recommended to use ours.
There's no way to check the version number beforehand. pear is not well
designed.

> * Database logging doesn't work with postgresql (due to use of the
> DELAYED keyword which is only supported by MySQL) and we don't want it
> anyway.

This was fixed some weeks ago. Please try current CVS instead or the
nightly snapshot from the webpage.

> However there doesn't appear to be any way to disable this by
> default. The logical action to my mind would be to set ACCESS_LOG_SQL=0
> in config.ini, however the IniConfig parser appears to set all
> uninitialised variables in the config file to 0 which then leads to
> ACCESS_LOG_SQL being set to it's default value of 2. To get around this
> I have created the patch below which allows the user to specify
> ACCESS_LOG_SQL=-1 in config.ini to prevent database logging

Oops, I'll check why ACCESS_LOG_SQL=0 fails for you.
This should not happen.

> * Using precached HTML (WIKIDB_NOCACHE_MARKUP) results in errors of the
> following type when I try and view any page in the wiki
>
> Fatal Error:
> lib/WikiDB/backend/PearDB.php:1014: Error: wikidb_backend_peardb_pgsql:
> fatal database error
>
>       * DB Error: unknown error
>       * (UPDATE page SET cached_html='xڝ”ÏnÛ0Æï}
>       * A°ZοVÉ2d†¶5H·ö(6µ%CRšEÞ}”lg;Ú
> $€-šüñã''ÞI1‘Ü[¥Ý“±äNžË‘|s’¶þµ>¿“b&y­öž·G|Æ&.‘og''o)p§
>
> To make the wiki work I have to set WIKIDB_NOCACHE_MARKUP = true in
> config.ini. This looks like phpwiki is trying to insert bogus values
> into the HTML cache.

cached_html is gzipped.
So postgresql has problems with binary data. I'll fix that.

> * My first attempt at importing from the zip dump didn't succeed. Lots
> of errors were encountered regarding diff merging between page
> revisions. This resulted in only the very first revision (ie, not what
> is currently displayed in the WLUG wiki) being imported into my new
> wiki.

These are just warnings. Diff merging is not too clever.
You may want to overwrite all or merge manually.
We just provide the basic docs and needed action pages so normally
it's safe to overwrite all. Just the HomePage should be merged.

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