Apache mods enabled but W3TC can’t see it

  • Compatibility Check shows:

    mod_deflate: Not detected (required for disk enhanced Page Cache and Browser Cache)
    mod_env: Not detected (required for disk enhanced Page Cache and Browser Cache)
    mod_expires: Not detected (required for disk enhanced Page Cache and Browser Cache)
    mod_filter: Not detected (required for disk enhanced Page Cache and Browser Cache)
    mod_ext_filter: Not detected (required for disk enhanced Page Cache and Browser Cache)
    mod_headers: Not detected (required for disk enhanced Page Cache and Browser Cache)
    mod_mime: Not detected (required for disk enhanced Page Cache and Browser Cache)
    mod_rewrite: Not detected (required for disk enhanced Page Cache and Browser Cache)
    mod_setenvif: Not detected (required for disk enhanced Page Cache and Browser Cache)

    but mods are enabled. How can I fix this?

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • bgdstr

    (@bogdanstratulat)

    W3 Total Cache cannot read the state of an apache module if the website
    is not run with mod_php on a apache server. mod_php is disabled in
    some environments by default because it is not secure (mod_php is
    outdated).

    Warning can be ignored: modules are enabled on a server in fact,
    but plugin cannot detect them correctly and most of the functions o
    f the plugin will be functional.

    If it is still required to make plugin detect all apache modules
    correctly, enable mod_php on the server.

    Thank you for using W3 Total Cache!
    Kind regards!
    Bogdan S.

    I just want to add a question concerning the last part of the reply, if I may…

    “If it is still required to make plugin detect all apache modules
    correctly, enable mod_php on the server”

    same situation here, two major german hoster (strato, hostingeurope, ..) have their apache modules activated – but the plug-in can not detect due to the php mode..
    Due to the obvious security reasons, mod-php will not be used…

    so my question – are the apache modules, since they’re active, used by the plug-in or, since undetected from the plug-in, cant be put in action?
    I also would understad (in case the modules cant be used by the plug-in) what the loss in speed/caching might be compared to same system but with working modules…

    thanks in advance
    aovivo.

    bgdstr

    (@bogdanstratulat)

    Below you can find a method of testing that does not have this dependency.
    Place the following, in the main .htaccess file:

    <IfModule mod_deflate.c>
    SetENV HTTP_MYMODS_deflate 1
    </IfModule>
    <IfModule mod_env.c>
    SetENV HTTP_MYMODS_env 1
    </IfModule>
    <IfModule mod_expires.c>
    SetENV HTTP_MYMODS_expires 1
    </IfModule>
    <IfModule mod_filter.c>
    SetENV HTTP_MYMODS_filter 1
    </IfModule>
    <IfModule mod_ext_filter.c>
    SetENV HTTP_MYMODS_ext_filter 1
    </IfModule>
    <IfModule mod_headers.c>
    SetENV HTTP_MYMODS_headers 1
    </IfModule>
    <IfModule mod_mime.c>
    SetENV HTTP_MYMODS_mime 1
    </IfModule>
    <IfModule mod_rewrite.c>
    SetENV HTTP_MYMODS_rewrite 1
    </IfModule>
    <IfModule mod_setenvif.c>
    SetENV HTTP_MYMODS_setenvif 1
    </IfModule>

    Once this has been done, feel free to check for the corresponding environment variables within the compatibility to check PHP code.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Apache mods enabled but W3TC can’t see it’ is closed to new replies.