Re: NoReverseMatch at /polls/1/results/

I agree that the typo is also an issue and should be fixed, but that wouldn't result in the OP's error, since reverse() is complaining about a 'detail' URL specifically. The typo would result in a similar error when the result page is displayed, and would show 'guestion' as one of the kwargs.

Re: NoReverseMatch at /polls/1/results/

HM, Upon a closer look at your code (views.results), you have this: return render(request, 'polls/results.html', {'guestion': question}) You are passing "guestion" (with a G) to the template instead of "question" (with a Q). As such, your template complains when you try to use "question.id"

Re: NoReverseMatch at /polls/1/results/

Sorry, James is right, your problem is like James described. Sorry for the noise I read again and see that I understood bad your problem. Sorry El viernes, 8 de mayo de 2015, Luis Zárate escribió: > Which urls.py you paste here? The project URLs or the app urls .? > > It is

Re: NoReverseMatch at /polls/1/results/

Which urls.py you paste here? The project URLs or the app urls .? It is because you are using namespace in the url reverse so you need to named in your project's URLs and put the code paste here in your app urls. El jueves, 7 de mayo de 2015, James Schneider escribió: >

Re: Django code of conduct - last line

ok I have done that Carl I'm new to using GitHub to collaborate so let me know if there is anything out of place https://github.com/django/djangoproject.com/pull/468 Thanks for your feedback g On Saturday, 9 May 2015 08:34:16 UTC+12, Carl Meyer wrote: > > Hi Graham, > > On 05/08/2015 01:43 PM,

Defining base templates for reusable apps

I'm looking into building a set of open source reusable apps for Django and was wondering what the currently accepted best practice was for defining base templates for reusable apps was? I want my reusable apps templates to be easy to slot into an already existing site design but I'm unsure

Re: Django code of conduct - last line

Hi Graham, On 05/08/2015 01:43 PM, Graham Oliver wrote: > Thank you, so how about > > 'Don’t forget that it is human to err and blaming each other doesn’t get > us anywhere. > Instead, focus on helping to resolve issues and learning from mistakes' I think this is an improvement in clarity and

Re: Django code of conduct - last line

Thank you, so how about 'Don’t forget that it is human to err and blaming each other doesn’t get us anywhere. Instead, focus on helping to resolve issues and learning from mistakes' ? g On Friday, 8 May 2015 15:01:23 UTC+12, Lachlan Musicman wrote: > > To my mind it means something along the

Re: Ensure an object is saved even when the atomic bock rollsback

> Den 08/05/2015 kl. 15.15 skrev Marc Aymerich : > > HI, > > I'm using atomic requests, but one of my views needs to save a model > regardless of wheter the current transaction rolls back or not. > > I'm confused about how to proceed with the current autocommit

Re: Ensure an object is saved even when the atomic bock rollsback

On Fri, May 8, 2015 at 6:43 PM, Marc Aymerich wrote: > > > On Fri, May 8, 2015 at 5:50 PM, Carl Meyer wrote: > >> Hi Marc, >> >> On 05/08/2015 07:15 AM, Marc Aymerich wrote: >> > I'm using atomic requests, but one of my views needs to save a model >> >

Re: Ensure an object is saved even when the atomic bock rollsback

On Fri, May 8, 2015 at 5:50 PM, Carl Meyer wrote: > Hi Marc, > > On 05/08/2015 07:15 AM, Marc Aymerich wrote: > > I'm using atomic requests, but one of my views needs to save a model > > regardless of wheter the current transaction rolls back or not. > > > > I'm confused about

Generic template; determining information about calling view/app

Hi Sorry if this is confusing, it's the best I can describe. I have been separating my templates for inheritance clarity. I have a generic template 'category_list.html'. This can be used by different apps because the layout is the same. What I need to do in order to use appropriate links in

Re: Ensure an object is saved even when the atomic bock rollsback

Hi Marc, On 05/08/2015 07:15 AM, Marc Aymerich wrote: > I'm using atomic requests, but one of my views needs to save a model > regardless of wheter the current transaction rolls back or not. > > I'm confused about how to proceed with the current autocommit behaviour. > Do I need to use a

Ensure an object is saved even when the atomic bock rollsback

HI, I'm using atomic requests, but one of my views needs to save a model regardless of wheter the current transaction rolls back or not. I'm confused about how to proceed with the current autocommit behaviour. Do I need to use a different db connection? or perhaps there is some way of telling