I'm under a really tight deadline on this pro-bono project, so I may just create a duplicate class and work around it at this point. It's not that much extra code, and the end-users will never know the difference. I'll see what I can do about figuring out why it's not behaving and contribute back if I can.
Thanks again for the help! Kind regards, Brandon On May 30, 3:47 pm, Rajesh Dhawan <[EMAIL PROTECTED]> wrote: > On May 30, 4:28 pm, Brandon Taylor <[EMAIL PROTECTED]> wrote: > > > Ok, sorry, I'm a dork, I forgot how to run patches. I successfully > > merged the first patch into my newforms-admin install, but it still > > doesn't work. > > Option 1: Try to fix the patch yourself and contribute it back to the > ticket :) > > Option 2: Switch to trunk. That would depend on how much time and > effort you've already invested in newforms-admin. > > Option 3: Create a custom view of your own that does what you need and > url map it so it loads instead of the default admin view. > > I would personally go with option #3 and stick with newforms-admin > since it's much more extensible. > > Also, take a look at the newforms-admin FAQ in case there's something > there that could help: > > http://code.djangoproject.com/wiki/NewformsHOWTO --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
