RICH TEXT HTML HOW TO

RICH TEXT HTML HOW TO

This requires the rich text content to go through a number of validation and conversion steps both between the editor interface and the version stored in the database, and from the database representation to the final rendered HTML.įor this reason, extending Wagtail’s rich text handling to support a new element is more involved than simply saying (for example) “enable the element”, since various components of Wagtail - both client and server-side - need to agree on how to handle that feature, including how it should be exposed in the editor interface, how it should be represented within the database, and (if appropriate) how it should be translated when rendered on the front-end. Rich text fields can specify a features argument to further restrict the elements permitted in the field - see Limiting features in a rich text field.Įnforcing a subset of HTML helps to keep presentational markup out of the database, making the site more maintainable, and making it easier to repurpose site content (including, potentially, producing non-HTML output such as LaTeX).Įlements such as page links and images need to preserve metadata such as the page or image ID, which is not present in the final HTML representation. The editor interface needs to filter out certain kinds of unwanted markup this includes malicious scripting, font styles pasted from an external word processor, and elements which would break the validity or consistency of the site design (for example, pages will generally reserve the element for the page title, and so it would be inappropriate to allow users to insert their own additional elements through rich text). In reality, it’s necessary to give editors a representation of rich text content that is several steps removed from the final HTML output, for several reasons: Managing documents, images, snippets and collectionsĪt first glance, Wagtail’s rich text capabilities appear to give editors direct control over a block of HTML content.Copying and creating aliases to existing pages.Previewing and submitting pages for moderation.Inserting links to documents into body text.Adding a custom clean method to your ModelAdmin models.Customising CreateView, EditView and DeleteView.

Customising IndexView - the listing view.

Customising the user account settings form.

How to use a redirect with Form builder to prevent double submission.

Multi-site, multi-instance and multi-tenancy.

About StreamField BoundBlocks and values.

How to add Wagtail into an existing Django project.How to use StreamField for mixed content.Integrating Wagtail into a Django project.

Rich text html