• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Please beaware of a breaking change in the REST API on the next Plesk release (18.0.62).
    Starting from Plesk Obsidian 18.0.62, requests to REST API containing the Content-Type header with a media-type directive other than “application/json” will result in the HTTP “415 Unsupported Media Type” client error response code. Read more here

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