Questioning Plugin’s Need to Store Data On Disk
-
Hi,
I tested your plugin today and I noticed that it’s writing several things to disk that don’t need to be stored in persistent storage in the file system. Moreover, the plugin creates multiple (nested) directories withinwp-content, yet it doesn’t necessarily have “write” permissions to it.
1. Why is there anginx.confwritten to disk?
2. Thepurge_cache_queuedirectory andcache_queue.jsonshould either be stored astransientdata or added as wp-cron tasks, IMO. When the plugin can’t write to this path, purging the cache fails silently after saving a post—it somewhat shows up in the logs, but it’s not verbose either.None of the created files are protected from being read from the outside—neither through obfuscation nor through access rules. The
debug.logat least is. While none of this necessarily reveals sensitive data, it’s data about the site that doesn’t need to be publicly available.I suggest either making all the paths filterable, so I can move them outside the web-root of the site or, better yet, save the data through the APIs provided by WordPress. None of this needs to live on the disk, as far as I’m aware.
If you accept OSS-contributions through GitHub for example, I’d be happy to further discuss this and provide a solution.
Thanks for the good work on the plugin.
🤘 Alex
The topic ‘Questioning Plugin’s Need to Store Data On Disk’ is closed to new replies.