• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue Instance Broken

Hi, i've installed wp on my domain and everything worked fine. But i did some custom coding for security purposes and it broke the wp instance every time, I change the wp-content folder and uploads folder then used the following code in wp-config:

define ('WP_CONTENT_FOLDERNAME', 'content');
define ('WP_CONTENT_DIR', ABSPATH . WP_CONTENT_FOLDERNAME);
define ('WP_SITEURL', 'https://' . $_SERVER['HTTP_HOST'] . '/');
define ('WP_CONTENT_URL', WP_SITEURL . WP_CONTENT_FOLDERNAME);
define ('UPLOADS', 'content/images');

Maybe I shouldnt do this because it affects the core of Plesk? Is there anything else i can do?
 
Could you please clarify why do you not use Security feature of Plesk WordPress Toolkit and prefer to make security customizations manually?
 
We believe that all common security practices can be achieved using these Security options of Plesk WordPress Toolkit and there is no necessity to perform manual customizations in WP configs:

Screenshot at Jan 14 10-47-07.png
 
Back
Top