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

Apphook cache invalidation problem #17

Closed
digi604 opened this issue Apr 22, 2009 · 6 comments
Closed

Apphook cache invalidation problem #17

digi604 opened this issue Apr 22, 2009 · 6 comments

Comments

@digi604
Copy link
Contributor

digi604 commented Apr 22, 2009

reverse is not working if a page is published after an apphook was installed.
A restart of the server is needed to make it work.

@pcicman
Copy link
Contributor

pcicman commented Apr 22, 2009

Right, will come soon...

@digi604
Copy link
Contributor Author

digi604 commented Apr 22, 2009

timed publishing pages have a problem too

@pcicman
Copy link
Contributor

pcicman commented Sep 24, 2009

comes in my trunk, timed published pages just not possible (expensive)

Proposal: we should avoid using apphooks with timed pages.

@digi604
Copy link
Contributor Author

digi604 commented Sep 24, 2009

i don't think that they are that expensive.
is there a possibility to switch off some apphooks based on the current language? So we don't have to write different urls.py for all the languages... maybe even with the namespace feature

@pcicman
Copy link
Contributor

pcicman commented Sep 24, 2009

have to check namespaces first...

i'm not willing to make the timed pages apphook integration, this will just lead to problems

possible scenario (!!on every request!!) will be:

1.) get all published (timed included) pages
2.) compare them with latest state
3.) if changed, clean urlresolvers._resolver_cache, this means all the urls must be recompiled. Currently there isn't any workaround for this, it is just the way how django resolvers works - patterns are cache globaly on module level.

@digi604
Copy link
Contributor Author

digi604 commented Sep 24, 2009

closed

christianbertschy pushed a commit to christianbertschy/django-cms-2.0 that referenced this issue Oct 1, 2012
czpython added a commit to czpython/django-cms that referenced this issue May 31, 2017
vxsx pushed a commit to czpython/django-cms that referenced this issue Jun 7, 2017
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants