Hello Dominique, On Friday, May 13, 2011 10:09:19 AM UTC-7, Dominique Guardiola Falco wrote:
None of my business, but you could also look why your code is calling this > method when it shouldn't be called > Or add a blank get_absolute_url methods to the models which doesn't have > one > The code is there to be called for this one model. It works with 1.2.5 but breaks with 1.3. I had already considered improving my code to be more robust for use with 1.3. My main point here though is that something that worked under 1.2.5 is now broken in 1.3. A call to a method when rendering a template that previously failed silently, now fails noisily. I'm attempting to ascertain whether failing silently is the desired behavior but is now broken under 1.3. If this is the case then I'd want to report this as a bug. I'm totally able to accept that my coding is the problem and was able to do something in 1.2.5 and now 1.3 has improved error detection or some such. I also don't want to just change my code without investigation as to why things changed. My understanding is that in some circumstances failing silently when rending template stuff is the prefered behavior. Is this one of them? I don't know, hence my question to the community. Toodle-loooooooooooooo.......... creecode -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
