This broke in django 1.4 since it fires based on the contents of an error message,
and the message changed. Most visible due to the fact that it completely broke
creation of new organsation objects.
Prevents changes from M2M updates from appearing after every single
save to a PgModel derived class. The unfortunate side effect is that
no M2M updates will appear, but this has to do with the context in how
the diff between two objects it taking place. An expanded note appears in
the explanation to #110Fixes#110
Creates prettier text for many-to-many fields for mail notifications by detecting if such a field is of a many-to-many type, and if so, joins the list together based on the related object's default unicode representation
Fixes#110
removed extra line of commented code
This allows all models inherited from PgModel to specify which
URLs to purge by either setting a field or defining a function
called purge_urls, at which point they will be purged whenever
the save signal is fired.
Also implements a form under /admin/purge/ that allows for manual
purging. This should probably be extended in the future to show
the status of the pgq slaves, but that will come later.
Includes a SQL function that posts the expires to a pgq queue. For
a local deployment, this can be replaced with a simple void function
to turn off varnish purging.
