description is now a rich text field

There is an ugly hack in the css to make the body (description field) the proper size.
I can take out the null=True - that allows the column to be null in the
database, like if you're creating one from the command line to test
something. The part I updated was blank=False because that makes it a
required field in forms (and admin).


On Mon, Aug 4, 2014 at 4:16 PM, Ryan Grigsby <notifications@github.com>
wrote:

> In
> knowledge/migrations/0004_auto__chg_field_question_body__chg_field_question_user__chg_field_resp.py:
>
> > +# -*- coding: utf-8 -*-
> > +from south.utils import datetime_utils as datetime
> > +from south.db import db
> > +from south.v2 import SchemaMigration
> > +from django.db import models
> > +
> > +
> > +class Migration(SchemaMigration):
> > +
> > +    def forwards(self, orm):
> > +
> > +        # Changing field 'Question.body'
> > +        db.alter_column(u'knowledge_question', 'body', self.gf('mezzanine.core.fields.RichTextField')(null=True))
> > +
> > +        # Changing field 'Question.user'
> > +        db.alter_column(u'knowledge_question', 'user_id', self.gf('django.db.models.fields.related.ForeignKey')(to=orm['auth.User'], null=True))
>
> It looks like they're still nullable, but for some reason it changed the
> user model?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/ryang-inova/django-knowledge/pull/4/files#r15778085>.
>