Posted by shimmyshack on 04/26/07 17:36

On Apr 26, 3:17 pm, Schraalhans Keukenmeester <bitbuc...@invalid.spam>
wrote:
> Rik wrote:
> > Schraalhans Keukenmeester wrote:
> >> Rik wrote:
> >>> Schraalhans Keukenmeester wrote:
> >>>> php_value include_path ".|../includes"
>
> >>>> (include_path='.:../includes')
> >>> If a unix box, the colon seems correct (windows would have a semicolon).
> >>> I've never seen a pipe use for this though, but that might be my lack
> >>> of OS knowledge and environmental variables.
>
> >> The pipe was a typo, alas. If only it were so easy, Rik.
>
> > Wish it was...
>
> >> Thanks for your
> >> keen eye though! No news from my provider either. WEIRD!
>
> > What happens if you try to include it specifically? Does that work or
> > does that give a more clear error?
>
> No matter what I try, just the filename, or including the relative or
> even full path to the include file, same error, no further specification
> of why this happens.
>
> (Helpdesk people can be really annoying, you tell them you have a
> working solution with include files outside httpdocs which you'd like to
> work for subdomains as well. The reply after two working days: "You
> can't include files outside your httpdocs on the server, that's why it's
> not working." Sigh!!! Guns please!)

it does sound rather as though your setup there is non-standard, it
stragely uses .htaccess to fiddle with include paths, when of course
you should handle the environment within your app.
i wonder if it isnt because there are symbolic links which are
resolving to be outside the openbase dir restriction.

my advice: name and shame your host with its bad customer service - to
me it sounds like http://1and1.co.uk who are also notorious for
getting back to you after weeks only to have misunderstood what you
asked, and insist on telling you something along the line of "its your
browser settings" which means I just dont bother reading their
replies!

after youve named and shamed them, consider moving to somewhere wher
you are in control of your environment, which doesnt depend on
architechtural restrictions, which after all wont work on IIS etc...
are on apache with htaccess disallowed!

[Back to original message]