Thanks Phil. Seems to do exactly what it promises.
Regards,
Matt.
On Jul 29, 12:10 pm, "Phil Davis" <[EMAIL PROTECTED]> wrote:
> On 26/07/07, Matt <[EMAIL PROTECTED]> wrote:
>
> > Can you confirm that the CRUDgenericviewsare compatible with
> >newforms? I haven't seen any examples of how to do i
On 26/07/07, Matt <[EMAIL PROTECTED]> wrote:
> Can you confirm that the CRUD generic views are compatible with
> newforms? I haven't seen any examples of how to do it, but I'm having
> a hard time believing that this core functionality hasn't been
> implemented (or even patched) for newforms yet.
On 7/27/07, Matt <[EMAIL PROTECTED]> wrote:
>
> 3693 is marked as 'accepted' - does that mean that its changes are in
> trunk?
No - it means that this is a change that we want to make, but haven't
yet. Usually it means that there isn't a patch available, or that the
patch isn't correct. In this c
> The CRUD generic views are using oldforms AFAIK.
Patches 3639 (http://code.djangoproject.com/ticket/3639) and 4636
(http://code.djangoproject.com/ticket/4236) seem to address this
problem, but I've not had any luck applying them.
3693 is marked as 'accepted' - does that mean that its changes a
On Jul 26, 4:50 pm, Matt <[EMAIL PROTECTED]> wrote:
> Hi Etienne,
>
> I read that {{ form.as_table }} was the default value for {{ form }}
> as well, but when I insert {{ form }} into my template I get something
> out which looks like the output of a __str__ method - a list of
> dictionaries and v
Hi Etienne,
I read that {{ form.as_table }} was the default value for {{ form }}
as well, but when I insert {{ form }} into my template I get something
out which looks like the output of a __str__ method - a list of
dictionaries and values.
I'm running Python 2.5 on Ubuntu Feisty. I'll put toget
I think the default value for {{ form }} is {{ form.as_table }}, so
perhaps it is safe to just use the default {{ form }} within a
table element:
{{ form }}
As for this error, it looks like the server didnt finished serving a request
and crashed. Maybe upgrading Python and a couple of pytho
Eric,
It seems I jumped to conclusions too quickly. I'm finding that
{{ form.as_table }}, {{ form.as_ul }} and {{ form.as_p }} cause the
server to error. The page is still served, but the following is in the
terminal where the development server is running:
Traceback (most recent call last):
F
On 25 Lip, 21:38, Matt <[EMAIL PROTECTED]> wrote:
> Hi Eric,
>
> Unfortunately neither of those seem to do anything - the template
> seems to just skip over it. I first tried with the 0.96 release, and I
> have updated to the SVN version with the same result.
>
> Any idea what I'm doing wrong?
No
Hi Eric,
Unfortunately neither of those seem to do anything - the template
seems to just skip over it. I first tried with the 0.96 release, and I
have updated to the SVN version with the same result.
Any idea what I'm doing wrong?
Thanks,
Matt.
On Jul 25, 6:55 pm, "[EMAIL PROTECTED]" <[EMAIL P
Hello,
{{ form.as_ul }} or {{ form.as_table }}, etc, should work for this
purpose.
Hope that helps,
Eric
Matt wrote:
> Hello group,
>
> I'm reasonably new to Django andconfused over how to implement generic
> views for CRUD operations, specifically with respect to newforms. I'm
> using 0.96 for
11 matches
Mail list logo
