Hello @futureyoon,
Thanks for your message.
It’s hard for me to say. It’s best to just check it out.
Best,
Mateusz
Hi @mateuszgbiorczyk
Thx for the input.
Given that you are aware of the current setup, which method would you recommend for this situation between
via .htaccess (recommended)
or
Pass Thru (without rewrites in .htaccess files or Nginx configuration)
Thank you
Hello @futureyoon,
via .htaccess – is a method that guarantees the highest performance.
OK.
Just for my understadning for this update,
“Support for environments where DOCUMENT_ROOT is different from WordPress installation directory”
Any partcular scenarios that you were aware of and tried to fix with this release?
It’s because as we have done a couple of test together earlier, it requires a brand new env setup. so if this update is not meant for AWS cloudfront or CDN related, it wouldnt be so worth to go thru the test again..
Do you mind sharing some cases that you were targeting to resolve. Thx
-
This reply was modified 4 years, 2 months ago by
futureyoon.
@futureyoon All the images must be on the same server as the plugin. It has not changed.
This change fixed the problem with paths on selected server configurations. Normally on the server the $_SERVER['DOCUMENT_ROOT'] variable should point to the root directory of your WordPress installation. Sometimes it is not and this change takes account of this type of configuration.
Did I explain it exactly?