• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question Set WordPress plugin new file permissions

We use Autoptimize. The plugin creates .php-files without execute permissions, resulting in 403 errors and a semi-loaded page. What causes the files to be created without the required execute permissions and how can I configure the domain in such a way that PHP-files in the cache directory are created with execute permissions?

I'm assuming there's a umask being set somewhere and I don't know where.
 
Turns out the execution of the files generated by Autoptimize (causing the 403 errors) didn't have to do with file permissions but with Plesk's WordPress Plugin's security measures. The plugin recognises which directory is used by Autoptimize (so the measure works regardless of what you define the AUTOPTIMIZE_CACHE_CHILD_DIR to be).

WordPress → Domain → Security → Disable PHP Execution in cache directories → Revert

What I would like to know is if/how I can enable this setting but override it somehow, since I don't want all of my cache directories to allow execution.
 
Back
Top