Wow, thanks for all the hard work to everyone involved! This is really
awesome!
I'll update the Dutch translations soon. And I'll have to start
preparing my company's 30+ Django projects for this change... ;)
Rudolph
--~--~-~--~~~---~--~~
You received this message
Giggidy giggidy.
On Fri, Jul 18, 2008 at 7:14 PM, Julien Phalip <[EMAIL PROTECTED]> wrote:
>
> Thanks Brian, Karen and all the NFA team for this massive
> contribution!!
>
> On Jul 19, 10:01 am, Brian Rosner <[EMAIL PROTECTED]> wrote:
> > I have just recently
Thanks Brian, Karen and all the NFA team for this massive
contribution!!
On Jul 19, 10:01 am, Brian Rosner <[EMAIL PROTECTED]> wrote:
> I have just recently merged the newforms-admin branch into trunk as of
> r7967 [1]. This is an extremely backward incompatible change. The
&g
I have just recently merged the newforms-admin branch into trunk as of
r7967 [1]. This is an extremely backward incompatible change. The
entire admin application in contrib has been refactored. The newforms
module has a few new features, but those changes are backward
compatible. The
On Jul 17, 2008, at 4:26 AM, Ross Lawley wrote:
> Hi all,
>
> The recent changes in newforms admin r7529 changed the validation
> for newforms admin models. However, it is a bit too strict and
> doesn't allow customizable admin forms to output non model fields.
>
&g
Sorry gmail munged the ticket url: http://code.djangoproject.com/ticket/7790
On Jul 17, 11:26 am, "Ross Lawley" <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> The recent changes in newforms admin r7529 changed the validation for
> newforms admin models. However, it is
Hi all,
The recent changes in newforms admin r7529 changed the validation for
newforms admin models. However, it is a bit too strict and doesn't allow
customizable admin forms to output non model fields.
I've added a patch with tests to:
http://code.djangoproject.com/ticket/7790-
On Jul 15, 2008, at 10:50 PM, Brian Rosner wrote:
> The documentation is pretty much done. I would like for people to give
> it some attention and shake out any problems. Not a big deal and can
> be dealt with after a merge. The tutorial needs a bit of
> newforms-admin love. I hav
Hi all,
On 9 sep 2007, 14:36, "Honza Král" <[EMAIL PROTECTED]> wrote an
example newforms-admin snippet that would programmatically add an
inline:
> class CommentOptions( models.Model ):
> enabled = models.Fireld()
> moderators = models.Field()
> ...
>
TECTED]> wrote:
> Hello!
>
> Last Saturday we've gathered in Moscow at Yandex and had a sprint aimed
> at newforms-admin bugs.
>
> It didn't work as smooth and effective that we hoped but all the
> problems are more or less explained by the lack of my experience as a
&g
I'm almost positivie #7353 is no longer an issue. I was getting that
error with oldforms-admin, and once upgrading to newforms-admin it was
resolved.
On Jul 16, 12:16 am, "Joseph Kocherhans" <[EMAIL PROTECTED]>
wrote:
> On Tue, Jul 15, 2008 at 11:50 PM, Brian Rosner &
On Tue, Jul 15, 2008 at 11:50 PM, Brian Rosner <[EMAIL PROTECTED]> wrote:
>
> Hey all,
>
> I wanted to quickly update everyone on the status of the
> newforms-admin branch. It is quite literally a few tickets away! I
> have either fixed or triaged many tickets today so t
Hey all,
I wanted to quickly update everyone on the status of the
newforms-admin branch. It is quite literally a few tickets away! I
have either fixed or triaged many tickets today so that the branch can
get merged into trunk. The tickets triaged really shouldn't have been
made blocker ti
Hello!
Last Saturday we've gathered in Moscow at Yandex and had a sprint aimed
at newforms-admin bugs.
It didn't work as smooth and effective that we hoped but all the
problems are more or less explained by the lack of my experience as a
sprint organizer. We'll try h
n Grady <[EMAIL PROTECTED]> wrote:
>
> > I know it's kind of late to bring this up, but I haven't been using the
> > branch,
> > so it hasn't been at the front of my mind at all :)
>
> > newforms-admin currently uses a url match of ^admin/(.*) whic
put it all together. If there is any interest in this
at all I can put together a prototype.
On Jul 7, 11:24 pm, Collin Grady <[EMAIL PROTECTED]> wrote:
> I know it's kind of late to bring this up, but I haven't been using the
> branch,
> so it hasn't been at the
I know it's kind of late to bring this up, but I haven't been using the branch,
so it hasn't been at the front of my mind at all :)
newforms-admin currently uses a url match of ^admin/(.*) which sort of kills
reversing - you can't just pass the parts in, you have to manual
> It works for me. If the print statement is not working then see about
> tracking it down and post a detailed ticket with what is happening.
> Also you will want to make sure you are returning the value from the
> super call. The parent save method will return an instance that is
e sure you are returning the value from the
super call. The parent save method will return an instance that is
needed else where in the newforms-admin views.
A quick side note, it is best to ask these question on the django-
users mailing list. django-developers is meant for the development of
to return
>
> super(YourModelForm, self).save(commit)
>
> in it.
>
> On Jul 2, 9:10 am, John Boxall <[EMAIL PROTECTED]> wrote:
>
> > Hi everyone!
>
> > I'm just trying out newforms admin - it's fantastic. I can't wait
> > until this make
Sure,
just remember to return
super(YourModelForm, self).save(commit)
in it.
On Jul 2, 9:10 am, John Boxall <[EMAIL PROTECTED]> wrote:
> Hi everyone!
>
> I'm just trying out newforms admin - it's fantastic. I can't wait
> until this makes it's way into
Hi everyone!
I'm just trying out newforms admin - it's fantastic. I can't wait
until this makes it's way into trunk -
A question -
I'd like to add custom behavior when a object is saved in the admin
console.
I'm following this example of how to add custom behavio
8-06-28 at 06:12 -0700, ionut wrote:
> > I do'nt consider to be a MVC good pattern rendering form html inside
> > newforms class.
>
> A form class is purely presentational, so there's no "MVC" (or whatever
> you might want to call it -- you can't do MVC o
Wow, we're a bit quick on the draw, huh? :)
On Jun 30, 2008, at 21:39, Malcolm Tredinnick <[EMAIL PROTECTED]
stick.com> wrote:
>
>
> On Tue, 2008-07-01 at 10:31 +0800, Simon Li wrote:
>> Hi Guys;
>>
>> I use Django newforms,I met a problem
> [...]
On Jul 1, 12:31 pm, Simon Li <[EMAIL PROTECTED]> wrote:
> Hi Guys;
>
> I use Django newforms,I met a problem
Hi, this is the wrong list to post your question about *using* Django,
next time post your question to django-users
>
> UserRole=(['admin','
On Tue, 2008-07-01 at 10:31 +0800, Simon Li wrote:
> Hi Guys;
>
> I use Django newforms,I met a problem
[...]
> I want to get ride of the , could you guys help me?
Please post questions like this to the django-users list. This list
(django-developers) is for the development of D
Questions of this nature should go on django-users, not
django-developers - this list is for the development of Django itself,
not usage questions :)
--
Collin Grady
Sentimentality -- that's what we call the sentiment we don't share.
-- Graham Greene
--~--~-~--~~-
Hi Guys;
I use Django newforms,I met a problem
UserRole=(['admin','administrator'],['user','Normal User'])
user_role =
forms.CharField(widget=forms.RadioSelect(choices=UserRole),error_messages={'required':u'You
must choose one!'})
the
On Sat, 2008-06-28 at 06:12 -0700, ionut wrote:
> I do'nt consider to be a MVC good pattern rendering form html inside
> newforms class.
A form class is purely presentational, so there's no "MVC" (or whatever
you might want to call it -- you can't do MVC on the
I do'nt consider to be a MVC good pattern rendering form html inside
newforms class.
I think a better proach while rendering html forms is to use a
template file
A proff of concept:
class BaseForm(StrAndUnicode):
...
def __unicode__(self):
t = get_template('default
Unfortunately, this wasn't my idea.
I just triaged it three months after anonymous came up with said patch.
http://code.djangoproject.com/changeset/7735/1214331065
signature.asc
Description: OpenPGP digital signature
y it should
probably stay ``form_class``.
>> 2. What should we do with the ``follow`` argument?
> [...]
>> b. We could issue a deprecation warning if ``follow`` is used,
>> letting people know that generic views now use newforms and to use
>> ``form_class`` if you ne
ent?
[...]
> b. We could issue a deprecation warning if ``follow`` is used,
> letting people know that generic views now use newforms and to use
> ``form_class`` if you need a custom form. This would be a bit more
> backwards compatible, since if you aren't using ``follow`` everything
the class-based view enhancements.
> In order to enable custom newforms-style forms, Brian has added a
> ``form_class`` argument to the views, which I think is the correct way
> to replace the functionality lost by the ``follow`` argument.
>
> There are a couple design decisions
`` argument, however, is
specific to oldforms Manipulators and was used for showing/hiding form
fields (see [2] for a refresher of the follow argument).
In order to enable custom newforms-style forms, Brian has added a
``form_class`` argument to the views, which I think is the correct way
to replace
Thanks for the links, I was sure someone had done this before. Looks
like they're scanning the models.py source code and finding the
information there. I think it would be easier and cleaner to generate
it dynamically.
@oggie rob, @russ magee
Yep, it would only ever be needed once, and cluttering
On Wed, Jun 11, 2008 at 1:22 PM, Will Hardy <[EMAIL PROTECTED]> wrote:
>
> Hi all,
>
> is anyone planning to write, or has anyone already written a script to
> help people convert their oldforms-admin to newforms-admin?
...
> Would this be useful enough to include in dj
> Would this be useful enough to include in django itself?
This could be posted somewhere on djangoproject.com or
djangosnippets.org. I wouldn't recommend using the management commands
- this is a one-off operation and there's no need to change django
itself (besides, people will probably want to
all,
>
> is anyone planning to write, or has anyone already written a script to
> help people convert their oldforms-admin to newforms-admin?
>
> If not, I was thinking of writing a little script (mangement comand)
> that would find all the oldforms-admin definitions in installed
Hi all,
is anyone planning to write, or has anyone already written a script to
help people convert their oldforms-admin to newforms-admin?
If not, I was thinking of writing a little script (mangement comand)
that would find all the oldforms-admin definitions in installed models
and output a
On Jun 1, 8:20 am, "Yuri Baburov" <[EMAIL PROTECTED]> wrote:
> So, how about an idea of adding request, object, and action to
> ModelAdmin instances in newforms-admin code rather than in user code
> and refactoring newforms-admin code based on this decision?
We've
On Sunday 01 June 2008 08:20:13 Yuri Baburov wrote:
> However, I don't want to apply threadlocal patch -- why it's not
> added to django yet if it is the best way to go?
What do you mean the 'threadlocal patch'? You can add a threadlocal
middleware without patching Django itself.
http://code
x27;, '')]+editable
And so on.
So, how about an idea of adding request, object, and action to
ModelAdmin instances in newforms-admin code rather than in user code
and refactoring newforms-admin code based on this decision?
--
Best regards, Yuri V. Baburov, ICQ# 99934676, Skype:
I already figured it out, by following the Django source I came up
with something like this to solve the problem:
def formfield_for_dbfield(self, db_field, **kwargs):
if db_field.name == 'sites':
kwargs['initial'] = Site.objects.filter(pk=settings.SITE_ID)
return s
I am in the middle of porting some code to the newforms admin branch.
One of the fields in my models was as follows:
sites = models.ManyToManyField(Site)
...where 'Site' is django.contrib.sites.models.Site
Before switching to the newforms admin branch, if I created a new
entry in
On May 29, 12:21 am, "Honza Král" <[EMAIL PROTECTED]> wrote:
> We had some discussions during PyCon in Chicago, the biggest issue we
> have with the hooks is the amount of code needed to change the widgets
>
> we talked with Joseph about something like widget-sets, a mapping prom
> either field, o
t; wrote:
>
> We (GCap, large commercial radio company in the UK) have been
> developing against the newforms-admin branch for a few months now, and
> based on that experience I have a number of suggestions for simple
> hooks that could be added to make it easier to customise.
>
&g
We (GCap, large commercial radio company in the UK) have been
developing against the newforms-admin branch for a few months now, and
based on that experience I have a number of suggestions for simple
hooks that could be added to make it easier to customise.
1. Provide a custom template for a
taset. Just like the edit_inline functionality found in
the admin. All your other issues deal directly with newforms yourself.
I would give the newforms and modelforms documentation again.
newforms: http://www.djangoproject.com/documentation/newforms/
modelforms: http://www.djangoproject.com/do
On 2008-05-27 05:33:01 -0600, "Russell Keith-Magee"
<[EMAIL PROTECTED]> said:
> Is there any particular reason that you can't just add a Meta class to
> this class definition, in the same way that a ModelForm works:
>
> class ArticleFormSet(FormSet)
> class Meta:
> form = ArticleFor
I'm a Django newbie, so please pardon me if I am asking stupid
questions or raising issues long-solved,
but ...
I have some requirements similar to these that you are discussing for
'formsets', and maybe my experience can help a little..
I went ahead and built myself a 'formset' factory, of sort
On Wed, May 21, 2008 at 8:44 AM, Russell Keith-Magee
<[EMAIL PROTECTED]> wrote:
>
> However, that said: I might be missing something here, but we've just
> gone through the process of deprecating form_for_model and
> form_for_instance based upon the reasoning that a class based form
> definition i
t;[EMAIL PROTECTED]> wrote:
>
> On Wed, May 21, 2008 at 5:56 AM, Brian Rosner <[EMAIL PROTECTED]> wrote:
>>
>> Hello all,
>>
>> The newforms-admin branch is getting close to finalizing the formset
>> API. However, to do so we would like to run it by the d
On Wed, May 21, 2008 at 5:56 AM, Brian Rosner <[EMAIL PROTECTED]> wrote:
>
> Hello all,
>
> The newforms-admin branch is getting close to finalizing the formset
> API. However, to do so we would like to run it by the developer
> community for ideas. I have posted a d
Hello all,
The newforms-admin branch is getting close to finalizing the formset
API. However, to do so we would like to run it by the developer
community for ideas. I have posted a diff [1] of documentation showing
the API. The diff shows the API without a leading underscore on the
Thanks, I found an example at the bottom of this page
http://www.kryogenix.org/days/2008/03/28/overriding-a-single-field-in-the-django-admin-using-newforms-admin
On Fri, 2008-05-09 at 03:16 +0200, Honza Král wrote:
> you can define a fomrfield_for_dbfield method on the ModelAdmin and
> ov
you can define a fomrfield_for_dbfield method on the ModelAdmin and
override the default formfield, supply it with an initial value, that
should work.
On Fri, May 9, 2008 at 3:14 AM, Rob van der Linde <[EMAIL PROTECTED]> wrote:
> Hi, I have some code that I wish to move over to the newfo
Hi, I have some code that I wish to move over to the newforms admin
branch. So far I have been able to convert my models no problem to the
new syntax.
One of my models has a many to many field to the Sites model that comes
with Django. The field is a required field, and prior to moving to the
ROTECTED]> wrote:
> whats wrong with overridng save, then calling the super.save() ?
>
> On May 2, 8:10 am, Alen Ribic <[EMAIL PROTECTED]> wrote:
>
> > At the moment, it doesn't seem that a developers can do pre-save/post-
> > save work c
whats wrong with overridng save, then calling the super.save() ?
On May 2, 8:10 am, Alen Ribic <[EMAIL PROTECTED]> wrote:
> At the moment, it doesn't seem that a developers can do pre-save/post-
> save work cleanly when dealing with Forms in New
At the moment, it doesn't seem that a developers can do pre-save/post-
save work cleanly when dealing with Forms in NewForms Admin using
django.newforms.models.ModelForm.
For instance, if I'd like to send a notification email to a client
once a form has been submitted for the first time
27; ...but it seems that the newforms-admin
> form doesn't get the error message.
>
> -al
>
> On Apr 30, 8:22 pm, Alrex <[EMAIL PROTECTED]> wrote:
>
> > As per the doc:
>
> > """Note that any errors raised by your Form.clean() override wil
*Correction:
I run a debug on BaseForm and can say that the error does get appended
to the field named '__all__' ...but it seems that the newforms-admin
form doesn't get the error message.
-al
On Apr 30, 8:22 pm, Alrex <[EMAIL PROTECTED]> wrote:
> As per the doc:
>
onfirm that my ModelForm-based class raises a
forms.ValidationError in clean() method.
The non_field_errors() is empty (empty ErrorList) even when error is
raised. No error message is displayed on top of my newforms-admin form
as it should to my understanding.
-Alen
--~--~-~--~~---
date_hierarchy is broken for me when filtering models with a nullable
date field and at least one instance is None. It raises an
AttributeError " 'NoneType' object has no attribute 'year' ". It seems
the error could be in line 265 of admin's admin_list.py.
Could someone confirm to open a ticket i
On Sun, Apr 27, 2008 at 1:02 PM, Marcob <[EMAIL PROTECTED]> wrote:
> I found that after queryset-merge in newforms-admin date_hierarchy
> filter doesn't work anymore: years and month are repeated.
Thanks for reporting this, Marco. Turns out the bug was a few layers
deeper
On Sun, Apr 27, 2008 at 1:02 PM, Marcob <[EMAIL PROTECTED]> wrote:
> I found that after queryset-merge in newforms-admin date_hierarchy
> filter doesn't work anymore: years and month are repeated.
For the record, this bug exists in trunk, also. I'm going to take a
loo
On Apr 27, 2008, at 12:02 PM, Marcob wrote:
>
> I found that after queryset-merge in newforms-admin date_hierarchy
> filter doesn't work anymore: years and month are repeated.
> To fix it I wrote this quick hack in django/contrib/admin/
> templatetags/
> admin_list.py:
C
I found that after queryset-merge in newforms-admin date_hierarchy
filter doesn't work anymore: years and month are repeated.
To fix it I wrote this quick hack in django/contrib/admin/templatetags/
admin_list.py:
Line 240:
-days = cl.query_set.filter(**{year_field: year_l
The current behaviour of BooleanField kind of negates the need for
NullBooleanField.
Contrary to the docs (and I'm pretty sure there's a ticket for it) a
BooleanField(required=True) doesn't actually fail validation if a
widget.
Personally, I like this behaviour better. Would we be losing any
fun
ser/howto questions
there.
> I have a form instance in the var form.
>
...
> class AdminDateWidget(forms.TextInput):
> class Media:
> js = ('just_testing.js',)
...
> I took this code from the django newforms-admin branch.
> I'm not sure if the cl
#x27;just_testing.js',)
def __init__(self, attrs={}):
super(AdminDateWidget, self).__init__(attrs={'class':
'DateField'})
--
I took this code from the django newforms-admin branch.
I'm not sure if the class Media is a part of the newforms-admin
framework or it belo
> Same goes for ignoring pyc files everywhere.
You can tell Subversion to add global ignores on your side of it.
See ~/.subversion/config. As for Windows, I don't know.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
be a
huge oversight. Same goes for ignoring pyc files everywhere.
--Ned.
http://nedbatchelder.com
Malcolm Tredinnick wrote:
> On Sat, 2008-04-19 at 05:02 -0700, Marcob wrote:
>
>> On 19 Apr, 13:37, Marcob <[EMAIL PROTECTED]> wrote:
>>
>>> I just exporte
On Sat, 2008-04-19 at 05:02 -0700, Marcob wrote:
> On 19 Apr, 13:37, Marcob <[EMAIL PROTECTED]> wrote:
> > I just exported newforms-admin branch e try to apply this
> > patchhttp://code.djangoproject.com/ticket/7028
> > It fails on django/contrib/admin/templateta
On 19 Apr, 13:37, Marcob <[EMAIL PROTECTED]> wrote:
> I just exported newforms-admin branch e try to apply this
> patchhttp://code.djangoproject.com/ticket/7028
> It fails on django/contrib/admin/templatetags/admin_list.py because it
> is in DOS mode!!!
> Why on earth?
I just exported newforms-admin branch e try to apply this patch
http://code.djangoproject.com/ticket/7028
It fails on django/contrib/admin/templatetags/admin_list.py because it
is in DOS mode!!!
Why on earth?
Ciao.
Marco.
--~--~-~--~~~---~--~~
You received this
On Apr 17, 5:04 pm, "Jeremy Dunck" <[EMAIL PROTECTED]> wrote:
> Middleware is easy to set and forget. Is there a reason not to make
> SecureForm the default, and InsecureForm for people using Ajax? ;-)
I'm pretty sure we can handle the Ajax case by not doing CSRF token
checks if request.is_ajax
On Thu, 17 Apr 2008 09:21:18 -0700 (PDT), "mrts" <[EMAIL PROTECTED]>
said:
>
> > Middleware is easy to set and forget. Is there a reason not to make
> > SecureForm the default, and InsecureForm for people using Ajax? ;-)
>
> Doesn't fit my workflow. In my case some POSTs are handled internall
> Middleware is easy to set and forget. Is there a reason not to make
> SecureForm the default, and InsecureForm for people using Ajax? ;-)
Doesn't fit my workflow. In my case some POSTs are handled internally
by other libraries (think OpenID).
--~--~-~--~~~---~--~--
On Thu, Apr 17, 2008 at 11:00 AM, Jacob Kaplan-Moss
<[EMAIL PROTECTED]> wrote:
>
> On Thu, Apr 17, 2008 at 10:08 AM, mrts <[EMAIL PROTECTED]> wrote:
> > This is cumbersome and error-prone, thus I propose that a SecureForm
> > or CSRFSecureForm be added to ne
On Thu, Apr 17, 2008 at 10:08 AM, mrts <[EMAIL PROTECTED]> wrote:
> This is cumbersome and error-prone, thus I propose that a SecureForm
> or CSRFSecureForm be added to newforms that would automate the steps
> given above (like CsrfMiddleware does).
Agreed -- I was just talking
ose that a SecureForm
or CSRFSecureForm be added to newforms that would automate the steps
given above (like CsrfMiddleware does).
Btw, Pylons does it (http://pylonshq.com/WebHelpers/module-
webhelpers.rails.secure_form_tag.html ).
--~--~-~--~~~---~--~~
You received th
On 16 Apr, 02:24, Marcob <[EMAIL PROTECTED]> wrote:
> http://code.djangoproject.com/ticket/7028
I just modifed this patch and added a new one for django test suite
(one liner!):
- improved-raw-id-admin-feedback-fixed-regression-test.diff (3.7 kB)
- tests-fix-for-improved-raw-id-admin-patch.patch
http://code.djangoproject.com/ticket/7028
This little patch improves a lot the user feedback experience during
raw-id-fields selection.
When a big table hasn't a clear id (for example just a numeric id) and
an user chooses an item from the popup window, the item description
appears only after s
On Apr 9, 11:56 am, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> they share the same longitudes. But it is reasonable to do it based on
> locale (including using the default locale setting).
Using the locale setting sounds great. Need any help?
--~--~-~--~~~---~--~-
Simon Litchfield said the following:
> Tad ugly though, don't you think? Most platforms/languages/frameworks
> handle the MDY/DMY situation relatively elegantly using some kind of
> setting.
Well I wasn't pitching it as the best solution, just *a* solution :p
--
Collin Grady
Of all forms of ca
On Tue, 2008-04-08 at 18:28 -0700, Simon Litchfield wrote:
[...]
> Am I not the only non-US guy who sees this as a major shortcoming in
> newforms?
It's not a forgotten corner, but we haven't fixed it yet. The idea is to
solve the entire problem, not just the one little piece t
, don't you think? Most platforms/languages/frameworks
handle the MDY/DMY situation relatively elegantly using some kind of
setting.
Am I not the only non-US guy who sees this as a major shortcoming in
newforms?
--~--~-~--~~~---~--~~
You received this message
Simon Litchfield said the following:
> No control is given over how initial date/datetime values are
> rendered, using DateField/DateTimeField.
>
> Clients don't like -MM-DD; who can argue?
>
> At the very least, I propose we at least allow an optional
> display_format string, kinda like inp
No control is given over how initial date/datetime values are
rendered, using DateField/DateTimeField.
Clients don't like -MM-DD; who can argue?
At the very least, I propose we at least allow an optional
display_format string, kinda like input_formats.
More importantly though, I think we ca
On Sat, Mar 29, 2008 at 9:09 AM, Rufman <[EMAIL PROTECTED]> wrote:
> How and when do the django newforms validate forms and add errors to
> the errors dictionary?
As soon as you inspect ``form.errors`` or ``form.is_valid``.
In the future, please ask this question on django-users
Hey Guys
How and when do the django newforms validate forms and add errors to
the errors dictionary?
Im trying to make a dynamic form, so I add the data after creating the
form class and adding the attributes. THis means that I will need to
'manually' call the form validation.
Than
I am still hacking around trying to figure out what exactly is still
having issues in newforms-admin auth. After I updated the patch at
http://code.djangoproject.com/ticket/6083 , I still got a strange and
inconsistant error despite restart after restarts of apache about how
my registration
It has not, it's getting there, the best way to speed it up, is to
contribute :D.
On Feb 17, 12:08 pm, rihad <[EMAIL PROTECTED]> wrote:
> Hi devs,
> I'd like to know whether the "newforms-admin" branch has alr
Hi devs,
I'd like to know whether the "newforms-admin" branch has already been
integrated?
Thanks.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to
e any patches, I will gladly test. I don't even
> > > have a clue where that error would be coming in from. I wish I did.
> > > Thanks for the confirmation, Michael Newman
>
> > You might want to try an svn up. I just merged changes from trunk into
> > the ne
even
> > have a clue where that error would be coming in from. I wish I did.
> > Thanks for the confirmation, Michael Newman
>
> You might want to try an svn up. I just merged changes from trunk into
> the newforms-admin branch, and if I remember correctly, there were
> som
eing worked on
>
> On 15 Feb, 15:27, Michael Newman <[EMAIL PROTECTED]> wrote:
>
> > Could someone confirm that Inline images don't work in Newforms admin?
> > Thanks. Here is the simplest sample code I came up with:
>
> > from django.db impo
ou might want to try an svn up. I just merged changes from trunk into
the newforms-admin branch, and if I remember correctly, there were
some fixes for File/ImageFields on trunk that hadn't made it in to the
branch yet.
Joseph
--~--~-~--~~~---~--~~
You received
1 - 100 of 896 matches
Mail list logo
