Advanced configuration does not work

To confirm, did you uncomment out any necessary cache keys depending on your Cache Enabler settings? To troubleshoot this it would be helpful to receive a screenshot of your Cache Enabler settings and the exact snippet used in your .htaccess file.

Screen: https://monosnap.com/file/hpRqPkMzsVO0ODRzO4PNa27eQ73VgO

Code:

# BEGIN Cache Enabler

<IfModule mod_rewrite.c>
    <IfModule mod_setenvif.c>
        RewriteEngine On
        RewriteBase /

        # cache directory
        SetEnvIf Host ^ CE_CACHE_DIR=/wp-content/cache/cache-enabler

        # default cache keys
        SetEnvIf Host ^ CE_CACHE_KEY_SCHEME http-
        SetEnvIf Host ^ CE_CACHE_KEY_DEVICE
        SetEnvIf Host ^ CE_CACHE_KEY_WEBP
        SetEnvIf Host ^ CE_CACHE_KEY_COMPRESSION

        # scheme cache key
        RewriteCond %{HTTPS} ^(on|1)$ [OR]
        RewriteCond %{SERVER_PORT} =443 [OR]
        RewriteCond %{HTTP:X-Forwarded-Proto} =https [OR]
        RewriteCond %{HTTP:X-Forwarded-Scheme} =https
        RewriteRule ^ - [E=CE_CACHE_KEY_SCHEME:https-]

        # compression cache key
         <IfModule mod_mime.c>
             SetEnvIf Accept-Encoding gzip CE_CACHE_KEY_COMPRESSION=.gz
             AddType text/html .gz
             AddEncoding gzip .gz
         </IfModule>

        # get cache file
        SetEnvIf Host ^ CE_CACHE_FILE_DIR=%{ENV:CE_CACHE_DIR}/%{HTTP_HOST}%{REQUEST_URI}
        SetEnvIf Host ^ CE_CACHE_FILE_NAME=%{ENV:CE_CACHE_KEY_SCHEME}index%{ENV:CE_CACHE_KEY_DEVICE}%{ENV:CE_CACHE_KEY_WEBP}.html%{ENV:CE_CACHE_KEY_COMPRESSION}
        SetEnvIf Host ^ CE_CACHE_FILE=%{ENV:CE_CACHE_FILE_DIR}/%{ENV:CE_CACHE_FILE_NAME}

        # check if cache file exists
        RewriteCond %{DOCUMENT_ROOT}%{ENV:CE_CACHE_FILE} -f

        # check request method
        RewriteCond %{REQUEST_METHOD} =GET

        # check permalink structure has trailing slash
        RewriteCond %{REQUEST_URI} /[^\./\?]+(\?.*)?$

        # check excluded query strings
        RewriteCond %{QUERY_STRING} !^(?!(fbclid|ref|mc_(cid|eid)|utm_(source|medium|campaign|term|content|expid)|gclid|fb_(action_ids|action_types|source)|age-verified|usqp|cn-reloaded|_ga|_ke)).+$

        # check excluded cookies
        RewriteCond %{HTTP_COOKIE} !(wp-postpass|wordpress_logged_in|comment_author)_

        # deliver cache file
        RewriteRule ^ %{ENV:CE_CACHE_FILE} [L]
    </IfModule>
</IfModule>

# END Cache Enabler

The problem remains unchanged. Any ideas? I have to use an old plugin version on several installations now because of this limitation.

Unfortunately the support we are able to provide for the advanced configuration is limited due to how it currently implemented. To troubleshoot this further, does this still occur for you if the query string exclusion is commented out?

Yes, even then the behavior persists if the query string exclusion is commented out.

I understand the limited support, only it ran great across all versions and since 1.7.x it just doesn’t run at all, on all my installations. So something in the update must have been changed fundamentally.

As you know, all that’s occurring with the advanced configuration is the server is being told to deliver the cached page, completely bypassing PHP (e.g. WordPress). This configuration on the server isn’t directly related to Cache Enabler. There were changes in the update as to be expected, however, the old snippet would still work but it could have delivered a wrong cached file depending on what settings were configured and what type of request was first made when the cache was empty. (Like delivering an ungzipped page even though the client accepts Gzip because it exists and the gzipped version does not.)

With how it’s currently implemented we can only provide a starting point. I would love to have Cache Enabler automatically handle this to avoid all of this, but unfortunately that feature isn’t available yet. That is why we only recommend implementing this if the user has the prerequisite knowledge as each configuration may vary, which is why one snippet doesn’t fit all use cases.

I’m still happy to help wherever I’m able as I’d like the issue to be resolved for you. In this case are you able to troubleshoot this further on your end? For example, if you haven’t already you can try commenting out various exclusions to see what may be triggering this, or even print out ENV:CE_CACHE_FILE and other server environment variables to see what data your server is actually handling and what it’s trying to deliver.

I have already tried everything, nothing can be done. I have no more idea what else I could try. very sad, but thanks anyway.