CMS Changes not reflected on site

Hiya Litium!
We got a customer running Litium 7.6.1 and because of known performance issues we implemented Redis for them a few months ago, even though it solved their performance issues we’re now running into other problems. Some of which we’ve been able to fix by writing our own extension method on the distributedMemoryCache which async updates the read value after returning it. (This is mainly values we choose to store in Redis and handle ourselves)

The CMS is however not one of them. If the customer are adding new subpages to a page these changes “disappear” until we up the Redis prefix, which is not a manageable solution. I’m a bit perplexed on how to move forward on this issue, since there’s no way for me to control the lifetime of the redis cache and the values doesn’t seem to be updated as they should using the backoffice.

Any help is appreciated. Thanks!

1 Like

Please open a support case about this.

Litium should send notification with Redis to each other so all servers in a multi-server environment should update their cache when entity is updated on one server.

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.