Let me reply to your question by first saying that it's not a good idea to put an
addon domain inside public_html. Here's why:
Let's say that you have domainONE.com created with the account. CWP forces
* it into public_html folder. Now, you create an addon domain domainTWO.com and you choose it to be inside public_html, meaning public_html/domainTWO.com
Now, we already have a problem.
If someone accesses
www.domainONE.com, it will work fine.
but if someone does
www.domainONE.com/domainTWO.com, it will show the addon domain within domainONE. Also explained here:
https://forum.centos-webpanel.com/index.php?topic=11600.msg39622#msg39622This is where CWP's design logic is flawed.
- The first flaw is that CWP forces the use of public_html for the main domain.
- The second flaw is that CWP allows you to put an addon domain inside public_html.
Mentioned here:
https://forum.centos-webpanel.com/index.php?topic=7189.msg39661#msg39661- The third flaw is that CWP devs have said on a thread to create a new user account for each new domain as "this is how it should be done". This is a very flawed logic for me, as I for example have 18 domains that all rewrite/redirect to the main domain. Why should I create 19 different accounts....
So, my suggestion is to accept CWP's logic and just go with it.
- Let the main domain be in /home/user/public_html, and all other addon domains be in /home/user/addonDomain.com
As for your problem with how the filesystemlock works, I did not notice it before. You are correct sir, it seems like this is a fifth design flaw.
File System Lock will lock all files and folders from any changes, this will also block all uploads, file modifications and even backup restore. This will secure your website almost 100%, and it's very useful if you are the only one who modifies website. If you need to modify your website or upload new files then you need to temporary unlock your files.
According to this, in my understanding and hopefully how it should be interpreted, the entire /home/user should be locked, or just at least all domain folders, including addon domains.
*You can change it by adding a custom vhost template for that domain, AFTER creating the account, but you will have a lot of issues because a lot of modules relies on the main domain existing in public_html