On 9/5/07, Maria McKinley [EMAIL PROTECTED] wrote:
This makes sense. I am sure I did not assign variables correctly, as
it was not clear to me from the instructions exactly how to do this. I
am trying to get pmwiki to look in a different directory
(/var/www/wikifarm/maria) for everything it
On Tue, Sep 04, 2007 at 10:43:49PM -0700, Maria McKinley wrote:
Object is not the name of a directory.
Php writes Object when an object is sent to the output.
$WikiDir is an object of the class PageStore
$WorkDir is a string
Perhaps you interchange these variables in some place.
On 9/5/07, Patrick R. Michaud [EMAIL PROTECTED] wrote:
On Tue, Sep 04, 2007 at 10:43:49PM -0700, Maria McKinley wrote:
Object is not the name of a directory.
Php writes Object when an object is sent to the output.
$WikiDir is an object of the class PageStore
$WorkDir is a string
Maria McKinley wrote:
On 8/28/07, Guillermo Calderon - INCO [EMAIL PROTECTED] wrote:
Maria McKinley wrote:
It would be great if they could create the
directory that includes all of these customizations in their own home
directory, and the web server reads these, but creates the wiki files
on
Object is not the name of a directory.
Php writes Object when an object is sent to the output.
$WikiDir is an object of the class PageStore
$WorkDir is a string
Perhaps you interchange these variables in some place. ($WikiDir is
used when $WorkDir is expected)
This makes sense. I am sure
On 8/28/07, Guillermo Calderon - INCO [EMAIL PROTECTED] wrote:
Maria McKinley wrote:
It would be great if they could create the
directory that includes all of these customizations in their own home
directory, and the web server reads these, but creates the wiki files
on the web server
Maria McKinley wrote:
It would be great if they could create the
directory that includes all of these customizations in their own home
directory, and the web server reads these, but creates the wiki files
on the web server itself. Has anyone else tried to do this or have any
ideas on how
On 8/28/07, Guillermo Calderon - INCO [EMAIL PROTECTED] wrote:
Maria McKinley wrote:
It would be great if they could create the
directory that includes all of these customizations in their own home
directory, and the web server reads these, but creates the wiki files
on the web server
On 8/27/07, Maria McKinley [EMAIL PROTECTED] wrote:
Ok, not so many takers on that question. Let's make it simpler. Is
wiki.d the only directory that the server writes to for publishing on
the web? The rest of the directories are all configurations,
documentation and other things that the web
On 8/27/07, Ben Wilson [EMAIL PROTECTED] wrote:
On 8/27/07, Maria McKinley [EMAIL PROTECTED] wrote:
Ok, not so many takers on that question. Let's make it simpler. Is
wiki.d the only directory that the server writes to for publishing on
the web? The rest of the directories are all
On 8/27/07, Tegan Dowling [EMAIL PROTECTED] wrote:
Directories written to:
wiki.d
uploads (when uploading enabled)
Directories necessary for web access:
pub
All other directories are private.
Also, depending on your configuration,
Directories written to could include
cache
Hi there,
I am having difficulties setting up a wiki farm, and I suspect the
problems has to do with where/how the php files that the web server
writes are put. When you create the directory for your additional wiki
and write the index.php file, is this directory you just created where
the server
If you've got: Example/index.php, the wiki files go to Example/wiki.d/
Try to make the wiki.d directory yourself and set universal write
permissions.
Maria McKinley wrote:
Hi there,
I am having difficulties setting up a wiki farm, and I suspect the
problems has to do with where/how the php
So, for security reasons we have traditionally mounted home
directories via nfs on our web server read-only (so unfortunately just
making Esample/wiki.d/ ourselves with universal write permissions
doesn't help). This worked fine for normal web pages; users edited
their own pages from their
14 matches
Mail list logo
