description is now a rich text field

There is an ugly hack in the css to make the body (description field) the proper size.
Sounds good. Do you want to just make that change to your fork?

On Monday, August 4, 2014, 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))
>
> Let's change the forwards migration to have to=orm[user_model_label] as
> well, and we'll just leave it at that. Don't know why it generated the
> other user model.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/ryang-inova/django-knowledge/pull/4/files#r15781550>.
>