Initialized a new project this evening and installed django-quill-editor as per usual. When I open the associated CreateView template, I get...

Funny thing is, the quill editor loads correctly in the UpdateView template. The following text is strangely already in the editor...

I've double and triple checked that the model, view, and template are set-up correctly.

EDIT

Realized it might help to add that I am also using django-crispy-forms.

I was looking at the docs but I thing it's missed to be told that {% include 'django_quill/media.html' %} is to be included. I wasted lot of time on this.

The editor works well, but displaying Quill content is kinda.... for and instance object.content will display something of this sort: <django_quill.fields.FieldQuill object at 0x7ff51c405190> What are the suggestions here?

I know this has been asked before #51, but the owner closed the issue without providing any feedback.

Quill editor v0.1.40 works fine on my local computer, but when in production, QuillFileds are invisible on admin panel – only labels appear:

When inspecting the admin page on Chrome, I see such errors on the console:

GET https://mysite.com/static/django_quill/django_quill.css net::ERR_ABORTED 404 (Not Found)

GET https://mysite.com/static/django_quill/django_quill.js net::ERR_ABORTED 404 (Not Found)

Uncaught ReferenceError: QuillWrapper is not defined
    at (index):261:27
    at (index):263:11

django_quill.css and django_quill.js fail to load. I can't figure out why it works on my local project which has the same setup, except that on local I use python 3.9/Django 4.0.1 while in production, it's v3.8/4.0.2.

Another difference is that, in production, django_quill folder is under myenv/lib/python3.8/site-packages/ directory.

On my computer, there is no django_quill folder under myenv/lib/python3.9/site-packages/. In fact, there is no such folder anywhere on my drive, nor the related django_quill.css or django_quill.js files.

I have no problem while migrating from old TextField's, or viewing the content on the templates.

Any suggestion or feedback will be welcomed and greatly appreciated.

Thank you.

When I change an existing field type to QuillField it fails because it is expecting its value to be in the delta/html format {"delta": "...", "html": "..."}, but my current data is just raw HTML. Does anyone have any tips on how to migrate this data?

Related issue #38 and fixes the issue of json

This PR and PR#36 are breaking changes for Django Versions < 3.1.x

The JSONField was introduced in Django 3.1. django-quill-editor will have to drop support for django 3.0.x versions.

I'm working with Django 3.1.8 models.py

class UUIDModel(models.Model):
    class Meta:
        abstract = True

    id = UUIDPrimaryKeyField()
    
class Setup(UUIDModel):
    name = models.CharField(max_length = 255, verbose_name = "Nome")
    content = QuillField()

admin.py

@admin.register(Setup)
class SetupAdmin(admin.ModelAdmin):
    pass

I made the migrations , migrate, all the proccess. The label content appear in the admin but has no field to write....

Hello,

I am trying to integrate the QuillField() into the Django admin. However, when I change the model from textField to QuillField(), I get a QuillParseError whenever I try to edit existing objects in the Django admin.

How would you resolve this error?

this allows the db backend to apply any optimizations it might want/need closes #26

checked everything out in a personal project. i can use the admin panel with a QuillField just fine, multiple edits work fine, and everything renders properly. i also checked my db (postgres) and the json getting stored is correct

If QuillField is not populated, it causes JSONParse error. It can be field by overriding FieldQuill.__init__ with:

def __init__(self, instance, field, json_string):
    json_string = json_string or '{"delta":"","html":""}'
    super().__init__(instance, field, json_string)

After that, QuillField blank and null arguments can be set to True.

Have you considered adding an initial value placeholder?

With what you have now, I doubt it will work with editing pages where there's suppose to be some initial value that is to be displayed on the editor.

Bumps certifi from 2022.6.15 to 2022.12.7.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

I ran into a similar issue as described in https://github.com/LeeHanYeong/django-quill-editor/issues/90#issuecomment-1174955291 and copying that user's suggested solution also fixed it for me.

Hey!

I was trying to use the editor with DRF, but when DRF serializes the field, it just calls str method, which returns that default python str for classes. If we instead return the delta, it will be possible to integrate with the serializer just fine.

I will open a PR to do so.

Problem:

When trying to display iframe from Quill onto webpage, it only displays the html and not the actual iframe

Context:

I am using Quill in my admin backend so that I can easily let an admin user add text and links onto a webpage.

Here is what the backend quill form looks like

I've added safe within the template fields so that URLs display correctly.

<div class="container">
   <br>
   <h2>Where to Buy {{ plant.name }}</h2>
   <div class="affiliate-section">
           {{ plant.affiliate_link.html | safe }}
   </div>