Reporting a Problem
This page explains how to report a problem with the theme or plugin in a way that makes it easier to investigate and fix.
To actually send the report, use the Contact form.
Before Sending Feedback
Section titled “Before Sending Feedback”- Confirm whether the issue affects the theme, the plugin, or both.
- Check whether the problem happens consistently or only in a specific situation.
- If possible, reproduce it on a staging site before reporting it.
What to Include
Section titled “What to Include”Versions
Section titled “Versions”Always include the exact versions involved:
- theme version,
- plugin version,
- WordPress version,
- PHP version.
If you are not sure about the current theme and plugin releases, see Current Versions.
Evidence
Section titled “Evidence”Please include visual evidence whenever possible, in the form of screenshots or screen recordings.
Try to capture:
- the full area where the problem happens,
- the exact action that triggers it,
- the final broken result.
Precise Scope
Section titled “Precise Scope”Describe exactly which parts are involved.
Useful examples:
- The specific block name, such as
Card GridorCourse Program Display. - The specific custom post type, such as
NewsorProjects. - The exact Customizer section, such as
Navigation Bar Options. - Whether the issue is in the editor, the front end, or the WordPress admin area.
- The affected template or page type, such as homepage, archive, single post, or standard page
Reproduction Steps
Section titled “Reproduction Steps”List the shortest sequence of steps needed to reproduce the issue.
Good reproduction steps are:
- specific
- ordered
- repeatable
Example:
- Open the homepage in the block editor.
- Edit the
Home Spotlightblock.- Save the page.
- Reload the front end.
- Notice that the secondary card image is missing.
Expected and Actual Result
Section titled “Expected and Actual Result”Include both:
- what you expected to happen
- what actually happened instead
This helps separate a real bug from an unclear usage expectation.
- Report one problem at a time when possible.
- Use the exact names shown in the UI or in these docs.
- If the issue appears only for a certain browser, device, or user role, say so explicitly.