Forgetting to uncheck "Share document root", one user erase his website
Hello,
Today I had the bad news to get a ticket from a user who erased his website by installing a new WordPress (through WP Toolkit), to an "addon" domain (or, now, I don't know how we are supposed to call that : "second domain added in an existing cPanel account!?").
Looking on that issue, we discovered that instinctively, he had "add another domain" under the unified "Domains" section > Submit that form and go straight to WP Toolkit to install WordPress.
I mean that he did not Unchecked the "Share document root" checkbox under the "Document Root (File System Location) " section.
[QUOTE]Document Root (File System Location)
If the document root is shared then the created domain will serve the same content as "example.com". This setting is permanent.
Share document root (/home/example/public_html) with "example.com".
the Default option offer the ability to ERASE the files through WP Toolkit (specially dangerous for (not so) beginner users) See screenshot below. It seems obvious to me that this checkbox should be Unchecked by default, to avoid the risk that users erase their WordPress websites with Toolkit, right after adding a new domain to the cPanel account (sure, Toolkit shows a warning, but my user was sure that he had selected the right "addon domain"). My users even don't know in which case they should point several domains to the same index.php file. The most part of the addon domains are not kind of "alias", but real websites hosted at the cPanel account root level (/home/user/example.com/). Do you agree that "most of the time, addon domains are used to host addon websites" ? If yes, you should agree that this checkbox should be Unchecked, because 1. it is the most common usage 2. the actual behaviour is "destructive" in case users do not read well the "disclaimer" each time they add an addon domain (and most of the users don't read all the disclaimers" and I confess I could make the mistake too by adding domains quick, the unified "domains" section was confusing in some way => specially this "inheritDocumentRoot" checkbox :-( Or at least, give us the possibility to uncheck the box from WHM tweak settings... Hopefully, I am doing daily backups. So I was able to restore the files from the night, but it seems he lost some data. Thanks A Lot in advance for the people from cPanel who are reading users complaining here :-D Tell me if I am wrong with this UX choice. !?
the Default option offer the ability to ERASE the files through WP Toolkit (specially dangerous for (not so) beginner users) See screenshot below. It seems obvious to me that this checkbox should be Unchecked by default, to avoid the risk that users erase their WordPress websites with Toolkit, right after adding a new domain to the cPanel account (sure, Toolkit shows a warning, but my user was sure that he had selected the right "addon domain"). My users even don't know in which case they should point several domains to the same index.php file. The most part of the addon domains are not kind of "alias", but real websites hosted at the cPanel account root level (/home/user/example.com/). Do you agree that "most of the time, addon domains are used to host addon websites" ? If yes, you should agree that this checkbox should be Unchecked, because 1. it is the most common usage 2. the actual behaviour is "destructive" in case users do not read well the "disclaimer" each time they add an addon domain (and most of the users don't read all the disclaimers" and I confess I could make the mistake too by adding domains quick, the unified "domains" section was confusing in some way => specially this "inheritDocumentRoot" checkbox :-( Or at least, give us the possibility to uncheck the box from WHM tweak settings... Hopefully, I am doing daily backups. So I was able to restore the files from the night, but it seems he lost some data. Thanks A Lot in advance for the people from cPanel who are reading users complaining here :-D Tell me if I am wrong with this UX choice. !?
-
Actually, yes! I do see there is already a backport request for 110, although I don't know exactly when or what version that will happen with. 0 -
Here's an update for everyone today :D 0 -
Here's an update for everyone today :D -10-25 at 11-38-02 WHM host - 116.0.1.png">84989
It is a very happy joy !! I think some dirt got in my eye :) Thank you so much! We will do the tests and will share results soon :)0
Please sign in to leave a comment.
Comments
63 comments