View Single Post
  #10  
Old 3rd July 2006, 10:33
TheRudy TheRudy is offline
Senior Member
 
Join Date: Dec 2005
Posts: 216
Thanks: 1
Thanked 7 Times in 5 Posts
Default

Quote:
Originally Posted by till
It might be the way cPanel manages subdomains,
Not the only CP that does that, actually most of them do this. When you create new subdomain, new folder with the same name as subdomain is created. Yes, i added that sub_ prefix which can be revmoed of course.

Quote:
Originally Posted by till
but this does not mean that anyone wants subdomains to work this way
Not everyone but a lot of people especially those people who are coming from CP's like cPanel,...

Quote:
Originally Posted by till
as ISPConfig implements it with the possibility to have more then one website per customer. For example most poeple here are asking to set a subdomain to a directory of their choice and not to a static subdirectory under the main web directory as this does not add real benefit to the current ISPConfig implementation with mod_rewrite (you can use mod rewrite that the URL in browser dies not change, this results in the same behaviour then your implemamtation).
You talking about adding new co-domain and Forward it to folder feature? Well that doesn't really work for me. What happens if the company doesn't want to offer mod_rewrite to customers? Plus i might be wrong but, to quote falko from some other thread about subdomains:
Quote:
If you have a web site www.example.com with a folder test in it, and you then create the Co-Domain test.example.com with a forward to test, then people can type in test.example.com in their browser's address bar, but the address will then switch to www.example.com/test. You cannot change this behavour, you have to accept it.
In other words, for a subdomain to work with new folder under mains and WITHOUT redirecting from 'subdomain.domain.tpl' to 'www.subdomain.tpl/folder', you would have to do some manual changes to the rules and stuff. Also from another thread about subdomains. Or was this fixed or did i understand it wrong?

Quote:
Originally Posted by till
Please ask me for any development related questions and not Falko.
Fully noted

Quote:
Originally Posted by till
I think there are two problems with the solution in your example screenshots, 1) we dont have space for another tab, (in your screenshot the SSL tab is not enabled) so it might be better to add the subdomain list on the same tab then the co-domains.
Right, didn't know about SSL as yes, i don't use it. Adding it under co-domains will probably solve this.

Quote:
Originally Posted by till
The way I prefer the implementation is to add a checkbox or option field to the co-domain settings where the type of subdomain can be selected. Either as rewrite rule like ISPConfig implements it now or as separate vhost like you proposed it.
Don't quite get this to be honest. Why not just simply moving subdomains tab inside co-domains. Then you would have for example on top subdomains and below co-domain stuff. Why checkbox or option field?

Don't get me wrong here but i would just like to view a CLEAR option for subdomains where even a non-expert can add it without asking anyone a single question. Let's face it, that is not possible now using co-domains and forward folder cause people will look for 'subdomains' name/title. Plus if cPanel and other CP's have it, why not also add it to ISPConfig? I mean its more of a plus for ISPConfig to have 3 ways of dealing with subdomains (mod_rewrite, new account, vhosts). Now that is something not a lot of CP's have! Well even if you guys don't like it or think its stupid, i'll probably add this feature for my ISPConfig.. I want my customers to add subdomains on their own without any support with ability to limit the number of subdomains per domain name..
Reply With Quote