Re: ModelForm.is_valid() doesn't work the first time but does the second

Thank you for your help. I apologize for the typo, but I am calling is_valid() with the parenthesis: >>> uf = UsersForm(u) >>> uf.is_valid() Traceback (most recent call last): File "", line 1, in File "/var/lib/openshift/5678c24389f5cff0330001cd/python/virtenv/venv/lib64/python3.3/site-p

Re: ModelForm.is_valid() doesn't work the first time but does the second

Not studying; I’m working on a website that will be used to register people for an event, but it is my first Django site. I’m aware that I can add to the existing user model, and I may. However, this is just my first attempt to create a model and form and save data to the database. I don’t thi

Re: ModelForm.is_valid() doesn't work the first time but does the second

"First, why does uf.is_valid() return" because you called "uf.is_valid" (note the lack of parenthesis), that's just a reference to the method and does not call it. "Second, why does uf.save() return that stacktrace the first time I call it, but the second time I call it, the object saves? " As f

Re: ModelForm.is_valid() doesn't work the first time but does the second

Sorry I missed. You have valid unknown at the start. Why are you not used django user model and author? Study purpose ,? 3 січ. 2016 05:53 "Michael Molloy" пише: > I'm not sure what could be wrong with the database settings. If I just > create an instance of the model and save it, it saves to the

Re: ModelForm.is_valid() doesn't work the first time but does the second

I'm not sure what could be wrong with the database settings. If I just create an instance of the model and save it, it saves to the database: >>> u.email

Re: ModelForm.is_valid() doesn't work the first time but does the second

Is_valid is working. You have problem with save. Check database setting. 3 січ. 2016 04:18 "Michael Molloy" пише: >ve > This is running in Openshift with Python 3.3 and Django 1.8.4 > > Here's my model: > > class Users(models.Model): > first_nm = models.CharField('First Name', max_length=100)

ModelForm.is_valid() doesn't work the first time but does the second

This is running in Openshift with Python 3.3 and Django 1.8.4 Here's my model: class Users(models.Model): first_nm = models.CharField('First Name', max_length=100) last_nm = models.CharField('Last Name', max_length=100) email = models.CharField('Email Address', max_length=200, unique=

Re: I'm missing something with Models and database migrations

Thank you both. --M On Monday, December 28, 2015 at 1:09:08 AM UTC-6, Peter of the Norse wrote: > > OK. Let’s take a look at the documentation > . > > Here is what you are looking for: > > clas

Re: Could not parse the remainder template inheritance

On Jan 2, 2016 8:11 AM, "Matthew" wrote: > > Actually it turned out this works!! My TextEdit app was being finnicky and made me re-write the entire code instead of just the quotation marks. Thanks for the help! > That seems a bit odd. I can see why just turning off the smart quotes wouldn't help.

Django + Ckeditor

Hello folks! Happy new year! I have a question about ckeditor on django. I configured ok and use ckeditor field on my project model. But when i show the content on a template view, the images only show the [img] tag and the path to file. I think it can be a filter but on the official site there ar

Re: Is it a bad idea to start a project using Django 1.7 at this moment?

Just a general lack of tutorials properly explaining everything I would say. Though I could be wrong as I dont have that much experience. Hosting in general just makes me sick. On Saturday, January 2, 2016 at 9:01:46 PM UTC+6, Tim Graham wrote: > > Yes, it's a bad idea. Django 1.7 is unsupported

Re: Django i18n design rationale

Hi, Am Fri, 1 Jan 2016 15:29:16 -0800 (PST) schrieb Jure Erznožnik : > 1. Expressions gathering vs declaring: Django has utilities to gather > expressions from sources, txt files and also javascript files. While > that by itself is a design choice, it also presents us with problems > such as (pos

Re: Could not parse the remainder template inheritance

And if you like it you should just buy BBEdit from BareBones, been using it for years, it’s great. François > On Jan 2, 2016, at 11:13 AM, Lee Hinde wrote: > > If you’re just getting your feet wet and don’t want to invest in an > editor/IDE just yet, try TextWrangler: > http://www.barebones

Re: Could not parse the remainder template inheritance

If you’re just getting your feet wet and don’t want to invest in an editor/IDE just yet, try TextWrangler: http://www.barebones.com/products/textwrangler/ It’s free and won’t get in your way. > On Jan 2, 2016, at 8:11 AM, Matthew wrote: > > A

Re: Could not parse the remainder template inheritance

Actually it turned out this works!! My TextEdit app was being finnicky and made me re-write the entire code instead of just the quotation marks. Thanks for the help! On Saturday, January 2, 2016 at 10:52:22 AM UTC-5, Matthew wrote: > > Hi James, > > I turned smart quotes off and am still having

Re: Could not parse the remainder template inheritance

Hi James, I turned smart quotes off and am still having the error. I wasn't aware that could cause future errors though, so thanks for the heads up! On Saturday, January 2, 2016 at 12:44:22 AM UTC-5, James Schneider wrote: > > > On Jan 1, 2016 8:08 PM, "Matthew" > wrote: > > > > Hi all, > > > >

Re: Is it a bad idea to start a project using Django 1.7 at this moment?

Yes, it's a bad idea. Django 1.7 is unsupported and no longer receives security updates. Please use at least the Django 1.8 series (the latest is 1.8.8 as of now) which is a long-term support release and will receive security updates until April 2018 as described at https://www.djangoproject.co

Is it a bad idea to start a project using Django 1.7 at this moment?

Hey guys, I am starting work on a website and I was thinking if starting with Django 1.7 is a bad idea or not, since 1.9 is out right now. With 1.7, I feel like hosting will be less of a headache. -- You received this message because you are subscribed to the Google Groups "Django users" group

[ANNOUNCE] Django bugfix releases issued: 1.9.1 and 1.8.8

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2016/jan/02/bugfix-releases-issued/ On a related note: Python 3.2 users, please be advised that we've decided to drop support for Python 3.2 in Django 1.8.x at the end of 2016. We won't break things intenti