Add new domain with 'Share document root' disabled by default
Transitioned to Case
Right now, by default this option is enabled so it creates an alias.
This should be disabled by default, or at least there should be a configurable global option for it's state by default.
I like this idea 
cPanel, WebHost Manager and WHM are registered trademarks of cPanel, L.L.C. for providing its computer software that facilitates the management and configuration of Internet web servers.
Creating alias domain by default in the domains function, when you don't have "addon domain" function(creating addon domains), doesn't make any sense and only confuses users. If someone can explain the logic behind that i would appreciate it but currently i can't see any logic about that. I really hope this is fixed by changing the default behavior or returning the function "Addon domains".
Creating alias domain by default in the domains function, when you don't have "addon domain" function(creating addon domains), doesn't make any sense and only confuses users. If someone can explain the logic behind that i would appreciate it but currently i can't see any logic about that. I really hope this is fixed by changing the default behavior or returning the function "Addon domains".
Is the Cpanel team not aware of the many reports related to this, because the features are ambiguous and make many clients misunderstand?
Logically, why the addon domain menu but by default gives the default menu alias? It is something ambiguous.
This is not just a new feature but a serious problem due to the confusing addon domain feature. so that a client who wants to do an addon but wrongly does an alias and the client is confused why the appearance of the addon domain is the same as the main domain because the client realizes that if it is wrong, the client deletes the parking domain so that sometimes userdata errors occur.
Is the Cpanel team not aware of the many reports related to this, because the features are ambiguous and make many clients misunderstand?
Logically, why the addon domain menu but by default gives the default menu alias? It is something ambiguous.
This is not just a new feature but a serious problem due to the confusing addon domain feature. so that a client who wants to do an addon but wrongly does an alias and the client is confused why the appearance of the addon domain is the same as the main domain because the client realizes that if it is wrong, the client deletes the parking domain so that sometimes userdata errors occur.
Spoke with several people on this and we're going to make an iteration on this. First, the language. we're going to update it to be something more user friendly and less technical. Similar to this:
( ) This domain should serve the same content as main-domain.com. (?)
(x) This domain should serve its own content. (?)
And secondly we are going to switch the default "serve its own content" when the user has addons and subdomains available to them.
Dustin Scherer (he/him) | Product Owner | @dustinscherer
Spoke with several people on this and we're going to make an iteration on this. First, the language. we're going to update it to be something more user friendly and less technical. Similar to this:
( ) This domain should serve the same content as main-domain.com. (?)
(x) This domain should serve its own content. (?)
And secondly we are going to switch the default "serve its own content" when the user has addons and subdomains available to them.
Dustin Scherer (he/him) | Product Owner | @dustinscherer
Customers are breaking their websites and we're flooded with tickets.
only 1% of our customers use aliases and everybody uses addon domains.
This is a serious issue.
Customers are breaking their websites and we're flooded with tickets.
only 1% of our customers use aliases and everybody uses addon domains.
This is a serious issue.
Any update?
How is it possible that Cpanel does not have specific data on the use of this and also that it is thinking so much to fix it?
In the forums, blogs, comments, you can see that the vast majority use additional domains, not aliases.
This UI bug is causing us a lot of support issues. Is it so complicated to give us an option in configuration to choose whether or not to mark it as default?
More than 4 months to decide to give us a configurable option? We're not talking about something critical to the kernel. Only the choose default option or not.
For our part, I can confirm that out of 2400 customers, 0 customers use aliases. 0%. nobody.
Please, more empathy with cPanel customers.
Any update?
How is it possible that Cpanel does not have specific data on the use of this and also that it is thinking so much to fix it?
In the forums, blogs, comments, you can see that the vast majority use additional domains, not aliases.
This UI bug is causing us a lot of support issues. Is it so complicated to give us an option in configuration to choose whether or not to mark it as default?
More than 4 months to decide to give us a configurable option? We're not talking about something critical to the kernel. Only the choose default option or not.
For our part, I can confirm that out of 2400 customers, 0 customers use aliases. 0%. nobody.
Please, more empathy with cPanel customers.
Replies have been locked on this page!