phpwiki-talk

Re: [Phpwiki-talk] italian translation of wiki

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

Great, Marco!

Unless someone else (Arno?, Steve?) particularly wants to handle
this, I can check it into the CVS.

(I.e.: send it to me.)

Jeff
<da...@da...>

In message <200...@ad...>,kp...@ad... writes:
>
>I've terminated the italian translation.
>Now where have I to send the stuff?

[Phpwiki-talk] italian translation of wiki

[<kp...@ad...>]

hi to all,

I've terminated the italian translation.
Now where have I to send the stuff?

ciao,
Marco

Re: [Phpwiki-talk] extranet

[Martin A. B. <mar...@hy...>]

"Martin A. Brooks" wrote:
> Can anyone suggest a workaround/fix?

Here's a diff that should at least part fix this problem:

***************
*** 227,233 ****
  
     if (empty($ScriptUrl)) {
        $port = ($SERVER_PORT == 80) ? '' : ":$SERVER_PORT";
!       $ScriptUrl = "http://$SERVER_NAME$port$SCRIPT_NAME";
     }
     if (defined('WIKI_ADMIN') && !empty($AdminUrl))
        $ScriptUrl = $AdminUrl;
--- 227,234 ----
  
     if (empty($ScriptUrl)) {
        $port = ($SERVER_PORT == 80) ? '' : ":$SERVER_PORT";
!       $proto = ($HTTPS == "on") ? "https" : "http";
!       $ScriptUrl = "$proto://$SERVER_NAME$port$SCRIPT_NAME";
     }
     if (defined('WIKI_ADMIN') && !empty($AdminUrl))
        $ScriptUrl = $AdminUrl;

[Phpwiki-talk] extranet

[Martin A. B. <mar...@hy...>]

Hi

I have an Intranet server setup with PHPWiki which works very well.

I've added an SSL server as a virtualhost which is fed from an rinetd
daemon and the outside world.

<Intranet:443>------<firewall/rinetd>--------Internet

The problem is that the links generated by PHPWiki for WikiLinksLikeThis
are slightly incorrect.

The generated link points to, for example, 
http://intranet:443/wiki/?MyPage

This, of course, generates an error. It should really be:
https://intranet/wiki/?MyPage

Can anyone suggest a workaround/fix?

Thanks

Martin Brooks.

[Phpwiki-talk] modify a name of a page

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

Hello,

  Is there a way to change the name of a page ? Do I need to do this operation
in the database ?

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

Re: [Phpwiki-talk] New to all of this.

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

I'm doing quite a lot, but not submitting to CVS.
Jeff did the last hacks, but made a break.
Steve told us to start somewhen this month...

Richard Kavanagh schrieb:
> The question is how "active" is this group ?. There seems to be little
> activity on soureforge (forum, tasks etc) and the CVS has not been
> touched for quite a while (as far as I can see),
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

[Phpwiki-talk] New to all of this.

[Richard K. <rm...@be...>]

Hello everyone,

Just joined the group having installed PHP wiki on my own site.

I use a MoinMoin wiki at work which has a number of features not 
present in the PHP wiki. Great I though I can practice some PHP and 
incorporate them in to the PHPwiki.

I have started doing so at www.benbun.co.uk/wiki/

The question is how "active" is this group ?. There seems to be little 
activity on soureforge (forum, tasks etc) and the CVS has not been 
touched for quite a while (as far as I can see),

I would like to help with the development oif the PHPwiki, if indeed 
it is still being actively developed.

If it is , how do I get involved.

Thanks,
Richard
-----------------------
www.bebun.co.uk

[Phpwiki-talk] hello all

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

I am still getting set up in sunny Key West, Florida, where I will be
until September. I've been offline for days now, and I am surprised how
nice it is to have a keyboard under my hands again!

I'm paying US$6.60/half hour to surf for the moment, so I won't be able to
catch up on the project quite yet.

In the next few days I should be online again and plunge into things.

cheers
~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

[Phpwiki-talk] Re: phpwiki translation

[Marco M. <kp...@ad...>]

> Hi Marco! I'm putting this on phpwiki-talk since I don't handle the
> translations; I will be very excited to see an Italian version of PhpWiki!

I think i'll work on this weekend on this problem. unfortunatley I was
ill and without a computer for a week. now the situation would be
stabilized.
> Can someone help him with this problem?

a flood of answers? :-)

> p.s. sorry for taking so long to reply, I was in Florida the last week.

np, same for me
-- 
                                                                 .''`.
                                                                : :' :
UNIX makes the people come together                             `. `'
                                                                  `-
                                                            Debian GNU/Linux
                                                                 Powered

[Phpwiki-talk] RE: PHPWiki with Microsoft SQL-Server

[<And...@ba...>]

There was a bug in the InsertPage() function - new version of the library
attached.

 <<mssql.php>> 
Regards, Andrew

>  -----Original Message-----
> From: 	Pearson, Andrew: IT (LDN)  
> Sent:	01 May 2001 16:27
> To:	'sw...@pa...'
> Cc:	'php...@li...'
> Subject:	PHPWiki with Microsoft SQL-Server
> 
> 
> My colleague John Clayton set up PHPWiki for our development team using
> Apache and MySQL on Windows NT 4.  He then left, and I was asked to port
> this to IIS and SQLServer. Please note this is not a reflection of the
> Apache and MySQL products, which were performing the task admirably, but
> had more to do with consistency of our environment. Since PHP does work
> with SQL-Server, the whole migration took about a day. Here are the steps
> I carried out:
> 
> 1. Wrote a sql-server library called mssql.php to reside in wiki\lib.
>  << File: mssql.php >> 
> 2. Added the following clause to wiki\lib\config.php
>    // MS SQLServer settings
>    } elseif ($WhichDatabase == 'mssql') {
>       $WikiPageStore = "wiki";
>       $ArchivePageStore = "archive";
>       $WikiLinksStore = "wikilinks";
>       $WikiScoreStore = "wikiscore";
>       $HitCountStore = "hitcount";
>       $mssql_server = 'servername';
>       $mssql_user = 'wikiweb';
>       $mssql_pwd = 'wikiweb';
>       $mssql_db = 'wiki';
>       include "lib/mssql.php";
> }
> 
> 3. Set $WhichDatabase='mssql' in config.php
> 
> 4. Dumped out the mysql wiki database (mysqldump --user=john
> --host=localhost wiki) and wrote the following perl script to convert to
> sql-server compatible sql
>  << File: translate_mysql.pl >> 
> 
> 5. Loaded the translated db script into SQL-Server and granted relevant
> permissions/logins etc. 
> 
> 6. Set "magic_quotes_sybase=On" in php.ini to handle embedded quote
> characters in strings. This is because SQL-Server, like Sybase, uses ''
> instead of \' within strings to cope with embedded quotes.
> 
> We had some problems initially with the PHP extension dll for sql-server,
> but I installed a newer version from http://www.mm4.de. In fact I unpacked
> their whole php4.0.5-rc1 distribution.
> 
> I make no claims about all this working 100%, but our existing site seems
> to work okay in its new IIS/SQL-Server home :-)
> 
> Andrew Pearson
> Barclays Capital, UK
> 
> 


--------------------------------------------------------------------------------------
For more information about Barclays Capital, please
visit our web site at http://www.barcap.com.


Internet communications are not secure and therefore the Barclays Group
does not accept legal responsibility for the contents of this message.
Any views or opinions presented are solely those of the author and do 
not necessarily represent those of the Barclays Group unless otherwise 
specifically stated.

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

[Phpwiki-talk] PHPWiki with Microsoft SQL-Server

[<And...@ba...>]

My colleague John Clayton set up PHPWiki for our development team using
Apache and MySQL on Windows NT 4.  He then left, and I was asked to port
this to IIS and SQLServer. Please note this is not a reflection of the
Apache and MySQL products, which were performing the task admirably, but had
more to do with consistency of our environment. Since PHP does work with
SQL-Server, the whole migration took about a day. Here are the steps I
carried out:

1. Wrote a sql-server library called mssql.php to reside in wiki\lib.
 <<mssql.php>> 
2. Added the following clause to wiki\lib\config.php
   // MS SQLServer settings
   } elseif ($WhichDatabase == 'mssql') {
      $WikiPageStore = "wiki";
      $ArchivePageStore = "archive";
      $WikiLinksStore = "wikilinks";
      $WikiScoreStore = "wikiscore";
      $HitCountStore = "hitcount";
      $mssql_server = 'servername';
      $mssql_user = 'wikiweb';
      $mssql_pwd = 'wikiweb';
      $mssql_db = 'wiki';
      include "lib/mssql.php";
}

3. Set $WhichDatabase='mssql' in config.php

4. Dumped out the mysql wiki database (mysqldump --user=john
--host=localhost wiki) and wrote the following perl script to convert to
sql-server compatible sql
 <<translate_mysql.pl>> 

5. Loaded the translated db script into SQL-Server and granted relevant
permissions/logins etc. 

6. Set "magic_quotes_sybase=On" in php.ini to handle embedded quote
characters in strings. This is because SQL-Server, like Sybase, uses ''
instead of \' within strings to cope with embedded quotes.

We had some problems initially with the PHP extension dll for sql-server,
but I installed a newer version from http://www.mm4.de. In fact I unpacked
their whole php4.0.5-rc1 distribution.

I make no claims about all this working 100%, but our existing site seems to
work okay in its new IIS/SQL-Server home :-)

Andrew Pearson
Barclays Capital, UK




--------------------------------------------------------------------------------------
For more information about Barclays Capital, please
visit our web site at http://www.barcap.com.


Internet communications are not secure and therefore the Barclays Group
does not accept legal responsibility for the contents of this message.
Any views or opinions presented are solely those of the author and do 
not necessarily represent those of the Barclays Group unless otherwise 
specifically stated.

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

Re: [Phpwiki-talk] Re: PhpWiki- passwords in backup files

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

> We discovered this problem a few months ago and it's been on the task
> list for a while... but in general there's no good solution so far. I
> think .htaccess files are going to be the best route.

why not include a default .htaccess file in the right place, protecting
the right things.  the biggest problem i see is that not all isp's provide
the ability to change things via .htaccess files, and some change the name
of the file used to do this.

> The one thing we can't protect against though is a malicious local
> user. That would require the PhpWiki files to be owned and readable by
> the web server user only, I suppose, or put yourself and the server
> user in a group... we haven't discussed this on the list in some time.

you can protect against this.  the best way to do this is to create the
root phpwiki directory with permissions 2770 and give group write to all
files/dirs below it.  now make the web server user own everything and
create a group that people must belong to in order to manually modify
files.  ideally all data and config files should be outside of the
document root as well.

we used to do this at the last isp i worked at to protect or document root
on our netapps.  so long as no one fat fingers a chmod/chown it works
great. :)

adam.

[Phpwiki-talk] ctags, etags

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

The newest version of ctags has native PHP support, something that I've
wished for for a long time:

http://ctags.sourceforge.net/

the command:

ctags -e `find . -name "*.php"`

should work for Emacs users.

~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

[Phpwiki-talk] Better checking for database support

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

I've been kicking this idea around for a long time, but since it's a minor
matter it hasn't bubbled up. Why not do this sort of thing:

<?php

if (function_exists('dba_open')) {
  echo "dba_open exists<p>";
}

if (function_exists('dbmopen')) {
  echo "dbmopen exists<p>";
}

if (function_exists('mysql_pconnect')) {
  echo "mysql_pconnect exists<p>";
}

if (function_exists('pg_pconnect')) {
  echo "pg_pconnect exists<p>";
}


?>


to test to see if dbmlib, dbalib, etc. support is available? Wouldnt' this
at least be better for the initial out of the box installation?

~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

[Phpwiki-talk] Re: PhpWiki- passwords in backup files

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

Hi Eric!

Thanks for reminding us... and I never thought of looking for file.php~
files! What will users think of next?

We discovered this problem a few months ago and it's been on the task list
for a while... but in general there's no good solution so far.

http://sourceforge.net/pm/task.php?group_project_id=7691&group_id=6121&func=browse

I think .htaccess files are going to be the best route. The one thing we
can't protect against though is a malicious local user. That would require
the PhpWiki files to be owned and readable by the web server user only, I
suppose, or put yourself and the server user in a group... we haven't
discussed this on the list in some time.

~swain

p.s. sorry for the delay in replying, I was in Florida for a week.

On Mon, 23 Apr 2001, Eric Zager wrote:

> First let me say that I'm very impressed with PhpWiki and Wikis in
> general.  I haven't used them very much yet, but it was astonishingly easy
> to set up PhpWiki and get it going.
>
> Maybe the following is an obvious danger, but in case no one's pointed it
> out-- the file lib/config.php has plaintext authentication info for the
> database.  In principle, a web user could get that info by just typing the
> URL for lib/config.php directly.  From the little experimenting I've done,
> that doesn't actually present a problem because the PHP engine tries to
> process that script.  But many editors create backup files,
> lib/config.php~ for emacs.  If you type the URL for the backup file, the
> PHP engine is not invoked and the user can see the backup file.
>
> You can get to the backup file at Sourceforge this way, but it looks like
> it's just the default without any sensitive info (until someone edits the
> file a second time).
>
> I'm not sure what the best solution is.  I'm not a big PHP person, I've
> only tinkered a little.  One idea is to add a .htaccess file that denies
> access to the most common backup files.
>
> Maybe there's no general solution, but a warning to the admin might be
> a good idea.
>
>
> - Eric
>

---
                  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

[Phpwiki-talk] Re: phpwiki translation

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

Hi Marco! I'm putting this on phpwiki-talk since I don't handle the
translations; I will be very excited to see an Italian version of PhpWiki!

Can someone help him with this problem?

cheers
~swain

p.s. sorry for taking so long to reply, I was in Florida the last week.

On Sun, 22 Apr 2001, Marco Milanesi wrote:

> Hi Steve,
>
> 	I'm trying to translate phpwiki in Italian.
> here is where I am:
>
> - Added to locale/translate.sh: ALL_LINGUAS="nl es de sv it"
> - executed locale/translate.sh:
>
> [bhead@milcohouse~/public_html/wiki$] locale/translate.sh
> locale/po/nl.po: warning: charset "8859-1" is not a portable encoding name
>                  warning: charset conversion might not work
> ........ done.
> locale/po/nl.po: warning: charset "8859-1" is not a portable encoding name
> 				 warning: charset conversion might not work
> ........ done.
> ........ done.
> ........ done.
> ........ done.
> [bhead@milcohouse~/public_html/wiki$]
>
> - Changed $LANG to 'it' in lib/config.php
> - pointed lynx at the local wiki URL displaying the english version.
>
> I'm surely missing something...
>
> ciao,
> Marco
>
> PS: anyway congrats! PhpWikiIsCool ;)
>
> --
>                                                                  .''`.
>                                                                 : :' :
> UNIX makes the people come together                             `. `'
>                                                                   `-
>                                                             Debian GNU/Linux
>                                                                  Powered
>

---
                  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

[Phpwiki-talk] Re: PHPWiki

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

Hi Richard! Sorry for the delay in responding; I've been in Florida for
the last week (counting ballots. No, just kidding ;-)

You can see a list of the things we want to add to PhpWiki here:

http://sourceforge.net/pm/task.php?group_project_id=7691&group_id=6121&func=browse

Not all of them will necessarily be added, but if PhpWiki is ever going to
be "feature complete" then most of them should make it.

If you wish to contribute to the project that would be great. However if
you modify a version of PhpWiki from the 1.2 release we might not be able
to add your changes; the code base in 1.3 has changed quite a lot... try
looking at a nightly build:

http://phpwiki.sourceforge.net/nightly/phpwiki.nightly.tar.gz

Thanks, and let me know what you think!

~swain

On Wed, 25 Apr 2001, Richard Kavanagh wrote:

> Hi,
>
> I have recently been introduced to te WIKI concept and have been assessing a number of the WIKI clones
> available on the web (principally TWIKI, MOINMOIN and PHPWIKI).
>
> We are trialling the MoinMoin wiki at my current company (they don't use PHP) as an internal documentation
> repository. I personally have installed the latest public release of PHPWiki on my own server so that I  can
> play around with it (www.benbun.co.uk/phpwiki).
>
> I have chosen the PHP version as I know a bit of PHP (but little PERL or Python as used by the others).
>
> THere are a number of features available within the MoinMoin and TWIKI WIKI's that are not in the PHP
> version. I intend to replicate this functionality to the PHPWIKI over the next few weeks/months.
>
> The questions are:
>
> - are you open to new developers joining the main development of PHPWIKI. ?.
> - are you interested in any changes I make ?.
> - if yes to the above - how do I join ?.
>
> Thanks.
> Richard.
>

---
                  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

Re: [Phpwiki-talk] $SCRIPT_NAME variable in config.php returns the wrong path

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

>In the file config.php, there is a reference to the $SCRIPT_NAME
>environment variable. This variable should I believe hold the location
>of the index.php file? In my case however it comes back with
>\cgi-bin\php.cgi.

>Would it not therefore be better to use a different environment
>variable? $PATH_INFO works in my case, but I don't know if it works for
>all cases. I think the main difference is that some service providers
>use the CGI Interpreter, and some use the Apache module.

$PATH_INFO doesn't work when mod_php is used (PHP as Apache module).
(In that case, it only contains the "tail" of the URL --- the part 
after that which specifies the script name.)

There are (at least) three basic PHP environments:

  1. Apache module (mod_php)  (probably the most common setup.)

  2. CGI interpreter (or "action handler") like you've got.

  3. Straight CGI using a standalone PHP interper.  (PHP script is marked
     executable and has a first line like "#!/usr/local/bin/php" on
     unix systems.)

There isn't a simple way to get the name of the script which works in
all three cases.

Furthermore, while one can auto-detect whether or not PHP is being
run as an apache module, it is difficult to reliably differentiate
between case 2 and 3.  (Note that in cases 2 and 3, it is (for the
most part) the http daemon, and not PHP which determines which
environment variables get set, and what values they get...)

PhpWiki probably could be fixed to auto-detect the correct setting
for SCRIPT_NAME in a few more cases than it does now, but I'm not sure
it's worth it.   It's more straightforward just to manually set
SCRIPT_NAME is those cases that need it.

Jeff

[Phpwiki-talk] $SCRIPT_NAME variable in config.php returns the wrong path

[Colm W. <co...@fl...>]

Hi,

In the file config.php, there is a reference to the $SCRIPT_NAME =
environment variable. This variable should I believe hold the location =
of the index.php file? In my case however it comes back with =
\cgi-bin\php.cgi .=20
=20
I have copied your PHP Wiki onto my service provider's server, to which =
I have ftp access along with some online database tools. Thus I can not =
change any of the servers internal settings. I have seen discussion =
threads where others report the same problem.

Would it not therefore be better to use a different environment =
variable? $PATH_INFO works in my case, but I don't know if it works for =
all cases. I think the main difference is that some service providers =
use the CGI Interpreter, and some use the Apache module.

Regards,
Colm Ward

Re: [Phpwiki-talk] Re: Install Question

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

On Fri, Apr 06, 2001 at 08:19:02AM -0700, Adam Shand wrote:
> 
> side question ... i poked around nomicwiki and is the sitemap feature a
> standard phpwiki feature?

No. You can have the source if you want, but I think most people were 
concerned about it taking up too much processing time on a large Wiki, as
it is regenerated on the fly.

Is anyone working on ways to visualise a PhpWiki? I liked some of the stuff
I saw at WardsOriginialWiki.

Malcolm

-- 
Malcolm Ryan - mal...@cs... - http://www.cse.unsw.edu.au/~malcolmr/
  AI Dept, CSE, UNSW, Australia, Phone: +61 2 9385-6906 Fax: +61 2 9385-4936

           "He causes his sun to rise on the evil and the good,
           and sends rain on the righteous and the unrighteous." - Matt 5:45

Re: [Phpwiki-talk] page too big

[Sandino A. <sa...@sa...>]

Didier Bretin wrote:

> Hello,
>
> On Thu, Apr 19, 2001 at 09:17:56PM -0400, Steve Wainstead wrote:
> > On Thu, 19 Apr 2001, Reini Urban wrote:
> >
> > > click on EditText
> Oops :o). I thought that I can't do this because it is a generated page.
> So I do it :o)))
>
> > Also, I think you've run into a problem with Postgresql that's been a=
round
> > a long time. From the INSTALL.pgsql:
> >
> > "Also note that Postgresql by default has a hard limit of 8K per
> > row. This is a Really Bad Thing. You can change that when you compile
> > Postgresql to allow 32K per row, but supposedly performance
> > suffers. The 7.x release of Postgresql is supposed to fix this."
> Ok :o).
> Apparently I'm with a 7.x release ... so the problem is not resolve
> in Postgres .... Hummmm...... I will search at Postgres 's site.
>

The problem is supposed to be resolved in 7.3.

--
Sandino Araico S=E1nchez
Si no eres parte de la soluci=F3n, entonces eres parte del precipitado.

Re: [Phpwiki-talk] page too big

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

Hello,

On Thu, Apr 19, 2001 at 09:17:56PM -0400, Steve Wainstead wrote:
> On Thu, 19 Apr 2001, Reini Urban wrote:
> 
> > click on EditText
Oops :o). I thought that I can't do this because it is a generated page.
So I do it :o)))

> Also, I think you've run into a problem with Postgresql that's been around
> a long time. From the INSTALL.pgsql:
> 
> "Also note that Postgresql by default has a hard limit of 8K per
> row. This is a Really Bad Thing. You can change that when you compile
> Postgresql to allow 32K per row, but supposedly performance
> suffers. The 7.x release of Postgresql is supposed to fix this."
Ok :o).
Apparently I'm with a 7.x release ... so the problem is not resolve
in Postgres .... Hummmm...... I will search at Postgres 's site.

Thanks.

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

Re: [Phpwiki-talk] page too big

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

On Thu, 19 Apr 2001, Reini Urban wrote:

> click on EditText

Also, I think you've run into a problem with Postgresql that's been around
a long time. From the INSTALL.pgsql:

"Also note that Postgresql by default has a hard limit of 8K per
row. This is a Really Bad Thing. You can change that when you compile
Postgresql to allow 32K per row, but supposedly performance
suffers. The 7.x release of Postgresql is supposed to fix this."

~swain

>
> Didier Bretin schrieb:
> >   I'm with the 1.2.0 version. Apparently now my page RecentChanges is too big and I got
> > the error:
> > How can I do to empty this page ?
> --
> Reini Urban
> http://xarch.tu-graz.ac.at/home/rurban/
>
> _______________________________________________
> 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

Re: [Phpwiki-talk] installation

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

>Now the mysql.sock is not in tmp, it is in /var/lib/mysql/
>
>Where is the problem: at php, at mysql at apache or something in
>phpwiki????

I'm not exactly sure why the defaults aren't correct in your case.
My guess is that you can fix it in the mysql config file /etc/my.cnf,
with something like:

  [client]
  socket = /var/lib/mysql/mysql.sock


Failing that, to get PhpWiki working,
you can set the path to the socket explicitly in the PhpWiki config 
file.   E.g., in lib/config.php, around line 85 (assuming PhpWiki 1.2.0),
set:

  $mysql_server = 'localhost:/var/lib/mysql/mysql.sock';

Jeff

[Phpwiki-talk] installation

[Szilard B. <sz...@in...>]

Hi,
After installing  phpwiki and using it the first time I got the
following error message:

Warning: Can't connect to local MySQL server through socket
'/tmp/mysql.sock' (111) in
/home/bokros/pub/phpwiki/lib/mysql.php on line 34
WikiFatalError
Cannot establish connection to database, giving up.
MySQL error:

Now the mysql.sock is not in tmp, it is in /var/lib/mysql/

Where is the problem: at php, at mysql at apache or something in
phpwiki????
Where should I set the path for the sock?

Thanks if any answer
Szilard