Core Admin comfort
The usual WordPress editor on a page with fields
wp-show-editor When a page has a field group, the WordPress editor is hidden on it: everything is edited in fields. If the client also needs free text, such as the company story or terms, wp-show-editor brings the editor back.
Where it goes
On <body>, next to wp-fields-group. No value needed.
wp="post-content" shows the editor’s text on the site, on the <div> where it belongs.
Example: the About page
Markup about.html
<body wp-fields-group="About" wp-show-editor>
<h1 fld-text="Title">About us</h1>
<div class="story" wp="post-content">
<p>We opened in 2019 with one grinder.</p>
</div>
</body>In the admin Pages → About
Content We opened in 2019 with one grinder. Now we roast our own beans.
About
Title About us
On the site About page
About us
We opened in 2019 with one grinder.
Now we roast our own beans.
Above the group’s fields is the familiar editor with headings, lists and pictures.
What matters
- Without
wp="post-content"on the page, the editor’s text never reaches the site. - If the page is one free block of text, the editor is enough; if it has repeating parts, fields work better.
Common mistakes
The build log is the “Logs” tab of your project on themeforge.pro; the free markup check shows the same notes.
Not like this
<div class="story" wp-show-editor wp="post-content">
<p>We opened in 2019.</p>
</div>The attribute not on <body>: the editor stays hidden in the admin. The log stays silent.
Like this
<body wp-fields-group="About" wp-show-editor>
<div class="story" wp="post-content">
<p>We opened in 2019.</p>
</div>
</body>Only on <body>.