Why does adding a Password Protected Directory require that the CMD_SUBDOMAIN command be available? What specifically is the Password Protected Directory function doing that requires CMD_SUBDOMAIN?
I prefer to just not allow subdomains on our DirectAdmin servers. The function of subdomains can still be duplicated by creating an additional domain name and just specifying the full subdomain name. As such, we have CMD_SUBDOMAIN disabled on our servers. But users cannot password protect any directories due to this limitation.
Is this an oversight some where. I don't know why Password Protected Directory would need the CMD_SUBDOMAIN command, especially if the account has no subdomains.
I prefer to just not allow subdomains on our DirectAdmin servers. The function of subdomains can still be duplicated by creating an additional domain name and just specifying the full subdomain name. As such, we have CMD_SUBDOMAIN disabled on our servers. But users cannot password protect any directories due to this limitation.
Is this an oversight some where. I don't know why Password Protected Directory would need the CMD_SUBDOMAIN command, especially if the account has no subdomains.