-
Notifications
You must be signed in to change notification settings - Fork 132
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
reload sitetree with sitetree_resync_apps #166
Comments
Thank you for the report. |
Here and in #135 is cache invalidation issue: SiteTree stores intermediate cache that needs to be invalidated from another process (manage). We'd probably end up with intermediate cache dropped. |
Thanks for your quick reply :) |
I've implemented an utility mehtod to reset cache, yet it requires cache to be set for something other than LocalMemory. You can verify the solution works in |
I will test it in a moment. Thanks for the quick response. |
I believe it works ok. (have to reload the dev webserver to see changes but that's ok) |
It shouldn't be necessary. What's your workflow? |
I change something in my file with urls (sitetrees.py); then I run python manage.py sitetree_resync_apps; I don't have Cache settings at all. (using default django cache settings) |
When I run python manage.py sitetree_resync_apps in my Django 1.7 or Django 1.8 stack; it seems like sitetree menu isn't correctly updated. I write "seems"; because I believe it's updated OK; but due to items still being in the cache you don't see it on the site or in the admin menu.
As I don't know in which cache it is; or how to delete it; my current workflow consist of: delete site tree items in admin menu manually, run python manage.py sitetree_resync_apps; this feel rather tedious when some URL's have to be added to the site tree; and you have to debug it a couple of times.
I even tried to clear the cache by writing an extra management command:
But this doesn't seem to work. Is there a way to force the cache to be flushed, or am I doing something wrong?
BTW: This issues could be related with #135
The text was updated successfully, but these errors were encountered: