Django中TinyMCE的小部件错误

Question

I'm getting this error with TinyMCE in django:

TypeError: init () got an unexpected keyword argument 'widget'

I have followed the instructions as I found them, and don't know why the error is there. Here is the model:

class Article(models.Model):
    """Represents a wiki article"""

    title = models.CharField(max_length=100)
    slug = models.SlugField(max_length=50, unique=True)
    text = models.TextField(widget=TinyMCE(attrs={'cols': 80, 'rows': 30}))#      (help_text="Formatted using ReST")
    author = models.ForeignKey(User)
    is_published = models.BooleanField(default=False, verbose_name="Publish?")
    created_on = models.DateTimeField(auto_now_add=True)
    objects = models.Manager()
    published = PublishedArticlesManager()

The comment "#formatted in ReST" is because the original TextField was using restructuredText. I was able to actually get tinyMCE from CDN and place a very simpel script in the head of the appropriate template. It loaded the wysiwyg editor, but then rendered the saved page with HTML tags visible.

So I added to form declaration as:

from django import forms

from models import Article, Edit, FileUploadHandler

from tinymce import models as tinymce_models

class ArticleForm(forms.ModelForm):
    class Meta:
        text = forms.Charfield(widget=TinyMCE(attrs={'cols': 80, 'rows': 30}))#(help_text="Formatted using ReST")
        model = Article
        exclude = ['author', 'slug']


class EditForm(forms.ModelForm):
    class Meta:
        model = Edit
        fields = ['summary']

class UploadImageForm(forms.ModelForm):
    class Meta:
        model = FileUploadHandler
        image = forms.ImageField()
        fields = ['title']

The editor is there, but upon save its rendering the article with html tags visible. Why is that?

Answer 1

widget is an attribute for form fields, not model fields. You need to move that setting to your form declaration (or formfield_overrides if you're trying to use it in the admin).

To display the marked up content without escaping the HTML tags in a later view, one way is to use the |safe built in filter.