• Irene

    (@arlinaite)


    Hi,
    Are this, the rules that W3TC rewrite in htaccess file? Because I see they are written in htaccess file. What is this issue and how to fix? Is this a bug?
    Compatibility Test 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)

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

Viewing 12 replies - 1 through 12 (of 12 total)
  • Plugin Contributor gidomanders

    (@gidomanders)

    The reason they are not detected could be because the function apache_get_modules() doesn’t exist or the function doesn’t return anything. You could check that by adding var_dump(apache_get_modules()); to your wp-config.php or theme functions.php. If it doesn’t return an array including the above mentioned modules, you should contact your hosting partner to confirm. If they are installed and enabled, you can ignore the tests.

    Thread Starter Irene

    (@arlinaite)

    Hi gidomanders

    Thanks for your fast and accurate reply

    bgdstr

    (@bogdanstratulat)

    I am happy to hear that everything has been sorted out. Please feel
    free to close and mark this topic as resolved.

    If you have any other questions, please feel free to ask.

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

    Thread Starter Irene

    (@arlinaite)

    Hi,

    Now I have a new error message:

    The following memcached servers are not responding or not running:

    Database Cache: 127.0.0.1:11211.
    This message will automatically disappear once the issue is resolved.

    I ask to Cloudways support and they check that this modules are up and running.

    Thread Starter Irene

    (@arlinaite)

    This error message appears in plugin page.

    Plugin Contributor gidomanders

    (@gidomanders)

    Maybe mencache is running, but on a different IP address or it is not reachable by PHP. Did cloudways tell you what settings to use to be able to connect?

    Thread Starter Irene

    (@arlinaite)

    Hi @gidomanders,

    Thanks for your reply.

    I had setup W3TC following indication of Cloudways KB:

    https://support.cloudways.com/wordpress-w3-total-cache-configuration-for-optimal-performance/

    And also for themes related matters, I used the settings recommended by theme developer:

    https://docs.presscustomizr.com/article/243-speed-up-the-hueman-theme-how-to-setup-w3-total-cache-plugin

    Is there something else to setup? What could be wrong?

    Thanks for your time.

    Plugin Contributor gidomanders

    (@gidomanders)

    If you followed those guides, I think you should not have any conflicting settings. Maybe there is a more detailed error in your error logs. If you could check that, I could possibly help you further. Otherwise you have to go to Performance => Support and submit a support request so we can help you remotely by logging in to your system.

    Thread Starter Irene

    (@arlinaite)

    Hi @gidomanders,

    Thanks for your reply.
    Yesterday I upgrade to PHP 7.2. I looked in the error log file from today and yesterday. It does not seem to have anything to do with the W3TC error.

    I only find this error display indefinitely, where only changes the referrer:
    example:

    [Tue Jul 03 06:26:21.918613 2018] [proxy_fcgi:error] [pid 18714] [client 127.0.0.1:39565] AH01071: Got error 'PHP message: PHP Warning: Use of undefined constant TEMPLATEPATH - assumed 'TEMPLATEPATH' (this will throw an Error in a future version of PHP) in /home/144251.cloudwaysapps.com/mhydpxbvzu/public_html/wp-includes/theme.php on line 136\nPHP message: PHP Warning: Use of undefined constant STYLESHEETPATH - assumed 'STYLESHEETPATH' (this will throw an Error in a future version of PHP) in /home/144251.cloudwaysapps.com/mhydpxbvzu/public_html/wp-includes/theme.php on line 136\nPHP message: PHP Warning: Use of undefined constant TEMPLATEPATH - assumed 'TEMPLATEPATH' (this will throw an Error in a future version of PHP) in /home/144251.cloudwaysapps.com/mhydpxbvzu/public_html/wp-includes/theme.php on line 136\nPHP message: PHP Warning: Use of undefined constant STYLESHEETPATH - assumed 'STYLESHEETPATH' (this will throw an Error in a future version of PHP) in /home/144251.cloudwaysapps.com/mhydpxbvzu/public_html/wp-includes/theme.php on line 136\n'

    [Tue Jul 03 06:29:44.206202 2018] [proxy_fcgi:error] [pid 18802] [client 127.0.0.1:39600] AH01071: Got error 'PHP message: PHP Warning: Use of undefined constant TEMPLATEPATH - assumed 'TEMPLATEPATH' (this will throw an Error in a future version of PHP) in /home/144251.cloudwaysapps.com/mhydpxbvzu/public_html/wp-includes/theme.php on line 136\nPHP message: PHP Warning: Use of undefined constant STYLESHEETPATH - assumed 'STYLESHEETPATH' (this will throw an Error in a future version of PHP) in /home/144251.cloudwaysapps.com/mhydpxbvzu/public_html/wp-includes/theme.php on line 136\nPHP message: PHP Warning: Use of undefined constant TEMPLATEPATH - assumed 'TEMPLATEPATH' (this will throw an Error in a future version of PHP) in /home/144251.cloudwaysapps.com/mhydpxbvzu/public_html/wp-includes/theme.php on line 136\nPHP message: PHP Warning: Use of undefined constant STYLESHEETPATH - assumed 'STYLESHEETPATH' (this will throw an Error in a future version of PHP) in /home/144251.cloudwaysapps.com/mhydpxbvzu/public_html/wp-includes/theme.php on line 136\n', referer: http://www.google.com/

    I checked what theme.php in line 136

    /**
     * Whether a child theme is in use.
     *
     * @since 3.0.0
     *
     * @return bool true if a child theme is in use, false otherwise.
     **/
    function is_child_theme() {
    	return ( TEMPLATEPATH !== STYLESHEETPATH );
    }
    Thread Starter Irene

    (@arlinaite)

    Hi @gidomanders,

    I have the reply from Cloudways Support:

    “The issue you have been facing on compatibility check is due to that we are using php-fpm instead of mod_php. Secondly, Memcached is working fine on your server. Please let us know if we can do anything else for you.”

    I found in Cloudways kb:
    https://support.cloudways.com/how-to-change-php-fpm-settings/

    “The rewrite/redirect rules defined in a .htaccess file will be effective for both environments.
    For server-level PHP settings (e.g. execution limit, max input variables, max input time etc.), go to the Server Settings section in the Server Management area.”

    You think it’s safe to ignore incompatibilities?
    Any suggestions?

    • This reply was modified 7 years, 11 months ago by Irene.
    Plugin Contributor gidomanders

    (@gidomanders)

    The fact that they’re using php-fpm and not mod_php, is also the reason you see Not detected, because php-fpm does not support the apache_get_modules() function. That’s not a problem, the plugin still functions normally without it.

    You should submit a support request through Performance => Support so we can debug your system to find out why the plugin cannot connect to your memcached.

    Thread Starter Irene

    (@arlinaite)

    Hi @gidomanders,

    Ok, understand, thanks for all your help.

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

The topic ‘Compatibility Issue’ is closed to new replies.