Eric Neville
My feedback
4 results found
-
13 votes
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
—
IGAn error occurred while saving the comment Eric Neville
supported this idea
·
-
4 votes
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
—
IGEric Neville
supported this idea
·
-
11 votes
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
—
IGEric Neville
supported this idea
·
-
10 votes
Thank you for your input! We will consider this functionality in upcoming releases, if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
—
IGEric Neville
supported this idea
·
@Martin Dias: I stumbled across a way to do this while checking out Plesk's CLI docs (server_pref). You can forbid customers from changing their main domain name while still allowing them to set their webroot/docroot (and www/non-www) preferences with 2 steps:
1. Via root, run: `plesk bin server_pref --update -forbid-subscription-rename true`
Note: Applies to customers only. Admins can still rename domains.
2. Via Admin GUI: Go to Service Plan > Permissions, enable "Domains Management" option
It's not as nice a solution as a UI with more granular/intuitive permissions management would be, but it's a good workaround in the meantime. Hopefully this helps!