phpwiki-talk

[Phpwiki-talk] dumping

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

Hello,

   I would like to test performance of phpwiki with differents database. 
My current wiki is working with postgresql-7.0. I would like to dump the 
data and upload them in a wiki configured with flat file.

   So I have try to access to the admin.php page and then I can only 
lock or remove a page.

   Arno tells me that the dump is possible. Can you tell me how I do it ?

Thanks.
-- 
             .------------------------------------------------.
     .^.     | Didier Bretin, France | db...@in...    |
     /V\     |-----------------------| www.informactis.com    |
    // \\    |                       `------------------------|
   /(   )\   | Visit: http://jeuxlibres.free.fr/              |
    ^^-^^    `------------------------------------------------'

Re: [Phpwiki-talk] FW: problems with numbered lists

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

Can you give us a sample URL? I saw a numbered list in your SandBox and it
looked fine.

~swain

On Thu, 9 Aug 2001, Novogrodsky, Dave wrote:

>  Dear Mr. Wainstead,
>
>  I am using your WikiPHP to store project documentation
> (http://www.novogrodsky.net). I have been having a problem creating
> numbered lists. I am using version 1.2 and it is running on a Red Hat box.
> Any idea what is causing this problem?
>
> Sincerely,
> David Novogrodsky
>
>
> _______________________________________________
> 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
http://pgp.document_type.org:11371/pks/lookup?op=get&search=0xF7323BAC

[Phpwiki-talk] FW: problems with numbered lists

[Novogrodsky, D. <Dav...@co...>]

 Dear Mr. Wainstead,

 I am using your WikiPHP to store project documentation
(http://www.novogrodsky.net). I have been having a problem creating
numbered lists. I am using version 1.2 and it is running on a Red Hat box.
Any idea what is causing this problem?

Sincerely,
David Novogrodsky

Re: [Phpwiki-talk] offline backup script with rcs (only incremental changes)

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

Oops, 
forgot the url's of the mentioned administrative interface and standalone
trick:

http://xarch.tu-graz.ac.at/home/rurban/acadwiki-1.3.6pre/viewsrc.php?show=admin/fix_HomePage.php#src
http://xarch.tu-graz.ac.at/home/rurban/acadwiki-1.3.6pre/viewsrc.php?show=admin/renamepage.php#src

This should work soon:
% php admin/fix_HomePage.php 

I'm looking how to get the absolute dir of WIKIROOT and setting up the whole
mess 
from the commandline. either by checking argv[1] or by searching for
index.php.
Missing is only RenamePage() in lib/stdlib.php yet.

also did a minor fix in
http://xarch.tu-graz.ac.at/home/rurban/acadwiki-1.3.6pre/viewsrc.php?show=admin/wbackup#src

Reini Urban schrieb:
> I have other in the works, e.g. admin/fix_HomePage.php,
> to rename FrontPage to HomePage in the database,
> which can be called standalone or by url.
> based on admin/renamepage.php, which I'm writing right now.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

[Phpwiki-talk] offline backup script with rcs (only incremental changes)

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

Hi,
This is a nice backup script suitable for cronjobs, 
daily backups where only incremental changes are stored.
I believe that it only works for 1.3x (zipdump),
someone else should find out the url to produce 1.2 dumps.
But it's not hardcoded anywhere.

Run it in the backupdir where all the ,v files get stored.
This will get filled up with files according the pagenames, so it would be 
wise to be empty, otherwise the page will overwrite an existing file.

Usage: 
cd /path/to/phpwiki/bak
original:
  ../admin/wbackup http://myserver/mywiki/index.php?
with pathinfo:
  ../admin/wbackup http://myserver/mywiki/  
with ZIPDUMP_AUTH = true
  ../admin/wbackup --http-user=admin --http-passwd=pass
http://myserver/mywiki/  

I had to strip the first line of each backup file, not to check-in 
equal files, where only the dump date changed.

Maybe one might take this to enable rcs versioning.
At least I try to incoorporate rcsdiff with these backups to reduce the 
space overhead with the current versioning.

Requirements:
wget
sed
unzip
on windows probably cygwin.

Note: 
my windows versions of rcs and ci get confused with \r. (=> a big oneliner)
so you would have to add unix2dos in between.

CVS:
where should be put such commandline utils? 
admin probably.

I have other in the works, e.g. admin/fix_HomePage.php, 
to rename FrontPage to HomePage in the database, 
which can be called standalone or by url.
based on admin/renamepage.php, which I'm writing right now.

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

Re: [Phpwiki-talk] CVS, mysql: order by rand()

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

On Sat, 4 Aug 2001, Reini Urban wrote:

> I'll start now to merge my AcadWiki enhancements into CVS.
> I need the latest improvements on VersionControl and UserAuth. Good work!

Absolutely! One thing I'd like to do with VersionControl though is move
the form to the diff page, not the info page. The info page was intended
to show the internal stucture of the page as it lives in the data
structure in PhpWiki. This should be a simple cosmetic change.

> maybe: multiline code, my ugly hacks for <code> .. </code>, <verbatim> ..
> </verbatim>, and <nowiki> .. </nowiki>

Hmm. I know we've discussed this on the list in the past. The 1.3 branch
has a new rendering engine Arno wrote which is really slick. I don't
recall if there was a hook for doing multiline processing or not. The
regexp to change the pattern match shouldn't be hard, but then, users can
use [square brackets] if they need to go beyond WikiWords.

> RandomPage:
> -----------
> how to workaround this mysql 3.23 feature which doesn't work in 3.22?

We are definitely moving to DB and PEAR, so you might want to think about
it in that context. We need the SQL to work with the major databases now
(MySQL, Oracle, MSSQL, Postgresql and so on).

> CharCount:
> ----------
> A new user requested feature: display the number of chars in pageinfo, maybe
> words also.
> we need this to produce a community text for a local internet handbook, which
> must have
> 10,000 chars. is this okay to put it into the pageinfo field. I know that
> currently there
> are only static db fields, but the user doesn't care. some convenience figures
> wouldn't hurt
> imho on the info page.

A nice feature!

~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
http://pgp.document_type.org:11371/pks/lookup?op=get&search=0xF7323BAC

[Phpwiki-talk] security: register_globals off

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

how about a switch to register_globals off?
seems to be a major hack, but for security reasons very advisable.

details: 
  all implicitly passed args/vars must be changed to
HTTP_[POST/GET]_VARS['varname']
  most of it can be fixed in lib/main.php though, because we have only one
main event loop.
sample:
  $searchterm=HTTP_GET_VARS['searchterm'];

see http://www.securereality.com.au/studyinscarlet.txt

best would be:
* register_globals off
* safe_mode on (but then there's no file upload anymore)
* allow_url_fopen off
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

[Phpwiki-talk] CVS, mysql: order by rand()

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

I'll start now to merge my AcadWiki enhancements into CVS.
I need the latest improvements on VersionControl and UserAuth. Good work!

I'll try:
BetterIndex, RandomPage, OrphanPages, WantedPages, improved BackLink, 
SeparateListOutput, MagicPages, SplitWordsInTitle, BetterRecentChanges,
HowToBlockRobots, 
optional PageChangeNotification to the admin only, ImageLinks
(see
http://phpwiki.sourceforge.net/phpwiki/index.php?full=CategoryNextWikiSuggestions)

maybe: locale stuff (this is awful, I just broke my german wiki db after
having recompiled to php-4.0.6)
maybe: localized WikiNameRegexp with TrailingNumbers (optionally)
maybe: multiline code, my ugly hacks for <code> .. </code>, <verbatim> ..
</verbatim>, and <nowiki> .. </nowiki>

RandomPage:
-----------
how to workaround this mysql 3.23 feature which doesn't work in 3.22?

  select pagename from wiki order by rand() limit 1;

the rand() function is defined in 3.22 also, but I wanted to avoid subselects.
attempt 1:
  $res = mysql_query("select pagename from $WikiPageStore", $dbi["dbc"]);
  srand((double)microtime()*1000000);
  $rows = mysql_num_rows($res);
  $page = mysql_result($res,rand(0,$rows-1));

how can one avoid to checkout all pages by using mysql the rand() function?
LIMIT doesn't accept ROUND($pagecount*rand()),1 as argument.
mysql v3.22.25 doesn't accept this syntax neither: 
  set @i:=round(200*rand());

oh bad. at least attempt 1 is cross-db compatible.


CharCount:
----------
A new user requested feature: display the number of chars in pageinfo, maybe
words also.
we need this to produce a community text for a local internet handbook, which
must have 
10,000 chars. is this okay to put it into the pageinfo field. I know that
currently there 
are only static db fields, but the user doesn't care. some convenience figures
wouldn't hurt 
imho on the info page.

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

[Phpwiki-talk] Re: AW: phpwiki navigation footer

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

On Wed, 1 Aug 2001, Andreas Krueger wrote:

> I have installed your phpwiki again,
> at www.andreask.de/phpwiki
> you can see what happens.
> Changing pages works fine, but still,
> there are "XXX Cannot replace" error-messages.

This is a mystery so far. This error message does not seem to exist in the
PhpWiki source code, so it might be coming from PHP itself. I'm still
looking.

> And the "5 best incoming links, 5 best outgoing links, 5 most popular
> nearby." are not shown.

I should have mentioned earlier (and I believe this is in the INSTALL
notes) that not all the features are implemented in the DBM version of
PhpWiki. The related links features are based on SQL queries that we did
not duplicate in 1.2. A user sent a patch some time ago but I never got it
to work for me.

> the one line:
>       $DBMdir = "/homepages/10/d10226928/htdocs/andreask/phpwiki/db";
>
> I had to use this absolute path, because
>       $DBMdir = "/andreask/phpwiki/db";
>
> resulted in errors

That would be the correct thing to do... by the way Netcraft claims your
ISP is running Linux, just so you know.

cheers
~swain


>
>
>
> Hello Steve,
> Thanks again for answering.
>
> > Please tell me what version of PhpWiki you are using
> the newest: 1.2.0 02/01/01
>
> > which database
> I chose "default", so dbm, right?
>
> > what platform you are running on
> I don't know, sorry.
>
> > and what version of PHP.
> I found out about my PHP asking the provider:
>  PHP 4.0.6
> there is also an PHP 3.0.16 installed,
> which can be chosen by *.php3
>
>
> I am currently trying out usemod092, a perl-based wiki.
> Are there different dialects of Wiki-Markup?
>
>
> Initial Comment:
>  I got these php-errors using the /admin tools:
>  /admin/dumpserial.php --------------------- Fatal error: Call to undefined
> function:  getallwikipagenames()  in
> /homepages/10/d10226928/htdocs/andreask/cp/wiki/admi n/dumpserial.php on
> line 10  /admin/zip.php -------------- Fatal error: Call to undefined
> function: closedatabase ()  in
> /homepages/10/d10226928/htdocs/andreask/cp/wiki/admi n/zip.php on line 71
> How can I use the /admin - tools?  ciao, AndreasK
>
> ----
>
> The admin.php gave an error500 until I removed all those lines:  // from the
> manual, Chapter 16    if (($PHP_AUTH_USER != $wikiadmin  )  ||
> ($PHP_AUTH_PW   != $adminpasswd)) {       Header("WWW-Authenticate: Basic
> realm=\PhpWiki\");       Header("HTTP/1.0 401 Unauthorized");       echo
> gettext ("You entered an invalid login or  password.");       exit;    }
> Now my admin.php is without password - but at least it  works...  ciao,
> andreasK
>
> terrible, that sourceforge removes the cr-returns from my message...
>
> > Did you set the username and password for the
> > administrator first?
> yes, I did.
> Only to "a" and "a", but I also tried other words. Any rules?
>
> Before that I got the error message "Set the administrator account and
> password first", which showed, that the script worked perfectly up to that
> line...
>
> > admin.php will not work
> > without having the username and password defined.
> yes, I read that.
>
> > With those lines removed anyone can use administrator
> > features of your Wiki.
> I know, that's a pity, but the directory is password-protected, anyway, so
> not a terrible problem, this one.
>
>
> THX,
> Andreas
>
>
> > > Hi Steve,
> > >
> > > Thanks for PHP Wiki, I am currently trying it out
> > > as a development plattform for a small project.
> > > Very useful, these Wiki's!
> > >
> > > I have already posted two questions in /bugs
> > >
> > > but here are more:
> > > a)
> > > Somewhere I have seen YOUR PhpWiki with 3
> > > automatic footer-lines which show:
> > > 5 best incoming links, 5 best outgoing links and
> > > 5 most popular nearby.
> > >
> > > How can I do that?
> > >
> > > b)
> > > With admin.php I often get the message:
> > > XXX Cannot replace
> > > But the action is actually done perfectly.
> > >
> > > Also index.php sometimes reacts like that:
> > > XXX Cannot replace XXX Cannot replace
> > >
> > > Thanks a lot in advance,
> > > AndreasK
> > >
> > >
>
>
>

---
                  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
http://pgp.document_type.org:11371/pks/lookup?op=get&search=0xF7323BAC

Re: [Phpwiki-talk] Re:Userids?

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

>yes. but why not also the admin? 
>the admin check is done later in user_auth.

I don't think we want random people to be able to make
edits which appear to be signed by the admin.
 
>other wiki's do it with simple userid cookies instead of auth.
>setting up the db auth scheme is not that trivial. cookies are easier.

(Password) authentication however is on the to-do list.
The motivations for adding real authentication include:
 * Page ownership (read-only or add-only pages).
 * Page change notification (authentication prevents
   the use of this feature for mail-bombing unsuspecting
   recipients.)
 * The (server-side) storage of large amounts of per-user
   state data could be used to do things like list/highlight
   changes since last visit, etc...  (Cookies can only store
   a finite amount of information.)

>> This would be a trivial hack, and I believe would be maximally forward-compa
> tible
>> with future non bogo-authentication.


The one problem I see with my proposed hacks is that it's going to
be fairly confusing to the user.  Since it's going to use the 
HTTP authentication mechanism (as currently used for admin logins)
there's not much opportunity to issue meaningful prompts.

Re: [Phpwiki-talk] Re:Userids?

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

Jeff Dairiki schrieb:
> How's this for an interim solution (until we get real user
> authentication, that is)?
> 
> Allow anyone to log in (via HTTP authentication,
> the same way the admin currently logs in) with any userid
> except the admin user, and any password.  

yes. but why not also the admin? 
the admin check is done later in user_auth.

other wiki's do it with simple userid cookies instead of auth.
setting up the db auth scheme is not that trivial. cookies are easier.

> This would be a trivial hack, and I believe would be maximally forward-compatible
> with future non bogo-authentication.
> I guess we don't want to allow people to set userid's which
> look like IP addresses or host names.
> 
> Perhaps we should only allow people to log in with with userid's
> which are WikiWords, so as to encourage userids to be the names
> of homepages?

good idea. count me pro.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: [Phpwiki-talk] Re:Userids?

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

Sounds fine... hack away! :-)

~swain

On Fri, 20 Jul 2001, Jeff Dairiki wrote:

> How's this for an interim solution (until we get real user
> authentication, that is)?
>
> Allow anyone to log in (via HTTP authentication,
> the same way the admin currently logs in) with any userid
> except the admin user, and any password.  This would be a
> trivial hack, and I believe would be maximally forward-compatible
> with future non bogo-authentication.
>
> I guess we don't want to allow people to set userid's which
> look like IP addresses or host names.
>
> Perhaps we should only allow people to log in with with userid's
> which are WikiWords, so as to encourage userids to be the names
> of homepages?
>
>
> Speak now or suffer the short term consequences.
>
> Jeff
>
>
> _______________________________________________
> 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
http://pgp.document_type.org:11371/pks/lookup?op=get&search=0xF7323BAC

Re: [Phpwiki-talk] Re:Userids?

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

How's this for an interim solution (until we get real user
authentication, that is)?

Allow anyone to log in (via HTTP authentication,
the same way the admin currently logs in) with any userid
except the admin user, and any password.  This would be a
trivial hack, and I believe would be maximally forward-compatible
with future non bogo-authentication.

I guess we don't want to allow people to set userid's which
look like IP addresses or host names.

Perhaps we should only allow people to log in with with userid's
which are WikiWords, so as to encourage userids to be the names
of homepages?


Speak now or suffer the short term consequences.

Jeff

Re: [Phpwiki-talk] Re:Userids?

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

In message <000601c110c9$279a9e80$640...@ho...>,"Seth Cohn" writes:

>It looks as if  it isn't a major thing, just set the cookie
>correctly (via setprefs&userid ) and then read it back.
....
>Adding a single line to UserPreferences such as
>[Set UserID | phpwiki:?action=setprefs&userid=40()] should be possible,
>right?

Yes I think that's right.  I'll take a look at it tomorrow, unless
someone else speaks up before then to say they're working on it.

I wrote the userauth stuff with the idea that it would be expanded
to be able to authenticate (i.e. with passwords) registered users 
(other than admin).  However, that step is currently waiting on the
specification/development of some sort of user database API (and all
the forms, etc. needed to register and authenticate users) --- this
is another area where it would be nice if we could find some "standard"
PHP library code which does what we want.

My one concern is that the non-authenticated userid's be added
in a way that will be forward-compatible with authenticated userid's
in the future.   (I'm sure it's possible, it just takes some thought
and care.)

Jeff

[Phpwiki-talk] Re:Userids?

[Seth C. <se...@eu...>]

Reini Urban wrote:

> I added this experimentally but I did too much and so it doesn't work.
> I also added arbitrary user events to support email notification for a
> list of pages. I guess this broke things.
> but the user cookie with jeff's user class works fine.

>
http://xarch.tu-graz.ac.at/home/rurban/acadwiki-1.3.5pre/viewsrc.php?show=li
b/userauth.php#src
>
http://xarch.tu-graz.ac.at/home/rurban/acadwiki-1.3.6pre/viewsrc.php?show=li
b/stdlib.php#src

I unsuccesfully attempted to diff these with the existing userauth and
stdlib files... It's clear that a lot of the changes you made are for the
email and notify pieces... but when I attempted to figure out how to make
just the cookie work, it didn't and it broke stuff enough that I went back
to the original userauth.  stdlib didn't seem to need much changing if any.

Someone who understands this better than me (not hard) want to take a quick
crack at it?  It looks as if  it isn't a major thing, just set the cookie
correctly (via setprefs&userid ) and then read it back.  Maybe I'm wrong,
but it looks like everything else in stdlib will work so long as a valid
userid is there.  How much of the auth stuff needs to be there for this?

Having anyone be able to sign via RecentChanges is a really nice thing...
Adding a single line to UserPreferences such as
[Set UserID | phpwiki:?action=setprefs&userid=40()] should be possible,
right?

Seth

[Phpwiki-talk] Re:Userids?

[Seth C. <se...@eu...>]

Reini Urban wrote:

> I added this experimentally but I did too much and so it doesn't work.
> I also added arbitrary user events to support email notification for a
> list of pages. I guess this broke things.
> but the user cookie with jeff's user class works fine.

>
http://xarch.tu-graz.ac.at/home/rurban/acadwiki-1.3.5pre/viewsrc.php?show=li
b/userauth.php#src
>
http://xarch.tu-graz.ac.at/home/rurban/acadwiki-1.3.6pre/viewsrc.php?show=li
b/stdlib.php#src

I unsuccesfully attempted to diff these with the existing userauth and
stdlib files... It's clear that a lot of the changes you made are for the
email and notify pieces... but when I attempted to figure out how to make
just the cookie work, it didn't and it broke stuff enough that I went back
to the original userauth.  stdlib didn't seem to need much changing if any.

Someone who understands this better than me (not hard) want to take a quick
crack at it?  It looks as if  it isn't a major thing, just set the cookie
correctly (via setprefs&userid ) and then read it back.  Maybe I'm wrong,
but it looks like everything else in stdlib will work so long as a valid
userid is there.  How much of the auth stuff needs to be there for this?

Having anyone be able to sign via RecentChanges is a really nice thing...
Adding a single line to UserPreferences such as
[Set UserID | phpwiki:?action=setprefs&userid=40()] should be possible,
right?

Seth

Re: [Phpwiki-talk] archiving for PostgreSQL

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

On Thu, 19 Jul 2001, Adam Shand wrote:

> just a vote of interest.  please dont' drop support for non-database
> wiki's!  i still want to use flat files or even dbm.

No, I have no intention of dropping them... in fact we need an abstract
base class for DB access. This is something Jeff, Arno and I hashed out on
the list a few months ago:

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

With an abstact base class, we can derive classes for DB/dbx, dba and
flat file stores and be done with it. Three will be easier to maintain
than five.

~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
http://pgp.document_type.org:11371/pks/lookup?op=get&search=0xF7323BAC

Re: [Phpwiki-talk] archiving for PostgreSQL

[Joel U. <uck...@no...>]

Quoth Adam Shand:
> 
> > Anyway, I still need to update the dba, dbm, and flatfile libs, since
> > neither Pear DB nor dbx handles those at present.
> 
> just a vote of interest.  please dont' drop support for non-database
> wiki's!  i still want to use flat files or even dbm.
> 
> adam.

Like I said, that's why I'm going to bring those up to speed today. I like the non-SQL DBs, too, if for no other reason than you can use them to test Phpwiki right out of the box.

-- 
J.

Re: [Phpwiki-talk] archiving for PostgreSQL

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

> Anyway, I still need to update the dba, dbm, and flatfile libs, since
> neither Pear DB nor dbx handles those at present.

just a vote of interest.  please dont' drop support for non-database
wiki's!  i still want to use flat files or even dbm.

adam.

Re: [Phpwiki-talk] Userids?

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

hmm, 
I added this experimentally but I did too much and so it doesn't work.
I also added arbitrary user events to support email notification for a 
list of pages. I guess this broke things.
but the user cookie with jeff's user class works fine. 

right now i'm fighting with zope to get a project finished so I cannot 
work much in phpwiki.

http://xarch.tu-graz.ac.at/home/rurban/acadwiki-1.3.5pre/viewsrc.php?show=lib/userauth.php#src
http://xarch.tu-graz.ac.at/home/rurban/acadwiki-1.3.6pre/viewsrc.php?show=lib/stdlib.php#src


Seth Cohn schrieb:
> Running recent cvs snapshot....  the more I play, the more little things I
> like, and the more little things I think about...
> Some aren't important, and seem to have been discussed on the Wiki as future
> Suggestions, such as RegisterInterest
> and AppendOnly (no clue if those are valid pages, just the concept as I
> recall)
> 
> The one real useful thing I want ASAP::
> 
> If I log in with the admin userid, it nicely changes the RecentChanges entry
> from being the IP (or rather the lookedup name) to my userid which if
> WikiWorded is a nice link...  But it only works for the single admin
> account, not other users.
> 
> According to the code, it's not complete yet, so the real question is: how
> long until it's finished?  If all it involves is setting a cookie, what's
> holding it up?
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: [Phpwiki-talk] Newpage creating errors.

[Joel U. <uck...@no...>]

Quoth "Seth Cohn":
> There is a set of errors when first creating a newpage:
> 
> lib/editpage.php:6: Notice[8]: Undefined variable: version
> 
> lib/editpage.php:6: Notice[8]: Undefined variable: version
> 
> lib/stdlib.php:522: Notice[8]: Undefined index: pagename
> 
> After creating a new page: you get this error.
> 
> lib/stdlib.php:522: Notice[8]: Undefined index: pagename
> 
> It vanishes after the page is reloaded, or editing an existing page.
> 
> Completely cosmetic, but disconcerting to say the least....

Hmm. I'm sure that's related to some of the changes I made. I'll take a 
look at that in the morning.

-- 
J.

[Phpwiki-talk] Newpage creating errors.

[Seth C. <se...@eu...>]

There is a set of errors when first creating a newpage:

lib/editpage.php:6: Notice[8]: Undefined variable: version

lib/editpage.php:6: Notice[8]: Undefined variable: version

lib/stdlib.php:522: Notice[8]: Undefined index: pagename

After creating a new page: you get this error.

lib/stdlib.php:522: Notice[8]: Undefined index: pagename

It vanishes after the page is reloaded, or editing an existing page.

Completely cosmetic, but disconcerting to say the least....

[Phpwiki-talk] Userids?

[Seth C. <se...@eu...>]

Running recent cvs snapshot....  the more I play, the more little things I
like, and the more little things I think about...
Some aren't important, and seem to have been discussed on the Wiki as future
Suggestions, such as RegisterInterest
and AppendOnly (no clue if those are valid pages, just the concept as I
recall)

The one real useful thing I want ASAP::

If I log in with the admin userid, it nicely changes the RecentChanges entry
from being the IP (or rather the lookedup name) to my userid which if
WikiWorded is a nice link...  But it only works for the single admin
account, not other users.

According to the code, it's not complete yet, so the real question is: how
long until it's finished?  If all it involves is setting a cookie, what's
holding it up?

Seth

Re: [Phpwiki-talk] archiving for PostgreSQL

[Joel U. <uck...@no...>]

Quoth Steve Wainstead:
> On Wed, 18 Jul 2001, Joel Uckelman wrote:
> 
> > When I added the code for page versioning, I broke support for everything
> > except MySQL, so now I'm trying to bring the other db formats up to speed.
> > Perhaps the changes I just committed in lib/pgsql.php and
> 
> Oh, don't worry. We are going to switch to a generic DBMS interface --
> either PEAR's DB or the dbx functions -- quite soon. Perhaps even tonight
> if I stay in and hack. I have done some rudimentary testing with the dbx
> stuff and it works fine. DB is a much larger hoop to jump through.
> 
> We will gain two big things: only one database interface to support, and
> multiple databases will now be supported. I'm leaning towards PEAR/DB at
> the moment since it's more developed, supports more databases and PEAR
> looks like the way to go right now.

Before looking at the Pear DB and dbx docs, I was hoping one of them would 
handle all of the db formats we use now; alas, they only support *SQL. That 
aside, using one of these would reduce the number of separate db libs we 
have to maintain, which is a Good Thing. I see that we'd gain support for 
seven extra SQL servers (!) if we went with Pear DB, as opposed to gaining 
two and losing msql with dbx. I'm not sure how much demand there is for 
Phpwiki to work with any of those, however, and even so, the dbx docs read 
as though support for more DBs is forthcoming. And while Pear DB seems more 
featureful than dbx, lots of those features are ones I don't see us using. 
So my vote is for dbx, though if you make it work with Pear DB, I won't 
change it back. ;)

Anyway, I still need to update the dba, dbm, and flatfile libs, since 
neither Pear DB nor dbx handles those at present.

-- 
J.

Re: [Phpwiki-talk] archiving for PostgreSQL

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

Merriam Webster says both "schemas" and "schemata" are correct, so we'll
let it lie for now.

~swain

One entry found for schema.



Main Entry: sche=B7ma
Pronunciation: 'skE-m&
Function: noun
Inflected Form(s): plural sche=B7ma=B7ta  /-m&-t&/; also schemas
Etymology: Greek schEmat-, schEma
Date: circa 1890
1 : a diagrammatic presentation; broadly : a structured framework or plan
: OUTLINE
2 : a mental codification of experience that includes a particular organize=
d
way of perceiving cognitively and responding to a complex situation or set
of stimuli


---
                  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
http://pgp.document_type.org:11371/pks/lookup?op=3Dget&search=3D0xF7323BAC