The Include file ‘../include/include.asp’ cannot contain ‘..’ to indicate
the parent directory.
I’ve looked up the problem and apparently it is a setting in IIS. I found the following advice:
This is to do with the ‘Enable parent paths’ option not
selected. This can be found out by:
Launching Internet Information Services Manager
Right clicking either Default Web Site or on the virtual
directory
In the website properties click the Virtual Directory tab
Click configuration under the Application Settings section
Click App Options and check the ‘Enable parent paths’
tickbox (see screen shot below).
So it this something JodoHost have done on purpose? Or can it be enabled?
From an administration point of view, one would think parent paths would be turned on by default, since it appears to get turned on manually by anyone who asks for it (or asks why it doesn’t work after spending time trying to use them). And those that don’t ask for it obviously are not using it anyway.
I’ll have that put on our signup page as well as send out an email to existing customers. That’s a valid point you brought up and we wouldn;t want customers to waste their time experimenting
[QUOTE=Yash]
I’ll have that put on our signup page as well as send out an email to existing customers. That’s a valid point you brought up and we wouldn;t want customers to waste their time experimenting
[/QUOTE]
It would indeed be very helpful if you either manage to have it turned on as default, or give users an option to turn it on themselves rather than through the support ticket system, which I believe should be used for ‘trouble’ rather than routine stuff.