3 ms·
Since at least Drupal 7, the core CMS has included the concept of “private files.” The files are stored in a directory that is not served publicly by the web se
by snowwrestler 11mo ago
Since at least Drupal 7, the core CMS has included the concept of “private files.” The files are stored in a directory that is not served publicly by the web server. Instead the CMS generates a proxy URL for each file, which is handled by the CMS like a page URL before serving the file by streaming it through PHP. So: it’s a heavier load on the server, but you get full permission management by the CMS.
Wordpress does not have this in core—no surprise. I was surprised to find that it’s not even available as a community plugin. I had to pay a developer to write a custom plugin when building a members-only website in Wordpress.
Some folks downplayed the risk of someone finding and directly accessing the file URL if it wasn’t referenced on a public page. It’s crazy to see it created a national government incident in the UK.
- Y-bar 11mo ago> I was surprised to find that it’s not even available as a community plugin. I found this one https://wordpress.org/plugins/prevent-direct-access/ https://wordpress.org/plugins/prevent-direct-access/
- fabian2k 11mo agoThat's even worse than I thought. I assumed it is a setting like in Drupal. To me it really doesn't make any sense to have that kind of giant hole in your permissions system from the start.