Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cache wrapper not working properly #123

Closed
smant opened this issue Dec 23, 2015 · 3 comments
Closed

Cache wrapper not working properly #123

smant opened this issue Dec 23, 2015 · 3 comments
Labels

Comments

@smant
Copy link

smant commented Dec 23, 2015

  1. Since April 5 PAGE_CACHE_LOCATION setting not used anywere
  2. With Django 1.8.6 code on pages/cache.py always select 'default' cache

1 + 2 + locmem cache as default + several uwsgi workers = hard to resolve issues with editing

@remik
Copy link
Collaborator

remik commented Dec 28, 2015

This one looks bigger as CMS is invalidating cache but at that moment it has access to only 1 cache location.
It need to know when cache was create and update if outdated.

@remik remik added the Bug label Dec 28, 2015
@batiste
Copy link
Owner

batiste commented Dec 28, 2015

The cache has been designed with memcache in mind: a single point of truth for cache. If you are using memory cache in several processes it will not invalidate properly.

@batiste
Copy link
Owner

batiste commented Jan 19, 2016

I updated the documentation and fixed the bug with the cache:

http://django-page-cms.readthedocs.org/en/latest/installation.html#caching
e87b3d0

Thanks for the report. Could you check this is all working? I would like to unit test this but it looks like it might be an difficult task.

@batiste batiste closed this as completed Mar 23, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants