Documentation

Issues with ShopMagic and LiteSpeed Caching

Why does ShopMagic show outdated data when LiteSpeed Cache is enabled?#

ShopMagic's admin interface retrieves data through the WordPress REST API. If a caching layer returns an older response, recently saved settings or newly created automations may not appear.

LiteSpeed Cache includes a Cache REST API option. However, outdated data alone does not confirm that LiteSpeed is responsible; browser caching, object caching, or another server or CDN cache may also be involved.

How can I exclude ShopMagic REST API requests from LiteSpeed Cache?#

  1. Go to LiteSpeed Cache → Cache → Excludes.
  2. In Do Not Cache URIs, add the following entry on a separate line:
/wp-json/shopmagic/
  1. Click Save Changes.
  2. Use Purge All LSCache from the LiteSpeed Cache menu to clear previously cached responses.
  3. Reload ShopMagic and check whether the latest data appears.

LiteSpeed supports partial URI matching, so this entry covers paths containing /wp-json/shopmagic/, including ShopMagic's /wp-json/shopmagic/v1/ endpoints. Do not add the domain or the .* suffix.

If your site uses a custom REST API URL or requests containing ?rest_route=, the rule above may not match. Ask your hosting provider or LiteSpeed support to confirm the appropriate exclusion for the actual request URL.

What if the problem continues?#

As a diagnostic step, set Cache REST API to OFF under LiteSpeed Cache → Cache → Cache, save, purge the cache, and test again. This setting affects all WordPress REST API caching, rather than only ShopMagic.

If the issue persists, check other caching layers and browser request errors. When contacting support, provide the affected ShopMagic screen, steps to reproduce the issue, and the relevant request URL.

Will the exclusion affect site performance?#

The targeted exclusion leaves other eligible URLs available for caching. Its performance impact depends on your site's traffic and configuration.

For details about URI matching and REST API caching, see the LiteSpeed Cache documentation.

Not the solution you are looking for?

Please check other articles or open a support ticket.