Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter rendal101

    (@rendal101)

    Same problems with the TwentySixteen Theme:
    Custom Permalinks don’t work, default (id-based) works.

    Deactivating all plugins doesn’t change anything.

    I’m having the same issue — both urls are lowercase.
    Issue remains 🙁

    Thread Starter rendal101

    (@rendal101)

    Interesting… so what does this line in ‘wordfence-waf.php’ actually mean:

    // Before removing this file, please verify the PHP ini settingauto_prepend_filedoes not point to this.

    ?

    However, you were right… it is something to do with the permalinks; setting it back to ‘plain’ (where it uses id’s) seems to be working. Unfortunately, switching back to a custom permalink structure renders the site inaccessible again.

    Any thoughts on that one? 🙂 😛

    Thread Starter rendal101

    (@rendal101)

    I was only prompted to download a copy of the .htaccess file.

    I’ve reinstated the original .htaccess (stripped out reference to wordfence stuff, now it only has the original wordpress code in there).

    I removed the .user.ini file, as well as the wordfence-waf.php file from that root directory. I have also disabled the wordfence plugin.

    The site was working perfectly after WordPress 4.5 update, prior to wordfence update. in fact, it was working after wordfence update too — it was only after attempting to setup the firewall that it stopped working…

    It still refuses to load.
    Adding /index.php to the end of the tld makes it load; other pages will load too (from navigation / direct url) however, images aren’t loading.

    Thoughts?
    Would WF have touched php.ini at all?

Viewing 4 replies - 1 through 4 (of 4 total)