Fee
My feedback
9 results found
-
1,198 votes
An error occurred while saving the comment Fee
supported this idea
·
-
27 votes
This looks like a valid feature, so we’ll see when we can implement it. Please continue voting if this feature is important for you, so we can prioritize feature accordingly.
—AK
An error occurred while saving the comment Fee
commented
Currently I use a workaround in Plesk 12.5: First install the setup via WordPress Toolkit, then rename wp-content, add the definitions WP_CONTENT_DIR and WP_CONTENT_URL in wp-config.php and change the file urls in the database. Then I can use the WordPress Toolkit for updates.
Unfortunately this workaround seems not to work in Plesk Onyx.
Please implement this feature before end of 2019 (end of life of Plesk 12.5). I would be happy if at least the workaround works in Plesk Onyx, but it would be very handy if I didn't had to use a workaround at all.Fee
supported this idea
·
-
44 votes
These suggestions look quite reasonable. We encourage other WPT users to join and let us know what other security improvements you’d like us to implement in WPT.
—AK
An error occurred while saving the comment Fee
commented
@Olaf Kapinski: The WordPress Toolkit features only run if you set up the installation with WordPress toolkit. If you install it manually it doesn't do anything.
Fee
supported this idea
·
-
543 votes
We have serious doubts this function can really increase server security:
1) Plesk has built-in protection against brute-force on login – it will lock the login form. So no one can try multiple attempts
2) Arbitrary login name adds very little guess-complexity to a proper password. If you have concerns for your login brute-forced – add another 5-7 characters into your password and feel safe.As changed login name is still very likely to be some sort of vocabulary word or derived from your other account name – this function would only give a false sense of better security. Your security strength is in complex password, not in a complex login name. If you have one good password, you don’t need to treat login as your “second password” – one good password is enough.
As for concerns that default password requirement is set in “weak”, that fail2ban module is not…
Fee
supported this idea
·
-
140 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.
—
ETFee
supported this idea
·
-
17 votesFee
supported this idea
·
-
20 votes
Thanks for submitting this suggestion. It definitely looks useful, so we’ll consider adding it in upcoming Plesk / WPT updates.
Everyone, please continue to vote for this feature so we could evaluate its popularity.
—AK
Fee
shared this idea
·
-
26 votesFee
supported this idea
·
-
34 votesFee
supported this idea
·
This important feature request was posted in 2013, one admin asked for more input in 2016, now in 2019 there are 710 votes and a lot of comments gave enough input.
If you need even more input: We have a Nextcloud instance running with plesk and want to activate antivirus file scanning for uploaded files. The required app needs ClamAV installed.