I did see you also posted this to the feature request as well. I've let the UI team know about the feedback.
Hello cPRex !
An apology if the message is somewhat aggressive. It's just that these kinds of changes are hurting us all. And you say that the normal use is aliases, but in any comment that cPanel clients can see we say that the normal use is Addon Domains.
Anyway an apology. I appreciate your management in the forums.
A doubt and that can serve as a partial and temporary solution for us:
How can we add a text block as an alert or warning on the cpanel Domains page?
I am attaching an image as an example (manipulated from the console's HTML).
Thank you.
Attachments
I completely understand the issues with the page, and the UI team is aware of the confusion this is causing for end users.
I don't have a good way to add something to the page like your example.
I don't have a good way to add something to the page like your example.
You can customize with content includes:
api.docs.cpanel.net
The file you want to work on is cpanel_jupiter_domains_header_after.html.tt
Guide to cPanel Interface Customization - Content Includes
With its world-class support and rich feature set, cPanel & WHM has been the industry-leading web hosting platform for over 20 years. Trusted worldwide by our technology partners WordPress, CloudLinux, LiteSpeed, and more.
api.docs.cpanel.net
The file you want to work on is cpanel_jupiter_domains_header_after.html.tt
@stormy, your input has been a great help. Thanks for the idea !! While this solution is temporary, it will help reduce customer tickets.You can customize with content includes:
Guide to cPanel Interface Customization - Content Includes
With its world-class support and rich feature set, cPanel & WHM has been the industry-leading web hosting platform for over 20 years. Trusted worldwide by our technology partners WordPress, CloudLinux, LiteSpeed, and more.
The file you want to work on is cpanel_jupiter_domains_header_after.html.tt
@cPRex, please, we will continue waiting for the definitive correction from cpanel about the default unchecking of Share Document Root. Thanks
P.S. Being able to add such messages on different cPanel pages from a graphical interface in WHM might be a good idea
Attachments
Even after modifying cPanel to alert users about this, we are running into this issue almost daily. Please, please, please UNCHECK the "share document root". It would still be bad even if cPanel was in the user's native language. Being in a foreign language, it's a recipe for disaster.
I've let the developers know the urgency on this issue.
That's true.
Posting the notice helps us because 95% of clients speak Spanish, but there is another problem. People don't read jejeje
While it has helped us, there are still some cases where they mistakenly do it as an alias, and what they want is an additional domain.
Hopefully that cPanel can correct that mistake very soon.
Posting the notice helps us because 95% of clients speak Spanish, but there is another problem. People don't read jejeje
While it has helped us, there are still some cases where they mistakenly do it as an alias, and what they want is an additional domain.
Hopefully that cPanel can correct that mistake very soon.
I just had another client erase his website. Of course they will not read any instructions.
Can we just have some sane defaults that actively prevent customers from doing stupid things like erasing the contents of public_html?
Can we just have some sane defaults that actively prevent customers from doing stupid things like erasing the contents of public_html?
Thank you.
If you wouldn't mind me asking, was any case number assigned to this issue?
It seems to me that you and we are fighting an uphill battle.
For whatever reason, someone at cPanel decided it is a bright idea to share the public root among multiple domains, while every norm in web hosting, web design, and web development strongly recommends the opposite.
This is so destructive for a web application, if a web developer at any web development firm does it, they would probably get fired. It breaks a magnitude of things. I cannot fathom how the experienced developers at cPanel came up with this idea.
And we are now stuck, with nobody making a simple change that has a destructive nature. It saddens me.
I did reach out to the UI team and confirmed it is on the agenda, but I don't have an ETA at this point.
It is sad that they didn't prioritize this. If they need time, why doesn't someone write a KB on how to modify the theme to uncheck the option?
There is an official theme modification guide, but it seems one had to dive deep to deselect the option as the official guides don't have any information on how to do that, which would be time-consuming and might break other things.
In any case, I am sorry for you CPRex, as you are the one who has to endure all the public banter.
It's all good - I just try and help the community, and relay stuff to the development team, whether that feedback is good or bad. Being stuck in the middle is *exactly* why I'm here.
Oh, it's a shame we don't even have an ETA for something so critical and easy to implement.
Was a case number generated?
This is something that has been requested since last year and continues to cause serious problems in the user experience.
Even with the notice, in 2 days we have had around 4 clients that delete the content of public_html to use other domains since it appears that they already have a wordpress installed, ignoring that they are sharing the same folder as another domain.
We need an immediate and effective solution. Just uncheck the default option.
Please cPRex, help us convey the urgency.
Was a case number generated?
This is something that has been requested since last year and continues to cause serious problems in the user experience.
Even with the notice, in 2 days we have had around 4 clients that delete the content of public_html to use other domains since it appears that they already have a wordpress installed, ignoring that they are sharing the same folder as another domain.
We need an immediate and effective solution. Just uncheck the default option.
Please cPRex, help us convey the urgency.
It seems to me there just wasn’t enough thought in the consequences of users deleting WordPress sites from WP Toolkit that reside in public_html when this was added to the UI.
I agree a resolution for this issue should be prioritized.
I agree a resolution for this issue should be prioritized.
do you know any eta for the second?
"change the default to create an addon domain if available".
this would for sure, reduce the amount of tickets we receive every month. clients wrongly add them as alias, since it's the default one right now.
@JoseDieguez - you've likely seen me say this before, but there is never an ETA. I have expressed how critical this is to the team as much as I possibly can, so they are well aware at this point.
sorry, i try to read as much as i can of every thread of my interested, may have missed the no eta yet.
I came here, again, because a client asked for 10 manual wordpress migrations, and all his domains were added as alias to the /public_html, so this gave us some extra steps, of removing and re-adding the domains, before we can actually work on his request.