Hardcoded paths in default wordfence-waf.php

  • Resolved Roy Orbitson

    (@lev0)


    6 years, 6 months ago

    When setting up Wordfence, I noticed that the generated wordfence-waf.php contains hard-coded absolute paths, which breaks the install when moving servers, hosting accounts, etc. Why not use __DIR__? And, whilst you’re there, lose the unnecessary ?>.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Fabian Deitelhoff

    (@fdeitelhoff)

    6 years, 6 months ago

    Hi there,

    I experience the same as a problem.

    I copied my hosted WordPress instance to a XAMPP installation to test something out. But I cannot manage to get it working due to many hard-coded paths.

    Is this intentional?

    Thanks

    wfalaa

    (@wfalaa)

    6 years, 6 months ago

    Hi Roy,
    Your suggestions have been logged to our dev team (internal reference number: FB6182), all suggestions are evaluated by our team and considered seriously. However, some might need further investigation and testing before implementing them in the plugin, so I’m not sure which one will make it to a new version or its ETA.

    For now, you can follow these instructions while migrating your sites, I’m sure this should prevent such an issue.

    Thanks.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Hardcoded paths in default wordfence-waf.php’ is closed to new replies.