phpwiki-talk

Re: [Phpwiki-talk] Protecting against google rank spam...

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

electron schrieb:
> I like the redirect idea. Plugin here we come....

Well, I'm not convinced, since the backbutton will break.
Maybe a list of registered external links will make sense.

> It might also be an idea for anonymous edits to have to be approved by a
> registered user before making the current version of a page. 

User approval? Not a bad idea.

I'm just doing the gForge.org integration so that they can use phpwiki 
as plugin. They have such an approval scheme.
FYI: gForge is the software which runs behind sourceforge.net.

> That's not in the spirit of wiki, but this next idea might be:
> 
> Expanding on that idea: Based on referrer or user agent, we show a version
> of the page that was last edited by a real user to the bot and leave the
> current version as it is to regular browsers.
> 
> Any phpwikis get spammed recently?

Not automatically yet. Just some trial sandbox spam with lots of links.

I guess they just try if an automatic phpwiki spam-pester will make 
sense in terms of google ranks.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: [Phpwiki-talk] mysql config.ini something wrong

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

Hello!

Now it is running, i found ist in:
http://www.macdevcenter.com/pub/a/mac/2003/06/05/wiki.html

Regards
Peter

> Hello!
> 
> I have taken sql as database but something wrong,
> http://www.apfel.at/phpwiki/
> 
> What is here do to?
> Regards
> Peter
> 
>> On Wed, Jun 09, 2004 at 06:28:05AM +0200, peter polz wrote:
>>> Hello!
>>>>> You still haven't defined a database.
>>> 
>>> Where can i define the database in the config.ini
>> 
>> DATABASE_DSN allows you to specify username, password, host, database
>> parameters for a MySQL database.  You'll want to fix your DATABASE_TYPE,
>> though.  If you want to stick with the dba stuff, though, you'll need to
>> specify the directory to store your DB file in the DATABASE_DIRECTORY.
>> 
>> - Matt
>> 
>> 
>> -------------------------------------------------------
>> This SF.Net email is sponsored by: GNOME Foundation
>> Hackers Unite!  GUADEC: The world's #1 Open Source Desktop Event.
>> GNOME Users and Developers European Conference, 28-30th June in Norway
>> http://2004/guadec.org
>> _______________________________________________
>> Phpwiki-talk mailing list
>> Php...@li...
>> https://lists.sourceforge.net/lists/listinfo/phpwiki-talk
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: GNOME Foundation
> Hackers Unite!  GUADEC: The world's #1 Open Source Desktop Event.
> GNOME Users and Developers European Conference, 28-30th June in Norway
> http://2004/guadec.org
> _______________________________________________
> Phpwiki-talk mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwiki-talk

Re: [Phpwiki-talk] mysql config.ini something wrong

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

Hello!

I have taken sql as database but something wrong,
http://www.apfel.at/phpwiki/

What is here do to?
Regards
Peter

> On Wed, Jun 09, 2004 at 06:28:05AM +0200, peter polz wrote:
>> Hello!
>>>> You still haven't defined a database.
>> 
>> Where can i define the database in the config.ini
> 
> DATABASE_DSN allows you to specify username, password, host, database
> parameters for a MySQL database.  You'll want to fix your DATABASE_TYPE,
> though.  If you want to stick with the dba stuff, though, you'll need to
> specify the directory to store your DB file in the DATABASE_DIRECTORY.
> 
> - Matt
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: GNOME Foundation
> Hackers Unite!  GUADEC: The world's #1 Open Source Desktop Event.
> GNOME Users and Developers European Conference, 28-30th June in Norway
> http://2004/guadec.org
> _______________________________________________
> Phpwiki-talk mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwiki-talk

Re: [Phpwiki-talk] mysql config.ini something wrong

[Matthew P. <mp...@he...>]

On Wed, Jun 09, 2004 at 06:28:05AM +0200, peter polz wrote:
> Hello!
> >> You still haven't defined a database.
> 
> Where can i define the database in the config.ini

DATABASE_DSN allows you to specify username, password, host, database
parameters for a MySQL database.  You'll want to fix your DATABASE_TYPE,
though.  If you want to stick with the dba stuff, though, you'll need to
specify the directory to store your DB file in the DATABASE_DIRECTORY.

- Matt

Re: [Phpwiki-talk] mysql config.ini something wrong

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

Hello!
>> You still haven't defined a database.

Where can i define the database in the config.ini

Regards
Peter

>> peter polz schrieb:
>>> Next problem:
>>> lib/WikiDB/backend/PearDB.php:34: Fatal[256]: Can't connect to database=
:
>>> wikidb_backend_peardb: fatal database error
>>>     =E2=82=AC      DB Error: not found
>>>     =E2=82=AC      (Unable to include the DB/.php file for `')
>>>     =E2=82=AC    =20
>>=20
>> Please read and try to understand the error messages.
>> You still haven't defined a database.


;=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
; Part Two: Database Selection
;=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

; 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 =3D dbt
  =20
; 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 =3D 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 =3D "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 whateve=
r
; is given here.
DATABASE_SESSION_TABLE =3D session

; For the file and dba backends, this specifies where the data files will b=
e
; located.  Ensure that the user that the webserver runs as has write acces=
s
; 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 =3D /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 =3D gdbm

; How long will the system wait for a database operation to complete?
; Specified in seconds.
DATABASE_TIMEOUT =3D 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 =3D some_other_directory

Re: [Phpwiki-talk] Wikis: The Next Frontier for Spammers?

[Bob A. <apt...@cy...>]

Hi,

On Tue, 8 Jun 2004, Steve Wainstead wrote:

> I'm also thinking that a randomly generated, one time password rendered in
> an image would be sufficient to foil spambots and still allow anonymous
> posting. The downside is: it requires graphics library with PHP. I think
> it would be possible, though, to create a small library that takes a word
> and renders it as ascii art, which would make it readable to humans only

s/humans/sighted humans/

I'm not a big fan of "captchas" due to accessibility issues but I am
intrigued by those rendered as ASCII art...

-- Bob

[Phpwiki-talk] Fwd: The emergent behavior of abandoned wikis

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

Another interesting article, author uses a modified PhpWiki. It's about
how Google drew a lot of people to a page by accident, and the results:

http://www.commonmonkeyflower.net/cms/item/412/

----
                  http://www.panix.com/~swain/
    "It has all the faults of a photograph." -- David Hockney
----

Re: [Phpwiki-talk] Wikis: The Next Frontier for Spammers?

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

On Tue, 8 Jun 2004, Bob Apthorpe wrote:

> Note also that anyone who implements such a thing in a portable fashion
> will become a hero of the blog community because they are suffering
> worse from link spamming than the wiki community. At least that's what

I'm also thinking that a randomly generated, one time password rendered in
an image would be sufficient to foil spambots and still allow anonymous
posting. The downside is: it requires graphics library with PHP. I think
it would be possible, though, to create a small library that takes a word
and renders it as ascii art, which would make it readable to humans only
(like the 'figlet' tool):

                  _   _
  ___  _ __   ___| |_(_)_ __ ___   ___
 / _ \| '_ \ / _ \ __| | '_ ` _ \ / _ \
| (_) | | | |  __/ |_| | | | | | |  __/
 \___/|_| |_|\___|\__|_|_| |_| |_|\___|


~swain

----
                  http://www.panix.com/~swain/
    "It has all the faults of a photograph." -- David Hockney
----

[Phpwiki-talk] crash with auth user...

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

Reini,
  I've tracked the offending line down to line 133 in Template.php:

eval('?>' . $this->_munge_input($this->_tmpl));

  I can echo out the contents of $this->_munge_input($this->_tmpl) so that
call isn't crashing me.

Here is the contents of $this->_munge_input($this->_tmpl)
-----------------------------------------------------------------
 stuff.
 *
 * NS/MO/IE/Op Browsers before 4.0 don't like that.
 */
if (browserVersion() >= 4.0)
  printf("\n", CHARSET);
?>


_print( Template('head') );?>
_print( Template('body') );?>
\n", $RCS_IDS);
}
?>
-----------------------------------------------------------------

It appears that there is a comment header missing somewhere.

John

Re: [Phpwiki-talk] bug in wikiusernew 'old' USER_AUTH_POLICY

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

John Cole schrieb:
> Reini,
>   Line 916 in WikiUserNew.php should be
> 
> function_exists('ldap_connect')) {
> 
> instead of 
> 
> function_exists('ldap_open')) {
> 
> There is no ldap_open command, so it will never try the LDAP auth.

I knew it must have been something stupid like this.

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

[Phpwiki-talk] Flat files

[Dan S. <da...@il...>]

Hi,

I have just installed phpWiki using flat files and I am getting the following
error, when it starts up :

Inserting page AddingPages, version 1 from text file

Warning: fopen(/tmp/wiki/pages/AddingPages): failed to open stream: No such
file or directory in
\\nas12ent\domains\w\wikiweb.co.uk\user\htdocs\phpwiki\lib\db_filesystem.php
on line 104


WikiFatalError
Error while writing page 'AddingPages'


Permissions look good, though it is on a Windows box.

Any help would be greatly appreciated.

Regards,

Dan

[Phpwiki-talk] bug in wikiusernew 'old' USER_AUTH_POLICY

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

Reini,
  Line 916 in WikiUserNew.php should be

function_exists('ldap_connect')) {

instead of 

function_exists('ldap_open')) {

There is no ldap_open command, so it will never try the LDAP auth.

John

Re: [Phpwiki-talk] flat files

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

Dan Stapleton schrieb:
> I am trying to get phpwiki working on a windows server with flat files. As far
> as I can tell the directory has full write permissions.
> 
> The page that comes up looks like this :
> 
> Inserting page AddingPages, version 1 from text file
> 
> Warning: fopen(/tmp/wiki/pages/AddingPages): failed to open stream: No such
> file or directory in
> \\nas12ent\domains\w\wikiweb.co.uk\user\htdocs\phpwiki\lib\db_filesystem.php
> on line 104
> 
> WikiFatalError
> Error while writing page 'AddingPages'
> 
> Any Help much appreciated.

Sorry, I cannot really help with the 1.2.x releases. I'm busy with the 
current version.

How about trying the current version?
The CVS version was tested and fixed recently for flatfile.

The fix affected only log-running flatfile wiki's when the database 
automatically purged a old minor revision.

So you can try any release if you don't care about this bug #963268
http://sourceforge.net/tracker/index.php?func=detail&aid=963268&group_id=6121&atid=106121

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

[Phpwiki-talk] flat files

[Dan S. <da...@il...>]

Hi,

I am trying to get phpwiki working on a windows server with flat files. As far
as I can tell the directory has full write permissions.

The page that comes up looks like this :

Inserting page AddingPages, version 1 from text file

Warning: fopen(/tmp/wiki/pages/AddingPages): failed to open stream: No such
file or directory in
\\nas12ent\domains\w\wikiweb.co.uk\user\htdocs\phpwiki\lib\db_filesystem.php
on line 104


WikiFatalError
Error while writing page 'AddingPages'

Any Help much appreciated.

Kind Regards,

Dan

Re: [Phpwiki-talk] Wikis: The Next Frontier for Spammers?

[Bob A. <apt...@cy...>]

Hi,

On Mon, 7 Jun 2004 22:23:42 +0200 Jon =C5slund <d9...@na...> wrote:

> On Mon, Jun 07, 2004 at 01:34:45PM -0400, Steve Wainstead wrote:
> > Nothing new here except a higher profile for the idea...
> >
> > http://news.netcraft.com/archives/2004/06/04/wikis_the_next_frontier_fo=
r_spammers.html
>=20
> If the goal of the spammer is higher google pagerank you could just
> force every link outside the wiki to a redirect script something like
> this:
>=20
>  http://phpwiki.sourceforge.net/phpwiki/redirect?http://www.veryniceprodu=
ct.com
>=20
> or using google itself like described here:
>=20
>  http://simon.incutio.com/archive/2003/10/13/linkRedirects
>  http://simon.incutio.com/archive/2004/05/11/approved
>=20
> It looks a bit ugly and sometimes you do want to make normal links,
> but I guess it wouldn't hurt if this was enabled by default. It would
> probably mean a lot less spammers if they knew not to even bother with
> phpwikis.

Redirects are fine as long as they don't naively redirect to any URL
(such as
http://phpwiki.sourceforge.net/phpwiki/redirect?http://www.veryniceproduct.=
com)
This will be abused worse than the sandbox as spammers will search for
wikis that allow open redirection and abuse those sites in an effort to
get around spam filters. For years the anti-spam community has been
working to get sites such as Yahoo to close their open redirectors due
to abuse (a recent example:
http://rd.yahoo.com/UtcUssn/*http://www.deliveryisguranteed.com)

A redirection system such as Shorl or TinyUrl is less prone to abuse, so
if you decide to go with redirection, please consider encoding the
destination url in the redirector to prevent trivial abuse.

Another suggestion is to parse out the URLs in a page (at least those
that allow anonymous editing) and check their domains against the SURBL
(http://www.surbl.org/), taking care to scrape out hostnames and known
rediriectors. The implementation guide at
http://www.surbl.org/implementation.html has more specifics.

Basically, if you find an URL like
http://rd.yahoo.com/*http://www.something.hotbarnyardtonermortgage.ac.uk/en=
largeyourxerox,
you'll want to reduce that to hotbarnyardtonermortgage.ac.uk and do a
DNS lookup for the A record of
hotbarnyardtonermortgage.ac.uk.sc.surbl.org. If that comes back with
127.0.0.2, the URL is suspect.

The SpamAssassin team has been working on supporting this for the
upcoming 3.x release. SA is written in perl but it shouldn't take
much to port the core of their work to PHP. Probably.

Note also that anyone who implements such a thing in a portable fashion
will become a hero of the blog community because they are suffering
worse from link spamming than the wiki community. At least that's what
the Geeklog people told me when I originally suggested this to them. And
no, I don't have a lot of free time to implement this and my PHP skills
are rudimentary at best, especially if you want something portable and
reusable.

Another quick and dirty hack to temporarily foil the bots that detect
and mangle the sandbox is to dynamically change the name/url of the
sandbox to something not so easily guessable (e.g. something different
from SandBox.) It kinda goes against the spirit of a Wiki but there's
little reason to allow the sandbox to be easily linked to or guessed.
Add a serial number to the sandbox URL (alternating between SandBox12,
12SandBox, Sand12Box where 12 is the serial number. Better to md5()
it...) and increment that number every time the sandbox is raked. In
short, make the link difficult to guess programmatically.

hth,

-- Bob

[Phpwiki-talk] Protecting against google rank spam...

[electron <ele...@mg...>]

I like the redirect idea. Plugin here we come....

It might also be an idea for anonymous edits to have to be approved by a
registered user before making the current version of a page.=20

That's not in the spirit of wiki, but this next idea might be:

Expanding on that idea: Based on referrer or user agent, we show a =
version
of the page that was last edited by a real user to the bot and leave the
current version as it is to regular browsers.

Any phpwikis get spammed recently?

-Electrawn


I've stopped 7,726 spam messages. You can too!
One month FREE spam protection at http://www.cloudmark.com/spamnetsig/}

-----Original Message-----
From: php...@li...
[mailto:php...@li...] On Behalf Of Steve
Wainstead
Sent: Monday, June 07, 2004 12:35 PM
To: php...@li...
Subject: [Phpwiki-talk] Wikis: The Next Frontier for Spammers?


Nothing new here except a higher profile for the idea...

http://news.netcraft.com/archives/2004/06/04/wikis_the_next_frontier_for_=
spa
mmers.html

~swain

----
                  http://www.panix.com/~swain/
    "It has all the faults of a photograph." -- David Hockney
----


-------------------------------------------------------
This SF.Net email is sponsored by: GNOME Foundation
Hackers Unite!  GUADEC: The world's #1 Open Source Desktop Event.
GNOME Users and Developers European Conference, 28-30th June in Norway
http://2004/guadec.org
_______________________________________________
Phpwiki-talk mailing list
Php...@li...
https://lists.sourceforge.net/lists/listinfo/phpwiki-talk

Re: [Phpwiki-talk] Wikis: The Next Frontier for Spammers?

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

Dmitry M. schrieb:

> On Mon, Jun 07, 2004 at 10:15:12PM +0200, Reini Urban wrote:
> 
>>Excluding the SandBox (robots.txt) is a very good idea.
> 
> 
> I'm not sure I understand. Why is the SandBox being singled out? It
> seems like pretty much any (unlocked) well-linked page could be abused
> in this way.
> 
> Am I missing something?

Yes, that spammers are very lazy, and typically only edit the SandBox.

Which is a luck for us because we even have a PhpWikiAdministration 
button to rake the sandbox, which can be done periodically and 
automatically.

And the Sandbox is for sure linked from the HomePage, so it gets higher 
google ranks then other pages, which the spammer doesn't know by
a short look (or an automatic script)
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: [Phpwiki-talk] Wikis: The Next Frontier for Spammers?

[Dmitry M. <dm...@la...>]

On Mon, Jun 07, 2004 at 10:15:12PM +0200, Reini Urban wrote:
> Excluding the SandBox (robots.txt) is a very good idea.

I'm not sure I understand. Why is the SandBox being singled out? It
seems like pretty much any (unlocked) well-linked page could be abused
in this way.

Am I missing something?


-D

Re: [Phpwiki-talk] Wikis: The Next Frontier for Spammers?

[Jon <d9...@na...>]

On Mon, Jun 07, 2004 at 01:34:45PM -0400, Steve Wainstead wrote:
> Nothing new here except a higher profile for the idea...
>
> http://news.netcraft.com/archives/2004/06/04/wikis_the_next_frontier_for_spammers.html

If the goal of the spammer is higher google pagerank you could just
force every link outside the wiki to a redirect script something like
this:

 http://phpwiki.sourceforge.net/phpwiki/redirect?http://www.veryniceproduct.com

or using google itself like described here:

 http://simon.incutio.com/archive/2003/10/13/linkRedirects
 http://simon.incutio.com/archive/2004/05/11/approved

It looks a bit ugly and sometimes you do want to make normal links,
but I guess it wouldn't hurt if this was enabled by default. It would
probably mean a lot less spammers if they knew not to even bother with
phpwikis.

-- 
Jon Åslund

Re: [Phpwiki-talk] Wikis: The Next Frontier for Spammers?

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

Steve Wainstead schrieb:

> Nothing new here except a higher profile for the idea...
> 
> http://news.netcraft.com/archives/2004/06/04/wikis_the_next_frontier_for_spammers.html

Excluding the SandBox (robots.txt) is a very good idea.

I did some more work on a new WikiAccessRestrictions plugin, but it's 
not ready yet.

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

Re: [Phpwiki-talk] mysql config.ini something wrong

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

peter polz schrieb:
> Next problem:
> lib/WikiDB/backend/PearDB.php:34: Fatal[256]: Can't connect to database:
> wikidb_backend_peardb: fatal database error
>     €      DB Error: not found
>     €      (Unable to include the DB/.php file for `')
>     €     

Please read and try to understand the error messages.
You still haven't defined a database.

> lib/IniConfig.php:108: Notice[1024]: missing config setting for DEBUG

you haven't defined this either.

> lib/IniConfig.php:218: Notice[8]: Undefined index: dsn

ditto.

> lib/main.php:869: Notice[8]: Use of undefined constant DEBUG - assumed
> 'DEBUG'
> 
> lib/WikiDB/sql.php:14: Notice[8]: Undefined index: dsn
> 
> lib/WikiDB/sql.php:16: Notice[8]: Undefined index: dsn
> 
> lib/WikiDB/backend/PearDB.php:24: Notice[8]: Undefined index: dsn
> 
> /Library/Tenon/PHP/lib/php/DB.php:258: Warning[2]: connect(DB/.php): failed
> to open stream: No such file or directory
> 
> /Library/Tenon/PHP/lib/php/DB.php:258: Warning[2]: connect(): Failed opening
> 'DB/.php' for inclusion (include_path='.:/Library/Tenon/PHP/lib/php')
> 
> 
> lib/WikiDB/backend/PearDB.php:34: Fatal[256]: Can't connect to database:
> wikidb_backend_peardb: fatal database error
>     €      DB Error: not found
>     €      (Unable to inclu
> 
> What is now wrong?
> Regards
> 
> Peter
> 
> 
>>peter polz schrieb:
>>
>>>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?
>>>
>>>;======================================================================
>>>; 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
>>
>>                 ^^^
>>
>>dbt is not a supported database type.
> 
> 
> 


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

[Phpwiki-talk] crash after logging in as user...

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

Just got the latest from cvs and I'm still having php 4.3.6 crash when
loggin in as a user.

If I log in as the admin, things are ok.

With USER_AUTH_POLICY = stacked or strict, when you log in, you get a
'document contains no data' error (equv error on IE).  When you have it set
to old, you get an invalid password and are returned to the login screen, no
crash.

When set to old, it does not apper to be going through the ldap checkPass
function (I put a few echo's in there and they did not show up.

Any clues to start debugging this?

Where does flow go after it leaves the  LDAP checkPass function?  I'm
debugging with echo and find in files, so it's slow going ;-)

Thanks,

John Cole

[Phpwiki-talk] Wikis: The Next Frontier for Spammers?

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

Nothing new here except a higher profile for the idea...

http://news.netcraft.com/archives/2004/06/04/wikis_the_next_frontier_for_spammers.html

~swain

----
                  http://www.panix.com/~swain/
    "It has all the faults of a photograph." -- David Hockney
----

Re: [Phpwiki-talk] mysql config.ini something wrong

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

peter polz schrieb:
> 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?
> 
> ;======================================================================
> ; 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
                   ^^^

dbt is not a supported database type.

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

[Phpwiki-talk] 2004 doctors American directoty,physicians,

[Myles S. <wnm...@ez...>]

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>Untitled Document</title>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859=
-1">
</head>

<body>
EXCLUSIVELY ON CD-ROM. 
<p> The 2004 edition of The American Medical Directory &amp; Physicians <b=
r>
  Guide has just been completed.</p>
<p>physicians, specialists, doctors, licensed doctors, <br>
  board physicians, emergency physicians, 2004 physicians guide, <br>
  2004 physicians directory, physicians contact.</p>
<p> According to many librarians, it is one of the most referenced <br>
  and frequently-used publication in libraries throughout the <br>
  United States. </p>
<p>It is also used by most healthcare professionals and industry <br>
  business development executives.</p>
<p> The American Medical Directory &amp; Physicians Guide contains <br>
  relevant data on over 500,000 physicians in the United States. </p>
<p>Each record is indexed by such features as name, address, phone/fax, <b=
r>
  county, year licensed, type of practice, type of </p>
<p>physician, as well as primary and secondary specialty.</p>
<p> During this introductory offer, the cost of the new directory <br>
  (which is available exclusively on CD-Rom) is $425.00 (reg. $795). </p>
<p>The CD-Rom is in Excel format and is searchable, downloadable, <br>
  and can be used on an unlimited basis.</p>
<p>To order the American Medical Directory &amp; Physicians Guide, <br>
  please print this e-mail, </p>
<p>complete the information below and fax it to 905-751-0199. <br>
  (tel: 905-751-0919).</p>
<p>BONUS OFFER: <br>
  ORDER NOW AND RECEIVE THE AMERICAN <br>
  NURSING HOME DIRECTORY ON CD-ROM <br>
  FREE OF CHARGE. </p>
<p>NAME:</p>
<p>TITLE:</p>
<p>ORGANIZATION:</p>
<p>ADDRESS:</p>
<p>CITY:</p>
<p>POSTAL:</p>
<p>TEL:</p>
<p>FAX:</p>
<p>E-MAIL:</p>
<p>InfoSource Group of Companies is a leading information <br>
  publishing firm with offices throughout North America <br>
  and Europe.<br>
</p>
</body>
</html>