A WYSIWYG field gives editors the familiar WordPress rich-text editor inside a field group, so a description can have paragraphs, bold text, lists and links without anyone writing HTML.
What It Does
The field stores formatted HTML. It suits content that is genuinely prose but does not belong in the main post body — a specification section, a long description, terms shown in a particular place.
Before You Start
- Nexter Extension is installed and active.
- Content Fields is enabled under Nexter → Content Fields.
- You have a field group, or are about to create one.
Add a WYSIWYG Field
- Go to Nexter → Content Fields and open the Group Fields tab.
- Open a field group, or create a new one.
- Click Add Field.
- Set Field Label to Full description. The Field Name fills in automatically and is what you use in code.
- Set Field Type to WYSIWYG Editor.
- Set a Default Value if new posts should start with boilerplate.
- Click Update.
Field Settings
Every field is configured across four tabs. These are the settings this field type offers, read from the field group builder in Nexter Extension 4.9.0.
General
| Setting | Options | What it does |
|---|---|---|
| Default Value | No help text in the UI. |
Validation
| Setting | Options | What it does |
|---|---|---|
| Required | No help text in the UI. |
Presentation
| Setting | Options | What it does |
|---|---|---|
| Instructions | No help text in the UI. | |
| Tabs | Visual & Text, Visual Only, Text Only | No help text in the UI. |
| Toolbar | Full, Basic | No help text in the UI. |
| Show media buttons | Display the Add Media button above the editor | |
| Delay Initialization | TinyMCE will not be initialized until the field is clicked | |
| Placeholder Text | No help text in the UI. | |
| Wrapper Attributes | No help text in the UI. |
Conditional Logic
| Setting | Options | What it does |
|---|---|---|
| Conditional Logic | No help text in the UI. |
When to Use It
- A long description separate from the post body.
- Care or usage instructions on a product.
- Terms or disclaimers rendered in a fixed position.
Display the Value
The value is HTML, so it must not be escaped with esc_html() — that would print the tags. Run it through the same filter WordPress uses for post content:
<?php
$html = nxt_field_value( 'description' );
if ( $html ) {
echo wp_kses_post( $html );
}Limitations
- Because the value is HTML, it is the one field type where careless output can introduce markup you did not intend. Always pass it through
wp_kses_post()rather than echoing it raw. - Shortcodes are not run automatically. Wrap the value in
do_shortcode()if you need them.
Troubleshooting
The front end shows tags such as <p> instead of formatted text
The value is being escaped with esc_html(). Use wp_kses_post() instead, as in the example above.
Paragraph breaks disappear
If you strip tags anywhere in your own processing, the formatting goes with them. Pass the stored value straight to wp_kses_post().
