All topics

Guide

Oxygen 6 Shortcode: A plugin’s output inside an Oxygen page

A plugin’s output inside an Oxygen page. Learn when to use Shortcode, follow a practical setup, and diagnose common problems.

2 min read · Updated 30 September 2026

Editorial review: builder-first workflow. Practice example; frontend behavior still needs checking in your project.

What it does and when to use it

Render the output of a registered WordPress shortcode. This example focuses on one achievable outcome rather than listing every possible setting.

Before you start

Start with a test page and the data or assets described in the example. The values below are starting points, not universal design defaults.

Worked example: A plugin's output inside an Oxygen page

Scenario: A plugin's output inside an Oxygen page. The goal is a useful result on a real project, not a claim that this scenario was a completed client project.

  1. Check the shortcode name and supported attributes in the plugin’s documentation.
  2. Add Shortcode and enter the shortcode in its content field. Configure the plugin’s own settings in WordPress.
  3. Position the element through the parent Container and builder spacing controls. Keep plugin appearance settings in the provider where appropriate.
  4. Check the frontend while logged out. An empty builder preview may differ from live output; test missing data and inactive-provider behavior on a test site.

Expected result

You should have a plugin's output inside an Oxygen page. Verify the result on the frontend using the same content or object described in the steps. A correct builder preview alone does not establish that links, data or interactions work for visitors.

Troubleshooting

If it prints unchanged, the shortcode may not be registered or its plugin may be inactive. For a shortcode that wraps child content, use Container Shortcode instead.

Checks before publishing

A shortcode does not work unless its provider is active. Check its frontend assets, accessibility and loading behavior.

  • Compare desktop and narrow-screen layouts using actual content.
  • Follow every destination and operate interactive controls with a keyboard where applicable.
  • Check an empty or unavailable-data state when the element depends on a provider.

Official reference and version notes

Official Shortcode reference provides the current provider information. This is independent, AI-assisted documentation on Benjamin Olsen’s website; examples are clearly identified as practice recipes.

The native references were checked against the site’s Oxygen 6.2.0-beta.9 installation and public documentation. Individual recipes should still be validated in your project.

Need more help with this guide? Contact Benjamin →

Explore more topics