Skip to main content

How to disable caching for the WooCommerce pages?

Comments

3 comments

  • cPRex Jurassic Moderator

    Hey there!  The only caching present would be tools you have configured, such as Nginx.  If you have Nginx installed on the machine we have an article here that explains how you can remove certain files from the caching tool:

    https://support.cpanel.net/hc/en-us/articles/7376659306263-How-to-exclude-files-from-Nginx-caching

    If there is other caching setup in WooCommerce itself, that isn't something cPanel would know about so I wouldn't be able to help with that side of things.

    0
  • Elizabeta

    Hello cPRex,

    Thank you very much for your answer. I think Nginx is not installed.
    When I run     cd /etc/nginx/conf.d/users/  there is some our users. But, probably I do not use Nginx.

    Also, there is no other caching like LiteSpeed Cache, W3 Total Cache, WP Super Cache, Redis Object Cache

    [root@cprodvm users]# ps aux | grep -E 'nginx|litespeed|memcached|redis'
    root     2891827  0.0  0.0  12224  1176 pts/0    S+   08:31   0:00 grep --color=auto -E nginx|litespeed|memcached|redis

    There are no active processes nginx, litespeed, memcached, redis.

    What is your recommendation to disable caching for a specific user? Should he himself install e.g. plugin LiteSpeed Cache  in Wordpress or disable caching via .htaccess file in Apache in its directory.
    Should something be done at the cPanel server level or can we leave it to the user to disable caching himself?

    Best regards,
    Elizabeta

     

    0
  • Elizabeta

    Hello,

    Just another info:

    Our user is having a big problem with the webshop at his web address. The webshop uses Wordpress and Woocommerce.
    On the WooCommerce webshop, the wrong product is displayed in the cart after being added.

    The user found information that caching should be disabled for the following WooCommerce pages:

    /cart/
    /checkout/
    /my-account/

    This problem did not exist before, maybe it appeared a month ago. 
    Could this problem be related to the new cPanel version 128.0.18?

    Best regards,
    Elizabeta

     

    0

Please sign in to leave a comment.