-
I ran into a problem today on one of my sites. We have several servers in read-only mode on the front-end and the only writable dir on front-end is /wp-content/uploads/ and this creates a problem with your plugin. 99% of most plugins use uploads dir for storing data on disk in order to be compatible with setups like this. It seems your plugin is creating a sitemap-cache dir inside the plugin dir to store sitemap xml files. Wost of all there was no plugin side checking to see if these files exist and no warning to the user. We didn’t notice the problem until we had 30% reduction in traffic. Is there any way you could use the /wp-content/uploads/ dir like every other plugin? I really don’t want to have to switch plugins. Please consider fixing this.
-
First I tried to disable sitemap caching using hook:
add_filter( ‘rank_math/sitemap/enable_caching’, function() {
return false;
});This didn’t solve my problem, because for some reason, your plugin still attempts to create empty directory with this feature turned off, and when you update the plugin the directory vanishes starting the process over again.
The only way to solve this problem was to relocate directory to uploads manualy using the rank_math/sitemap/cache_directory hook.
Although I do appreciate the convenience of providing us with these hooks, I still think the default should be uploads directory, and if you disable the sitemap cache via hook, it shouldn’t try and create that directory over and over again on a read-only file system.
The ticket ‘Sitemap Cache’ is closed to new replies.