cache not working

Hi,

Does enabling the “Delete Old CSS And JS Files?” option in the Enfold theme options > Performance make any difference?

Please see my message in the private content field.

Regards,
Yigit

Hi,

Thanks for the update. What happens if you turn file compression off under Enfold->Performance? There’s really no point in having it active anyway, since your plugin should do that for you.

Best regards,
Rikard

Hi,

Sorry for the late reply. We are not sure what is causing your problems unfortunately, but maybe it’s the same problem as in this thread? https://kriesi.at/support/topic/no-caching-option-due-to-no-cache-issue/

Best regards,
Rikard

Hi,
Reading what you wrote in private, I don’t think that you can completely remove the WordPress session PHPSESSID, which is what you webhost seems to be asking.
I see that you are using the cookie bar on the site, try disabling this and see if you have the same issue.

Best regards,
Mike

Hi,
Thanks for the feedback, since you have disabled the Enfold cookie bar the only PHP Session cookie that is now applied is the WordPress PHPSESSID, I don’t believe there is anyway to completely remove this. This is beyond what we can help you with since it is a basic WordPress function, and I’m not sure that WordPress will work correctly if you were able to remove this.

Best regards,
Mike

Hi,
Well from what they are writing they want the standard WordPress PHPSESSID to be removed, perhaps they are giving you bad information because I can’t see that any other theme would do this.

Best regards,
Mike

Hi,
The function that they posted:

function varnish_safe_http_headers() {
    header( 'X-UA-Compatible: IE=edge,chrome=1' );
    session_cache_limiter('');
    header("Cache-Control: public, s-maxage=120");
  if( !session_id() )
  {
    session_start();
  }
}
add_action( 'send_headers', 'varnish_safe_http_headers' );

is the function that you added from this post above.
Which is from this Stack Exchange solution to override the WordPress default PHPSESSID to solve issues with a Varnish server.

Best regards,
Mike

Hi,
No, you should not add any code to the functions-enfold.php
Any customizations that you wish to add should be in your child theme functions.php
The way that I read the message from SG, there are no session cookies being assigned with this code in place, this seems to support the Stack Exchange solution replies for Varnish servers.
But when they checked again after about 30 minutes there was a session cookie, this seems to be due to the time limit in the code: s-maxage=120
So since this seems to show that the issue is between the SG cache and the WordPress PHPSESSID, I would recommend asking SG what they recommend the time limit in the code should be to work with their server cache.

Best regards,
Mike

Hi,
As I read their report he PHPSESSID cookie is defined by the wp-content/plugins/sitepress-multilingual-cms/
So I guess your SG cache is not campatable with the WPML plugin and you should disable it.
They say that they found a no-cache in the /wordpress-importer/avia-export-class.php but this is only used when you export the theme settings, these files are only loaded on the backend when you perform an export of the theme files. If you want to manually remove this from the theme you can by editing the files below, but the theme export feature may not work correctly and you will need to edit these files after each update. As it stands now SG says you won’t be able to use a cookie notification, or the WPML plugin and you will need to modify the export feature, in order to use their cache. Perhaps you should look into a cache plugin like WPRocket or WP Fastest Cache, neither of these have this issue with WPML or Enfold.

If you want to manually modify your files look for header(‘Pragma: no-cache’); in:
\enfold\config-layerslider\LayerSlider\assets\classes\class.ls.exportutil.php ▸ line 178
\enfold\framework\php\wordpress-importer\avia-export-class.php ▸ line 215

Best regards,
Mike

Hi,
Thank you for the update about the SG cache system, I don’t know why this was an issue, but I’m glad that you have it sorted out now, and now your site is working well with no issues.
Thanks for sharing your experience, perhaps this will help future users that are using the SG cache system.
If you have any further questions please create a new thread and we will gladly try to help you. Thank you for using Enfold.

Best regards,
Mike