Allow Wordpress Scan to search for a custom directory name instead of wp-content
I habitually rename my wp-contents directory for security reasons (as part of iThemes Security). As a result Plesk no longer recognises the Wordpress installations on the server, when scanning so I'm unable to take advantage of Plesk's Wordpress features.
Please could this be modified to allow me to specify a custom name for my wp-contents directory?
Ben Neale
shared this idea
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
-
Aurélien
commented
I agree with this request, to match better security standards
-
R W commented
Dear team, it would be important if I have 30 websites that have this problem. Maybe they can do the update. Thanks for the support
-
Kurt
commented
This is an important feature for those of us who have these unique website setups.
-
Henning
commented
Very important feature that would address multiple shortcomings of the WP Toolkit und would enable custom WordPress environments (e.g. roots/bedrock), as well as popular security / obfuscation techniques. Thanks!
-
Peter Hase
commented
Liebes Support Team, habt ihr schon eine Information, wann ihr diese Funktion in Plesk einbindet?
Wir nutzen 35 Webseiten mit geänderten wp-content Verzeichnis und wären dankbar, wenn ihr dies endlich umsetzten könnt.
Besten Dank
-
Aleksandar Perisic
commented
WP Toolkit is useless without this, custom themes that have changed /wp-content/ to something else cant use Back Up / Restore - as custom folders are not backed up.
-
Fred
commented
Hello, I have the same problem with Ithemes Security.
How do I make WordPress Toolkit take into account the name change of the wp-content folder?
Thank you -
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.