Well, I found a simple solution to my own problem, so for the archives: If you place files form.html and freeform.html in a directory called comments/ within your templates/ directory, they will override the default templates!
Nice and simple, and obvious when I thought about it a little - this is what I'm finding great about Django: conventions allow you to make assumptions which just work! -Phil On 24/05/06, Phil Powell <[EMAIL PROTECTED]> wrote: > I just wanted to pose this question before raising a ticket, or > starting to work on a patch, just incase someone's got a workaround. > > I'm implementing contrib.comments, and everything works fine in a > basic dev setup. However, I'm running into a problem when trying to > deploy on a more complex setup running through Apache. > > Ive got an app running under a URL of the format: > http://www.somedomain.com/site/appname/. I want to run comments > through a URL like: http://www.somedomain.com/site/comments/, but it > appears to me that the "action" attribute in the comment forms is > hardcoded to /comments/ > > I could do some really hacky URL manipulation, but I'd rather not - > would seem to me that a more sensible solution would be to provide an > overide for the standard path to comments. > > Anyone else run into the same problem? Found a graceful fix? > > Thanks, > > -Phil > --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
