• Resolved Destillator

    (@destillator)


    Hi,

    I saw that the code refers to the wp-content directory in multiple places. Plugins like Better WP Security advise to rename wp-content into something else, but this breaks the plugin, obviously. Can this be fixed in a future release? That would be great.

    Thanks in advance!

    http://wordpress.org/extend/plugins/cleanerpress/

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Arevico

    (@arevico)

    Hi,

    We do not think that renaming ‘wp-content’ is a good idea. The renamed path will get presented to a potential adversary anyways (even if renamed). Uploads, plugin css and javascript files are loaded from it.

    Renaming the ‘wp-admin’-folder is recommended (if there if no publicly facing link to that folder on your website. The pugin does not contain hardcoded wp-admin references, only wp-content references.

    hifistyle

    (@hifistyle)

    Yup,
    I’ve renamed my wp_content and now have caused problems. Luckily I did backup. Anyone know if you just run the backup to fix?

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘wp-content hardcoded’ is closed to new replies.