Rich Editor

The Rich Editor of QOR is based on Redactor editor.

Set the type of field as rich_editor, et voila!

Currently, if the content added/managed via the Rich Editor needs to comply with Accessibility needs, the administrator using QOR Admin should edit the raw HTML after using the Rich Editor, to be sure, to be sure, to be sure.

product.Meta(&admin.Meta{Name: "Description", Type: "rich_editor"})


type RichEditorConfig struct {
    AssetManager         *Resource
    DisableHTMLSanitizer bool
    Plugins              []RedactorPlugin
    Settings             map[string]interface{}


File/Image uploading support, first, create an asset manager provided by Media library, then configure it to be attached to a Rich Editor.

import ""

// Add Asset Manager, for rich editor
assetManager := Admin.AddResource(&asset_manager.AssetManager{}, &admin.Config{Invisible: true})

product.Meta(&admin.Meta{Name: "Description", Config: &admin.RichEditorConfig{AssetManager: assetManager}})


By default, rich editor's content will be filtered by QOR's default HTMLSanitizer powered by bluemonday before save, set it to true to skip it.


With Plugins, you can add Redactor plugins and/or create your own Rich Editor plugin and use either/both with Rich Editor:

product.Meta(&admin.Meta{Name: "Description", Config: &admin.RichEditorConfig{
  AssetManager: assetManager,
  Plugins:      []admin.RedactorPlugin{
    {Name: "medialibrary", Source: "/admin/assets/javascripts/qor_redactor_medialibrary.js"},
    {Name: "table", Source: "/js/redactor_table.js"},
  Settings: map[string]interface{}{
    "medialibraryUrl": "/admin/product_images",


Pass redactor settings as json to rich editor, refer above example.

Common Meta types

results matching ""

    No results matching ""