Graham Ullrich

@zeeshanabid94 thanks for your desire to add tests for this issue. Regarding testing pinax-blog code, after adding appropriate tests to your local copy of the pinax-blog repo you then invoke...

`ACCOUNT_DELETION_MARK_CALLBACK` was removed from settings in this commit: https://github.com/pinax/django-user-accounts/commit/526bcda633448e6801a95bdd33d7e0d5eaad0406, but the latest models.py references `settings.ACCOUNT_DELETION_MARK_CALLBACK` https://github.com/pinax/django-user-accounts/blob/master/account/models.py#L389 Seems like a straightforward bug. A good PR for this requires: * change models.py...

Here is the initial WIP design: https://github.com/grahamu/pinax-starter-projects/tree/images.

On advice of counsel, I have moved this project to a standalone Pinax demo repository named [`cloudspotting`](https://github.com/grahamu/cloudspotting).

@paltman here's the simple setup.py if you decide we add that to starter projects.

@jtauber Looks like this branch has been created, perhaps this issue is complete?

@jtauber Looks like this branch (waiting-list) has been created, perhaps this issue is complete?

@jaydenwindle seems reasonable to create an `admin` dir under pinax in pinax-templates, and extend from there just like is seen in pinax-points.

@jaydenwindle Thanks for your template transfer PRs. At the moment our focus is on the Pinax 18.01 release, so `pinax-points` in on the back burner for a bit. Once 18.01...

@zmrenwu thanks for your analysis. Writing a test to demonstrate behavior is the best way to get something changed. You might write a simple test showing this issue and submit...