|
From: Joseph T. <jt...@dr...> - 2004-04-11 17:24:31
|
I think that this is frequenly the case: If you want to install it under a user directory (My test setup is at http://www.dragonstrider.com/~jtate/serendipity for example). If your web hosting company provided you space at http://www.example.com/foo/bar, but used Directory directives in httpd.conf rather than a virtual server it would fail for you. The return value I replaced showed /var/www/html/home/jtate/public_html/serendipty as the local dir. Isn't /usr/local/lib/php/s9y the desired path for serendipityPath if that's where serendipity_config* and the like are located? Several places in the code we include $serendipity['serendipityPath'] . "foo.php". I guess I don't see what the problem is: Why is returning /usr/local/lib/php/s9y a bad thing? Any ideas? I suppose we could try some variation on $_SERVER['PATH_TRANSLATED']. I'll be happy to come up with a test script with a bunch of possible solutions that we could all run to see which gives the correct response. Joseph Garvin Hicking wrote: > Hi Joseph! > > >>Fixed a bug in the installer if the blog is not in a subdir of apache's Document >>root. Garvin, if there's a reason that you canged this, speak up. > > > Yes, there is a reason: > > When using the shared library setup, the _FILE_ variable points to the > /usr/local/lib/php/s9y path instead of the directory where you are running s9y > from. So your patch breaks the shared setup. > > I wonder in which case s9y is not installed in a document_root, does this even > exist? I think the patch breaks more than it does good, so I vote for either > restoring the old way for our 0.6 release or think of how we can get both ways > to work. > > I'm currently very busy with other stuff, so maybe one can come up with a solution? > > Regards, > Garvin. > |
