Hello,
In the past I was able to specify the "cache" folder for FVM to use via the Admin backend interface as well as the FVM_DIR + FVM_URL constants.
Now neither is possible (since v3.3). The meaning for FVM_DIR has now changed into the location of the plugin itself - by which then the cache folder would be located inside the plugin folder - which is not good for our setup.
Since the constant WP_CONTENT_DIR is always created by WP itself, the ability to locate the cache folder inside the UPLOADS folder is now obsolete.
For now I reverted to v3.2.9 but it would be nice to be able to specify the cache folder location (and url), since wp-content/cache is neither a good location for us.
hi @peixotorms , would like to +1 this issue as this can also affect WP sites that uses version control if the cache folder cannot be specified anymore with the FVM_DIR + FVM_URL constants outside of a plugin directory
Hello, In the past I was able to specify the "cache" folder for FVM to use via the Admin backend interface as well as the FVM_DIR + FVM_URL constants. Now neither is possible (since v3.3). The meaning for FVM_DIR has now changed into the location of the plugin itself - by which then the cache folder would be located inside the plugin folder - which is not good for our setup. Since the constant WP_CONTENT_DIR is always created by WP itself, the ability to locate the cache folder inside the UPLOADS folder is now obsolete. For now I reverted to v3.2.9 but it would be nice to be able to specify the cache folder location (and url), since wp-content/cache is neither a good location for us.
Greets Michel