Non-wordpress directory for Image files = security risk?

  • I’m developing my own WP site in a localhost Xampp environment. I dislike the way WP stores and implements image files – for website graphics and the images that appear in my posts.

    When complete, I intend to upload my WP site to a subdirectory in the server public_html.

    I’ve been uploading my website graphics and post images to a separate subdirectory in that same server public_html. It looks like this:

    mydomain/html_public/mysite <— install my wp site here

    mydomain/public_html/images
    mydomain/public_html/images/sitegraphics <— upload website graphics here
    mydomain/public_html/images/postimages <— upload image files for my posts here

    It works so far, but I’m concerned about how to SECURE these separate, non-wordpress subdirectories – mydomain/public_html/images and its subs.

    I’m using the free Wordfence plugin to protect the WP site.

    Q1. Will Wordfence secure the non-wordpress directories? Probably not, right?

    Q2. Can I use .htaccess files to secure the non-wordpress directories?

Viewing 1 replies (of 1 total)
Viewing 1 replies (of 1 total)
  • The topic ‘Non-wordpress directory for Image files = security risk?’ is closed to new replies.