Hi Joseph!
> 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.
True, I forgot about that way of assigning directorys to hostnames. Damn. :)
> 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?
But we use the Path setting also many times on including the templates/plugins
or the local configuration -- those always need to be read from the "real"
directory, not the shared one. The easiest way would be to create two directory
paths serendipityPath and serendipityLibraryPath...
> Any ideas? I suppose we could try some variation on
> $_SERVER['PATH_TRANSLATED'].
Hm, I haven't yet tested if that variable is set on those occasions...
> 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.
That would be great!
Thanks and regards,
Garvin.
|