• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Wordpress Scan when wp-contents has been renamed

Ben

New Pleskian
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?

Thanks

Ben
 
Thanks - I've done that. If anyone else likes this idea, please vote: https://plesk.uservoice.com/forums/...-wordpress-scan-to-search-for-a-custom-direct
I'd vote for it but it's unlikely to ever be a very popular request. I actually managed to get Plesk to sync with a custom location: :)

1. With `wp-config.php` in your web root (outside of your WordPress folder), the scan can detect and find your folder locations even if your WordPress folder is renamed other than 'wordpress'.

2. The tricky part is that Plesk uses php-cli to run the sync. So it requires a special config for the CLI to process and run your wordpress configuration without errors.

Here is the sample code I added at the top of my `wp-config.php` file:
Code:
if (php_sapi_name() === 'cli' && !defined('WP_USE_THEMES')) {
    $_SERVER['HTTP_HOST'] = $_SERVER['SERVER_NAME'] = 'www.domain.com';//defined for PHP cli via Plesk
    $_SERVER['SERVER_ADDR'] = gethostbyname(gethostname());
    $_SERVER['REQUEST_URI'] = '/';
    $_SERVER['DOCUMENT_ROOT'] = '/var/www/vhosts/domain.com/httpdocs/';
    define('WP_USE_THEMES', true);
}

It syncs properly after that, picking up my custom plugins path as well.
 
Last edited:
Back
Top