htaccess coordination with WP Super Cache plugin

  • Resolved ericr23

    (@ericr23)


    1 year, 1 month ago

    I finally decided to set up a caching system, and WP Super Cache in “expert” mode uses Mod_Rewrite in the htaccess file. The plugin wrote its rewrite code before the WordPress code in htaccess, but it also moved the preexisting Wordfence “extended protection” rewrite code to the top, when it was at the end before. So the htaccess file is currently “Wordfence WAF”, “WPSuperCache”, “WordPress”. If I disable the extended protection and then reenable it, the code is back at the end: “WPSuperCache”, “WordPress”, “Wordfence WAF”. Does the order matter?

    • This topic was modified 1 year, 1 month ago by ericr23.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support wfpeter

    (@wfpeter)

    1 year, 1 month ago

    Hi @ericr23, thanks for messaging us about this.

    Other than Litespeed-specific changes that need to go above the # BEGIN WordPress line, we haven’t run into cases where a plugin caused a problem with our .htaccess lines inside that section. Some plugins add to the top of that section, and some add to the bottom, though the order of RewriteRule lines may matter if more than one rule would be triggered for the same file/path. The line further down the file would probably supercede any that came before it in that case.

    Thanks,
    Peter.

    Thread Starter ericr23

    (@ericr23)

    1 year, 1 month ago

    Thank you.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘htaccess coordination with WP Super Cache plugin’ is closed to new replies.