Re: Allow slug to be prepopulated on edit

2010-10-25 Thread rebus_
On 25 October 2010 14:04, Justin Lilly wrote: > I don't believe there is. > > Historically, this is there because slug fields usually make their way > to be used > for URLs. As such, changing the title of an object shouldn't adjust its URL as > that can be bad for SEO and folks who might have book

Re: Wherein Benjamin Franklin answers questions pertaining to the Django development process

2010-04-19 Thread rebus_
On 20 April 2010 01:23, Bitrot McGee wrote: > Q: When will Django finally have every feature I want? > A: "Ambition has its disappointments to sour us, but never the good > fortune to satisfy us." > > Q: What the fuck is taking so long? > A: "As we enjoy great advantages from the inventions of oth

Re: idea for using RequestContext by default

2010-01-05 Thread rebus_
Hi, This is the "natural" sequence of doing things anyway, i don't see why would you shuffle it around. 1. process stuff into variables 2. add said variables to a ContextRequest 3. send said ContextRequest to a template for rendering. In the example buttman gave in his link [1] you could say you

Re: Running unit tests when you can't create a new database

2009-12-08 Thread rebus_
2009/12/9 Martin Omander : > Hi all, > > How about letting Django users run unit tests without creating a new > test database? > > To use Django's built-in unit test harness, you have to have database > creation privileges. Not all web hosts give users those privileges. > For example, Webfaction, a

Re: validation.py backwards incompatibility for fieldsets

2009-11-19 Thread rebus_
2009/11/19 Russell Keith-Magee : > On Thu, Nov 19, 2009 at 10:35 PM, rebus_ wrote: > > Thanks for the report! You've definitely found a problem, and your > test case made it easy to narrow it down. Your patch wasn't quite > right - it resulted in an incorrect error mes

validation.py backwards incompatibility for fieldsets

2009-11-19 Thread rebus_
Hi, This is my first bug report so please don't shoot me right away. In revision 11744 [1] code was added in django/contrib/admin/validation.py which is supposed to improve the error message for M2M fields. It seems to me that this change has broken ability to display multiple fields on the same

Re: CSRF changes - backwards incompatible

2009-10-30 Thread rebus_
I would go with the idea that your settings are probably wrong. Just tried trunk and it seems to work fine. You should read: http://docs.djangoproject.com/en/dev/ref/contrib/csrf/#upgrading-notes Also, this is list is not for general Django troubleshooting but rather for Django development. Dav

Re: CSRF changes - backwards incompatible

2009-10-27 Thread rebus_
2009/10/27 Luke Plant : > If you have supplied custom templates to contrib views that accept > POST requests (e.g. auth login etc.), the template may need updating. > The steps needed are fully described in the docs, but in short: > >  Inside all elements, add {% csrf_token %} > > That's it. Apo