Path is outside resolved document root

Hello, first of all, thank you for a powerful plugin!

I’m using it on a setup kind of similar to what was mentioned here: https://wordpress.org/support/topic/sanity-check-failed-for-source-path-is-outside-allowed-path/page/3/#post-11925962, but deploying with Deployer instead of Capistrano. The thing is that I’m getting exactly the same error (Path is outside resolved document root).

Is there any parameter that I need to set in order to avoid/override this check? Do you consider this as an issue at all? Do I have any risk of misbehaviour if I patch this by myself to by-pass the check?

A little bit more information about my setup: the wp-content/uploads and wp-content/webp-express directories are created in [site_root]/shared, and the DocumentRoot of the site is located at [site_root]/current, so [site_root]/current/wp-content/uploads and [site_root]/current/wp-content/webp-express are set as symbolic links to the real directories, and the directory [site_root]/current itself is a symbolic link to [site_root]/releases/[timestamp].

So, this would be the structure managed by Deployer by default:

+ root
— – current (link to root/releases/20200513)
— + releases
—- + 20200513
—— + wp-content
——– – uploads (link to root/shared/wp-content/uploads)
——– – webp-express (link to root/shared/wp-content/webp-express)
— + shared
—- + wp-content
—— – uploads
—— – webp-express

Thank you in advance.

Cheers!

• This topic was modified 5 years, 10 months ago by mgarciaebo.
• This topic was modified 5 years, 10 months ago by mgarciaebo.
• This topic was modified 5 years, 10 months ago by mgarciaebo.