Comment #4 on issue 9 by n.leush: Save and remove signals doesn't take to account template sites http://code.google.com/p/django-dbtemplates/issues/detail?id=9
I see... But in this case altering settings is not a bug reason. I clearly can see add_template_to_cache and remove_cached_template works incorrect when saving template for some another "Site" which differs from current. Let's see an example - I have one db for two same sites which are different django instances. Is this normal? I can save template for "another" site while working with current. And I'll get cached template from another site for current site. If this is not a normal situation (when to sites are in one db) - then why to store "sites" field in db-template? This is just a bug after bug (http://code.google.com/p/django-dbtemplates/issues/detail?id=6). My solution of issue 6 was very easy but not correct generally considering model's signals cache access. Sorry for this miss take, I just wanted to correct it... -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pinax-updates" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pinax-updates?hl=en -~----------~----~----~----~------~----~------~--~---
