Hi,
A hosted customer who was trying to establish an added FTP account removed the public_html from the Directory field and entered their target directory name "store" within that field. Of course their /store directory is within their public_html so it was a big mistake to replace public_html with the word "store" rather than to simply add "store" to the path like so:
/public_html/store
However, what should have been a minor mistake became a huge mess because when he clicked Create FTP Account. the cPanel system did three things:
1 -- Removed the entire root, public_html directory.
2 -- Removed the public_ftp directory.
3 -- Created a new directory in sub-web named "store".
Question - So that people don't end up flush months of work down the tubes with a single click upon making such a simple error, is there any way cPanel.net can lock in the public_html part of the path in the FTP Accounts utility? Or at least prevent the system from removing public_html when the Directory field is filled in this way?
A hosted customer who was trying to establish an added FTP account removed the public_html from the Directory field and entered their target directory name "store" within that field. Of course their /store directory is within their public_html so it was a big mistake to replace public_html with the word "store" rather than to simply add "store" to the path like so:
/public_html/store
However, what should have been a minor mistake became a huge mess because when he clicked Create FTP Account. the cPanel system did three things:
1 -- Removed the entire root, public_html directory.
2 -- Removed the public_ftp directory.
3 -- Created a new directory in sub-web named "store".
Question - So that people don't end up flush months of work down the tubes with a single click upon making such a simple error, is there any way cPanel.net can lock in the public_html part of the path in the FTP Accounts utility? Or at least prevent the system from removing public_html when the Directory field is filled in this way?