E
emsol
Guest
Hi,
Scenario...
Customer moves from a Windows server (running inspanel) to a plesk 7 Windows server and his site now wont work due to the paths being different.
Reason seems to be related to his includes - previousley, the site was setup with "enable parent paths" and uses "include virtual" statements for all its include files.
When trying to run the site on the Plesk server it comes up with errors that it cant find the files - even with "enable parent paths" set to on.
One thing I notice about the old server in comparison with the plesk one is that the site was setup in IIS6 as a username rather than a domain name - I cant actually see in the site settings where the domain name itself is pointed at the local user folder.
Should I get the customer to change all his include statements to "include file" instead - and use relative paths ? Or is there a simple way of making his virtual includes work ?
I'm mostly a Linux person and still learning IIS so any help with this would be greatly appreciated.
Scenario...
Customer moves from a Windows server (running inspanel) to a plesk 7 Windows server and his site now wont work due to the paths being different.
Reason seems to be related to his includes - previousley, the site was setup with "enable parent paths" and uses "include virtual" statements for all its include files.
When trying to run the site on the Plesk server it comes up with errors that it cant find the files - even with "enable parent paths" set to on.
One thing I notice about the old server in comparison with the plesk one is that the site was setup in IIS6 as a username rather than a domain name - I cant actually see in the site settings where the domain name itself is pointed at the local user folder.
Should I get the customer to change all his include statements to "include file" instead - and use relative paths ? Or is there a simple way of making his virtual includes work ?
I'm mostly a Linux person and still learning IIS so any help with this would be greatly appreciated.