I made this as a feature request on the feedback system. But that was 2 days ago and it's still sitting in moderation. Never know if anyone ever pays attention to the feature request system. Never been a huge fan of feature request features, because it doesn't seem to garner as much attention and discussion as forum posts.
A lot was made with changing the DocumentRoot for subdomains some versions back. The create a Subdomain now pops up a menu asking the user what they want to use for their Subdomain's DocumentRoot. I'm more of a fan of giving end users less options, because the more options you give them the more likely they are to mess something up.
I realize some server administrators may not feel that way and may want to give end users the most control. I just don't happen to be one.
I'd prefer an option where the server administrators can define what options they want to show to end users for subdomain DocumentRoots. Or to just remove the options entirely and set the subdomain DocumentRoot to /home/%user%/domains/%subdomain%/public_html so that the end user has no control of it.
If end users aren't given any option, then they learn to live with the option that is provided. If they must, absolutely have to have a subdomain's DocumentRoot inside another domain's DocumentRoot, they can contact us (the webhosting provider) and we'll set a symlink accordingly. But I doubt many end users will want anything different than what is provided.
I'm a big fan of Occam's Razor in the sense of giving users the least number of options that are really necessary. The issue with the current system is that end users will click anything. So they may have one subdomain set in one DocumentRoot format and another subdomain in another format. Then they get confused as to where the content is for each subdomain. Restricting this to just a single path would seem to be best.
In the interim, I'll probably just modify the virtualhost templates to always set the DocumentRoot to /home/%user%/domains/%subdomain%/public_html regardless of what option the user actually selects. Not a great solution, but it keeps things simple. And I prefer simple things for my clients.
A lot was made with changing the DocumentRoot for subdomains some versions back. The create a Subdomain now pops up a menu asking the user what they want to use for their Subdomain's DocumentRoot. I'm more of a fan of giving end users less options, because the more options you give them the more likely they are to mess something up.
I realize some server administrators may not feel that way and may want to give end users the most control. I just don't happen to be one.
I'd prefer an option where the server administrators can define what options they want to show to end users for subdomain DocumentRoots. Or to just remove the options entirely and set the subdomain DocumentRoot to /home/%user%/domains/%subdomain%/public_html so that the end user has no control of it.
If end users aren't given any option, then they learn to live with the option that is provided. If they must, absolutely have to have a subdomain's DocumentRoot inside another domain's DocumentRoot, they can contact us (the webhosting provider) and we'll set a symlink accordingly. But I doubt many end users will want anything different than what is provided.
I'm a big fan of Occam's Razor in the sense of giving users the least number of options that are really necessary. The issue with the current system is that end users will click anything. So they may have one subdomain set in one DocumentRoot format and another subdomain in another format. Then they get confused as to where the content is for each subdomain. Restricting this to just a single path would seem to be best.
In the interim, I'll probably just modify the virtualhost templates to always set the DocumentRoot to /home/%user%/domains/%subdomain%/public_html regardless of what option the user actually selects. Not a great solution, but it keeps things simple. And I prefer simple things for my clients.
