Formatted text with a visual editor
fld-editor="Field name" The WordPress visual editor in one field: headings, lists, bold, links and images. For an “About us” block, a story or terms.
Where it goes
On a block that contains the formatted text, usually a <div> (in Webflow, a Rich Text element). The whole content of the block, with its tags, becomes the field’s starting value.
The field appears in the admin only if the page has a group name: wp-fields-group on its <body>.
Example: the “Our story” block
<div class="story w-richtext" fld-editor="Our story">
<h2>Our story</h2>
<p>We opened in 2019 with one grinder
and a borrowed espresso machine.</p>
</div>We opened in 2019 with one grinder and a borrowed espresso machine.
Now we roast our own beans.
The client added a paragraph in the editor.
What matters
- Put it on a
<div>. WordPress wraps the text in paragraphs itself. - The styles of headings and paragraphs inside come from the site’s CSS for that block, so style the tags inside it, not separate classes.
- For plain text without formatting fld-area is simpler for the client.
Common mistakes
The build log is the “Logs” tab of your project on themeforge.pro; the free markup check shows the same notes.
<p class="lead" fld-editor="Intro">Open every day.</p>On a paragraph: the editor’s own paragraphs end up inside it, and the browser breaks the layout. The log is silent.
<div class="lead" fld-editor="Intro">Open every day.</div>On a <div>.
The same in site settings or on a category
fld-editor | on a page or post |
|---|---|
opt-editor | in site settings |
tax-editor | on a category or tag, such as a category description |
Alternative spelling
f_editor, o_editor, t_editor works the same: the build gives an identical theme.