Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

RichTextField not visible when used as a field on custom Image model

See original GitHub issue

Issue Summary

RichTextField fields are not visible in the CMS when used as a field on custom Image model.

Steps to Reproduce

I set up a custom image model as described here. I added a wagtail.core.fields.RichTextField as one of the fields, and added that field name to admin_form_fields. I expected the field to appear at /cms/images/{pk} but it does not. Other standard-issue Django fields added in the same way do appear in the CMS.

Technical details

Python version: Python 3.6.4
Django version: Django 2.0.4
Wagtail version: Wagtail 2.0.1
Browser version: Safari 11.1; Chrome 65.0.3325.181

Issue Analytics

State:
Created 5 years ago
Reactions:1
Comments:13 (7 by maintainers)

Top GitHub Comments

1reaction

sir-sigurdcommented, Aug 29, 2019

@gasman, OK, I’ll probably have time to fix it.

1reaction

gasmancommented, May 30, 2018

I think the ‘proper’ fix for this will be to ensure that the edit form’s media property is output onto the page - this should include the necessary draftail.css and draftail.js includes. (However, it may still be lacking some of the additional includes normally found in _editor_js.html, such as modal-workflow.js, and so you might find that some functionality is missing, such as chooser popups.)

Note that having a rich text field within the image model could also cause problems with the ‘upload’ tab of the image chooser popup, because the rich text field may itself trigger popups, and a popup within a popup isn’t officially supported…