change the root for subsequent domains.

[calmasacow]

Ok I have a windows 2008 R2 Server with Plesk 11.0 on it and The primary domain was created during the initial setup.

the root of this site is C:\inetpub\vhost\"InitialDomainName.com"

Now inside of that I can see all of the goodies the httpdocs and the httpsdocs everything life is good.

so I add a second domain and it creates C:\inetpub\vhost\"SecondDomainName.com"

but then inside of C:\inetpub\vhost\"InitialDomainName.com" it creates a folder called "SecondDomainName.com"

and that folder links to C:\inetpub\vhost\"SecondDomainName.com"\httpdocs

and the only thing I can give people access is that linked folder not C:\inetpub\vhost\"SecondDomainName.com"

Is there any way to change this behavior? what if I need to access C:\inetpub\vhost\"SecondDomainName.com"\httpsdocs of any of the other domain level folders for that domain? Currently I can't. surley there is a way around this. do I have to create a webspace for each site to do this? would this mean I have to also create a separate admin account for each domain to to do this and lose all ability to centrally manage all of the domains?

Update:

So after uploading the contents to the "SecondDomainName.com" it looks that subfolder C:\inetpub\vhost\"InitialDomainName.com"\"SecondDomainName.com" is where all of the files have gone. The directory structure at C:\inetpub\vhost\"SecondDomainName.com" seems to server no purpose whatsoever.

 

[C]

oh your opinion or that. I support you

 

[calmasacow]

So does anyone from parallels actually view these forums or what? It seems like 90% of these posts just never get a solution.

 

[balltongu]

It seems that there is one person, Igor, that replies to these sometimes. Overall I'm getting pretty disheartened by this product - we have an older grandfathered license so I don't think we're getting hosed as badly as new customers are, however are some of you really paying upwards of $100/month with no support contract and then having to pay at least $70 per incident?

 

[balltongu]

Also to speak to your original question, when I first saw that behaviour I couldn't figure out what was going on, it makes no sense why they do what they are doing. I've got a list of "things that drive me crazy about Plesk" and thanks to your post it reminded me to add this one.

 

[PavelV]

I will try to explain why is this so confusing and what we have done to fix this.

In Plesk 11.0 every domain (no matter, is this main domain for subscription or addon domain) has its own directory c:\inetpub\vhosts\domain.com.
This directory for main domain (domain specified during subscription creation) contains whole content for subscription. So c:\inetpub\vhosts\initialdomain.com contains HTTP content for initialdomain.com, logs for initialdomain.com, content for web users, content of anonymous FTP, generated web statistics pages and so on.
When you are adding addon domain (SecondDomainName.com in your case) its HTTP content is also placed inside your subscription root (or webspace root) inside c:\inetpub\vhosts\InitialDomainName.com\SeconDomainName.com by default (but you can specify any directory inside your webspace root).

So why do we create c:\inetpub\vhosts\SecondDomainName.com with its own structure, with httpdocs directory etc? This folder contains only auxillary information for this second domain. Some information was placed inside this folder automatically, but never used by Web Server. You should fully ignore its content. c:\inetpub\vhosts\SecondDomainName.com\httpdocs contains just default extracted skeleton of site. IIS is not configured to look into this folder. Only generated web statistics for addon domain is placed inside this location in Plesk 11.0.

We understand, that this is a bit confusing, so we have removed all references to these folders in our upcoming 11.5 version. When you create addon domain addon.com in 11.5 there is no folder "c:\inetpub\vhosts\addon.com" with some garbage. Web content of addon.com is placed inside folder specified by you inside your webspace root, for example c:\inetpub\vhosts\InitialDomainName.com\addon.com.

Thank you for your feedback. I hope that my explanations revealed your questions about confusing behavior in Plesk 11.0.