Using Falcon Engine with WordPress in subdirectory

  • Resolved Michael Fraase

    (@mfraase)


    10 years, 8 months ago

    I’ll start by confessing to using WP Rocket for caching/minification. Since the WordPress 4.3 upgrade, I’ve had serious conflict problems with both WP Rocket 2.6.6 and 2.6.7:

    1. Using the DocumentCloud plugin, DocumentCloud embeds fail to render
    2. Using the Jetpack plugin, Related Posts fail to render

    Interestingly, these conflicts disappear if I deactivate WP Rocket.

    Even more interesting, neither of these conflicts appear if I activate the Falcon Engine caching module in Wordfence.

    But, I have a problem with Falcon Engine that I hope can be addressed (it’s what caused me to license WP Rocket).

    Activating the Falcon Engine caching understandably causes the .htaccess file to be rewritten. Totally to be expected (WP Rocket does this as well). Unfortunately, if you run WordPress in a subdirectory of Apache’s document root, Falcon Engine rewrites (or writes, actually) the wrong .htaccess file.

    Instead of rewriting /.htaccess, Falcon Engine creates /[wordpress]/.htaccess (where [wordpress] is the WordPress subdirectory. Falcon Engine is smart enough to download /.htaccess but not to rewrite /.htaccess. And /[wordpress]/.htaccess is apparently totally ignored in my installation:

    WordPress 4.3
    Wordfence 6.0.15
    OS X 10.10.5/Server 4.1.5 (with OS X native Apache; Homebrew PHP 5.6.12 and Homebrew MySQL 5.6.26

    When I copy the contents of /[wordpress]/.htaccess to /.htaccess everything works just fine, but I’d have to manually do that every time Wordfence blocked something. And it blocks plenty, let me tell you (that’s a compliment).

    Is there a way to resolve this? I’m going to show that I know just enough to be dangerous and go ahead and ask: Can I create a symbolic link to one of the .htaccess files or something?

    https://wordpress.org/plugins/wordfence/

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

    (@mmaunder)

    10 years, 8 months ago

    Hi Michael,

    Thanks for the detailed report. We are aware of this issue. Falcon used to work with subdirectory installations but recently stopped working and we’ve had other reports to confirm this. We have a bug outstanding for this issue and a fix will be in the next maintenance release.

    I’m the guy that reproduced the bug on our end and I think it may be a change in Apache 2.4 which triggered this – something to do with the order in which Apache now processes .htaccess files in subdirectories. However I haven’t confirmed that – only that fact that this issue exists.

    We’ll have a fix out in the next week or two.

    Regards,

    Mark.

    Thread Starter Michael Fraase

    (@mfraase)

    10 years, 8 months ago

    Well alrighty then, Mark. Thanks so much for the quick response; it’s much appreciated.

    Now if you can just fix the wp_wfHoover table bloat problem in the database… (grin).

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

The topic ‘Using Falcon Engine with WordPress in subdirectory’ is closed to new replies.