Thanks for starting this thread ... just hit this myself porting to
1.2.1 from 1.1.1 ...
On May 18, 4:38 pm, Jori wrote:
> Thanks, you're correct. I don't know how I didn't notice but then
> again it worked just fine with 1.1.1.
>
> -Jori
--
You received this message because you are subscribed
I just ran into this as well. Very odd that earlier versions didn't
raise the same error.
On May 18, 1:38 pm, Jori wrote:
> Thanks, you're correct. I don't know how I didn't notice but then
> again it worked just fine with 1.1.1.
>
> -Jori
>
> On May 18, 11:03 pm, Daniel Roseman wrote:
>
>
>
>
Thanks, you're correct. I don't know how I didn't notice but then
again it worked just fine with 1.1.1.
-Jori
On May 18, 11:03 pm, Daniel Roseman wrote:
>
> It's an integer field, but the choices are all strings. The first
> value in each tuple should be an integer, to match the field.
> --
> DR
On May 18, 8:49 pm, Jori wrote:
> Hi,
>
> I upgraded one of my projects to 1.2 today. I noticed that one of my
> model forms won't validate anymore:
>
> class Review(Entry):
> RATING_VALUE_CHOICES = (
> ('1', _('1. Overpriced')),
> ('2', _('2. Prices above average')),
>
Uups, copypasted the wrong choices list. The format is the same so
don't mind the variable name.
On May 18, 10:49 pm, Jori wrote:
> Hi,
>
> I upgraded one of my projects to 1.2 today. I noticed that one of my
> model forms won't validate anymore:
>
> class Review(Entry):
> RATING_VALUE_CHOICE
Hi,
I upgraded one of my projects to 1.2 today. I noticed that one of my
model forms won't validate anymore:
class Review(Entry):
RATING_VALUE_CHOICES = (
('1', _('1. Overpriced')),
('2', _('2. Prices above average')),
('3', _('3. Average price range')),
('4',
6 matches
Mail list logo
