System Info and Diagnostics

JKD Toolkit 4 min read

Two tools answer the question "what state is this site in right now" without visiting your hosting panel, running phpinfo or opening files. Most support tickets close faster when the reports from these two are attached to the first message.

Neither tool changes anything.

They read and display, so running them on a live site at any moment is safe.

#System Info

A snapshot of the environment, on its own page in the theme dashboard.

#The installation card

At the top, status pills for each component: the theme, the companion plugin and the Pro plugin, each in one of three states, active, installed but disabled, or not installed.

This is the fastest answer to "why do I not have the Pro features". You can see at a glance whether the Pro plugin is even present and whether it is switched on.

#The environment card

The PHP version and its limits, the WordPress version, and server details, plus additional blocks that Pro adds. Some rows carry a status, normal or warning, with a tooltip explaining what the value means.

#The copy button

The most useful thing on the page. It collects the whole report as plain text, aligned into columns.

That text is what we ask you to paste into a support request, either in the message or as a text file if it is long.

A screenshot of this page is worse than the copied text.

Text can be read, searched and quoted back to you in a reply. A screenshot can only be squinted at, and half the values are usually cut off.

#The logs card

View and download the framework log. This is not the same file as the WordPress debug.log, and neither replaces the other.

#Diagnostics

On the Tools page, under the Diagnostics tab.

On a free build the tab is visible but locked: it needs the Pro plugin and an active license.

#What it does

Runs a set of checks the moment you press the button, and shows each one as its own row with a status, passed, warning or failed, plus a short explanation and a hint about what to do.

The checks are grouped by category:

Server

PHP version, PHP extensions, memory_limit, max_execution_time, max_input_vars, SSL, file permissions, writability of the uploads folder, upload size limits.

WordPress

WordPress version, WP-Cron, REST API availability.

Theme

Theme configuration and the state of Pro features.

Hub

Connectivity to Hub and the health of the license check.

Its copy button works the same way the System Info one does. Attach both.

#The daily history

These same checks run once a day in the background and the result is kept as a dated snapshot. The history holds thirty days, with older entries cleared on each run, so the panel shows a trend rather than only the current state.

#Email notifications

Off by default, enabled by their own setting.

An email is sent when a check CHANGES state, not while a problem persists.

Green turning yellow or red sends one; staying red does not, and each check has a daily cooldown so the same problem cannot email you every morning. So silence in your inbox does not mean everything is fine, it means nothing has changed since yesterday.

#The most useful thing on this page

A failed check in Diagnostics is not a theme bug. It is something to show your host.

That is why the order is: run Diagnostics first, then open a ticket. A ticket that starts with "the diagnostics say max_execution_time is 30 and my host says they cannot change it" gets a useful answer immediately.

How to diagnose a problem and report a bugMost things that look broken are unfinished rather than broken. Before hunting the cause of a symptom, confirm the basic steps were all completed. Check the basics first The environment meet...Troubleshooting

#Common questions

Diagnostics is greyed out

It needs the Pro plugin and an active licence, while System Info works without either and carries most of the same environment data.

Can running these break anything?

No, both only read, which is why they are safe on a live site at any time of day.

Where is the framework log stored?

Under your uploads folder in the theme's own directory, and the System Info card shows the path, the size and a download button for it.

Everything passes and my problem is still there

Then it is not an environment problem, which is genuinely useful to know, so move on to the debugging steps and to a ticket with both reports attached.

Neither screen will open

The panel is built on the REST API, so a security plugin blocking it is the first suspect, and the WordPress ToolsSite HealthInfo screen carries much of the same environment data while working independently of us.

#Still stuck

Open a support ticket with the copied text from both screens.

Last updated

Was this article helpful?

Related articles

FIND THE ONE THAT FITS YOUR PROJECT

Import a demo, swap the content, adjust the layout. Modern WordPress under the hood, fast even when the site fills up.