Custom endpoint content

Every custom endpoint has a Content field. Whatever you put there renders on that endpoint’s account page.

What the field accepts

• Formatted text and HTML markup.
• Shortcodes from other plugins, including form plugins.
• Page-builder output that is expressed as a shortcode.

Line breaks and paragraphs in the stored content are preserved on output.

Embedding forms and shortcodes

Shortcodes in endpoint content are expanded when the page renders, so form plugins work. For example, to embed a contact form:

[contact-form-7 id="123"]

The stored content is sanitised on save, then shortcodes are expanded on output. Because sanitising happens before shortcode expansion, the input, select and textarea controls that form-plugin shortcodes generate survive and render correctly.

Content sanitisation and trust

Endpoint content follows the same trust model WordPress uses for post content:

• Users with the unfiltered_html capability (typically administrators on a single site) keep their raw markup.
• All other users have their content passed through wp_kses_post() on save.

Embed the default dashboard

To show WooCommerce’s stock dashboard panel inside a custom endpoint’s content, add:

[default_dashboard_content]

See Shortcodes and block.