Plesk Tech Support
My feedback
-
4 votes
Thank you for your input. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
—
IGPlesk Tech Support
shared this idea
·
-
4 votes
Thank you for your input. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
—
IGPlesk Tech Support
shared this idea
·
-
7 votes
Thank you for your input. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
—
IGPlesk Tech Support
shared this idea
·
-
1 voteopen discussion · 1 comment · Feature Suggestions » Extensions · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment Plesk Tech Support
shared this idea
·
-
4 votesopen discussion · 1 comment · Feature Suggestions » Plesk (general) · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment Plesk Tech Support
commented
Hello,
Let me clarify the request in more details:
The Plesk is running on CloudLinux OS
For example, the customer account asks Plesk admin to change the PHP version for his domain example.com from PHP 5.3 to PHP 7.0
The Plesk admin goes to Domains > example.com > PHP Selector and made the changes and informs the customer that the PHP version was changed.
The customer logs into Plesk under his account to check the changes, goes to Domains > example.com and sees that the PHP version still shows as PHP 5.3.
In other words, when the Plesk admin performed the changes via Domains > example.com > PHP Selector the domain is starting use the newly set PHP version, but the customer still sees the old PHP in Domains > example.com and as a result, the incorrect information is shown for the customer.
This case was investigated by the Plesk development team and CloudLinux Support - in both cases was confirmed that the PHP version in Domains > example.com and Domains > example.com > PHP Selector should not be the same.
Plesk Tech Support
shared this idea
·
-
2 votes
Thank you for your input. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
—
IGPlesk Tech Support
shared this idea
·
-
4 votes
An error occurred while saving the comment Plesk Tech Support
commented
multiple instances on the same server are required
Plesk Tech Support
shared this idea
·
-
4 votes
Thank you for your input. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
—
IGAn error occurred while saving the comment Plesk Tech Support
commented
Plesk Tech Support
shared this idea
·
-
45 votesPlesk Tech Support
supported this idea
·
-
2 votes
Thank you for your input. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
—
IGAn error occurred while saving the comment Plesk Tech Support
commented
Plesk also has a button to reboot the server, so theoretically kernel updates installation can be completed without having to use CLI at all.
Plesk Tech Support
shared this idea
·
-
23 votes
It’s pretty clear what scenarios are expected to be covered by custom labels. We’ll look into extending the labels functionality in the next WPT releases.
—AK
An error occurred while saving the comment Plesk Tech Support
commented
At the moment in WordPress Toolkit, it is possible only to select the already exited "Production, Demo, Testing, Staging, Development"
Please add the possibility to create custom Labels for example "Reseller" to determine that the WordPress instance belongs to the Reseller account.
-
3 votes
Thank you for your input. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
—
IGAn error occurred while saving the comment Plesk Tech Support
commented
Currently, Plesk implements SNI so that each mail server can be protected by an individual SSL certificate. However, this only works if the domain has hosting. Mail-only domains cannot be secured with individual SSL certificates and need to rely on the server-wide certificate instead.
There should be an option to issue and assign individual SSL certificates to protect mail-only domains.
-
8 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 Plesk Tech Support
commented
It will be helpful to have a possibility to send email notifications to multiple custom addresses (instead of just one) configured in Plesk > Tools & Settings > Notifications.
Currently, it is needed to use workaround like mailing lists or forwarding. -
2 votes
Thank you for your input. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
—
IGPlesk Tech Support
shared this idea
·
-
2 votes
Thank you for your input. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
—
IGPlesk Tech Support
shared this idea
·
-
3 votes
Could you clarify that we correctly got the case:
Plesk Admin wants to prohibit an ability for their customers to set up an email forwarding to external emails.
If yes, would it work if the related subscription will have additional permission, which will allow/disallow to manage mail forwarding at all for a particular subscription?SE
Plesk Tech Support
shared this idea
·
-
6 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.
—
IGPlesk Tech Support
supported this idea
·
-
19 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.
— ES
Plesk Tech Support
supported this idea
·
-
5 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.
—
IGPlesk Tech Support
supported this idea
·
-
4 votes
Thank you for your input! We will consider this functionality in upcoming releases if this requests becomes popular enough.
We invite everyone who considers this request important to please continue voting for it.
—AS
Plesk Tech Support
supported this idea
·
SmartUpdate upon detection of JavaScript errors to not proceed with an update of WordPress and reports an error to a client.
Business case of your feature request?
A client's website that involves JavaScript will remain intact in case a WordPress update has the potential of breaking a website.
What happened: WP update to 5.6 caused JavaScript error and the page was blank. Despite this, the WP instance was updated.
What are the expected benefits of this feature?
Avoiding websites downtime.