T
tobinharris
Guest
Hi there,
I have just set up the first and only website on Plesk (Windows 2003 Server). I realised that Plesk creates a virtual folder for each site, which causes problems with ASP and Virtual directories. For example:
The following include is now broken
<!--#include virtual="/includes/db.asp"-->
This is a real pain becuase to get around it I have to do something like
<!--#include virtual="/mysite.com_non_ssl/includes/db.asp"-->
I know I can use the <!--#include file...--> directive but the site is massive and it's a real pain! Does anyone know how to get around this?
Kind Regards,
Tobin Harris
P.S - Don't know if this is relevant, but I noticed that the "Micorosoft ASP Support" checkbox in the domain setup is disabled, saying that the component was not installed. ASP.NET was however. I don't know if this makes a difference in how Virtual roots are handled, but I wouldn't have thought so.
I have just set up the first and only website on Plesk (Windows 2003 Server). I realised that Plesk creates a virtual folder for each site, which causes problems with ASP and Virtual directories. For example:
The following include is now broken
<!--#include virtual="/includes/db.asp"-->
This is a real pain becuase to get around it I have to do something like
<!--#include virtual="/mysite.com_non_ssl/includes/db.asp"-->
I know I can use the <!--#include file...--> directive but the site is massive and it's a real pain! Does anyone know how to get around this?
Kind Regards,
Tobin Harris
P.S - Don't know if this is relevant, but I noticed that the "Micorosoft ASP Support" checkbox in the domain setup is disabled, saying that the component was not installed. ASP.NET was however. I don't know if this makes a difference in how Virtual roots are handled, but I wouldn't have thought so.