So we were trying to figure out why list_filter was not working in the
admin display for a couple of our models. It turns out that we have
another model which has a OneToOneField to the first model. This sets
the meta attr one_to_one_field on the first model to the field in the
second model.
Then
Well after finally getting some spare time I have created a patch
which validates all admin options. I have attached the patch to ticket
#3222. **NOTE** this is for the newforms-admin branch.
http://code.djangoproject.com/ticket/3222
I marked it as design decision needed as I changed a bit more
On 1/29/07, Andrew Durdin <[EMAIL PROTECTED]> wrote:
>
>
> On Jan 29, 4:50 pm, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
> > On 1/29/07 10:15 AM, Robert Myers wrote:
> >
> > > I'm seeing the same amount of errors on python 2.3.4, it appears th
On 1/28/07, Andrew Durdin <[EMAIL PROTECTED]> wrote:
>
>
> I'm trying to run all the django tests under Python 2.3.5 (on OS X
> 10.4.8), and there are lots of failures (see below).
> My settings file for the test is just:
>
> DEBUG = True
>
> DATABASE_ENGINE = 'mysql' # 'postgresql', 'mys
On 1/24/07, vfoley <[EMAIL PROTECTED]> wrote:
>
>
> Hello,
>
> one thing that bugs me about URL patterns is that you can specify a
> prefix only for the view functions to call, not for the URLs to match.
> A quick example
>
> web request:
> http://localhost/project/view/1/
>
> urls.py:
> urlpattern
> Excellent -- I'm excited that you're interested in helping out. The
> best bet would be to submit patches against the newforms-admin, but
> I'll give the caveat that I'm moving pretty quickly on this and may
> duplicate your work. The last thing I want is for you to spend time on
> a patch, only
>
>
> I'm -1 on adding it to URLconf and would rather see it in settings.py.
> Perhaps like:
>
> ADMIN_FIND_ADMIN_CLASSES = True
> ADMIN_MODELS = (
> 'myproj.myapp.admin.PollAdmin',
> 'someotherproj.someapp.admin.FooAdmin',
> )
>
> Where ADMIN_FIND_ADMIN_CLASSES (or whatever we want to call
I agree that moving this out of the model would be a great idea. I have been
thinking about this for a long time and not quite sure the best way to
handle it. However, my latest brainstorm idea is to place an
admin-urls.pyfile in each app which would work just like the generic
views and allow you
t
I love the new interface as well, congrats everyone!
Only one tiny remark, the closed tickets use to show up with a
strike-through, possibly a missing css param?
Robert
On 1/17/07, Deryck Hodge <[EMAIL PROTECTED]> wrote:
>
>
> On 1/17/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
> > I'd also
I would also like to help out. I wanted to fix a few issues with model
validation specifically for admin options. I'm not sure if you plan on
changing any of the existing options or how the options are called though.
If you are then I wont waste my time working on something that will change.
If no
On 1/2/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
Checked in as [4273].
Thanks!
Here is the roadmap I will follow unless anyone disagrees:
> 1. Submit tickets for the bugs uncovered by the test in 3217.
> 2. Submit enhancement ticket to include validation for all admin
> options.
>
line 2548, in regressiontests.forms.tests
Failed example:
print w.render('mydate', '2010-04-15')
Is expecting 2006 but it is now 2007. This test will continue to fail
each new year so it may be wise to rewrite this test, maybe with the
years list populated?
line 2485:
w =
SelectDateWidget(
Hello everyone!
Well my new years resolution was to be more active in the Django
community. We'll see how it goes. But, to start off the year I wanted
to extend the Admin application. In order to do that though there needs
to be a few more unit tests to verify I don't break anything. Of
course
13 matches
Mail list logo
