EP Diagnostics

EP Diagnostics is a single-purpose plugin: it generates a full report of your server environment, installed plugins, and client browser, and lets you copy the whole thing to your clipboard as plain text. When you contact support, paste the report into the email. No more “what PHP version are you on again?”

Published by ElmsPark Studio.

Overview

What the report includes:

PageMotor

• Version number and beta status (e.g. “0.8b”).
• Active frontend theme with version.
• Active admin theme with version.

EP Suite inventory

• Every installed EP plugin with its class name, version, and whether it’s currently active.
• Every non-EP plugin alongside, so support can see if something third-party might be interfering.

Server environment

• PHP version and SAPI (fpm, cgi, cli).
• MySQL / MariaDB version.
• Server software (nginx, Apache, LiteSpeed).
• Operating system.
• Upload limits: upload_max_filesize, post_max_size.
• Memory limit.
• Max execution time.

PHP extension checks

Ticks and crosses for the extensions most EP plugins need:

• curl — outbound HTTP
• openssl — SSL, encryption, JWT
• mbstring — multibyte string handling
• json — obvious
• mysqli — database
• fileinfo — MIME detection for uploads

A red cross next to any of these is almost always the cause of a plugin not working.

Client side (browser)

JavaScript probes and reports:

• Browser name and version.
• Operating system.
• Screen resolution.
• Viewport size.

Useful when a bug might be browser-specific.

Requirements

• PageMotor 0.8.2b or later
• EP Suite base class (bundled)

Installation

1. Download ep-diagnostics.zip from the EP Suite downloads page.
2. Upload via Plugins → Manage Plugins. Activate.
3. Open Plugin Settings → EP Diagnostics. The report is already there.

Using the report

1. Scroll through and check the red/green indicators. Any red is a potential issue worth fixing before it becomes the cause of your support ticket.
2. Click Copy report to clipboard.
3. Paste into a ticket at help.elmspark.com, the community forum, or your support email.

The report is plain text, formatted for readability. No markdown, no HTML — just key/value pairs and section headers.

What EP Diagnostics cannot do

• Fix issues automatically. The plugin is read-only. It reports what it sees; fixes are manual.
• Remote diagnostics. It runs on your server and reports what that server sees. It doesn’t phone home, doesn’t send data anywhere, doesn’t share anything without your explicit copy-paste.

Privacy

Nothing leaves your server unless you choose to share the report. No telemetry, no usage tracking, no analytics. The report is generated on-demand when you open the settings page.

Troubleshooting

“Copy to clipboard doesn’t work”

Browser permissions on clipboard have tightened. Some browsers only allow clipboard writes on user-initiated clicks. If your browser blocks it, select the text manually and Cmd/Ctrl+C.

“The report says an extension is missing but I installed it”

The extension needs to be enabled for the SAPI PHP is running under (usually fpm for web). Check /etc/php/8.2/fpm/conf.d/ for the extension’s .ini file. Reload PHP-FPM after adding it.

“The report doesn’t see my custom plugin”

The plugin must be in user-content/plugins/ and activated in the active theme to appear. Inactive plugins are listed separately with their status greyed out.

“I want to share the report but it contains information I’d rather not make public”

The report is deliberately information-dense for support purposes. It doesn’t contain credentials or personal data, but it does reveal your server software and versions. If you’re pasting into a public forum, skim first and redact anything you’re uncomfortable sharing.

Feedback and corrections

For a quick question about this plugin, EP Support inside your admin is the fastest option. The chat widget sits on every EP plugin settings page and knows which one you’re on, with starter questions and links preloaded for that exact screen.

For anything bigger — a bug report, a feature request, or a “how do I…” that needs a real reply — open a ticket at help.elmspark.com. A real person, helped by AI, writes the reply. Usually within a few hours. Tickets don’t disappear into the void.

Changelog

1.2.13

• Settings language menu. The language menu in this plugin’s settings now lists only the languages it is actually translated into, plus English, so you can no longer pick a language that changes nothing.
• Danish. Adds a Danish translation.

1.2.12

• Brings the shared ElmsPark component up to date. 1.2.11 deliberately kept the older copy of the component every ElmsPark plugin shares; this version moves to the current one, now that it is being released across the suite. The speed fix from 1.2.10 is unchanged.
• Also brings the shared ElmsPark admin layout up to date: the brand-colour control has moved out of the page header into a Branding section in Settings. Nothing else about your settings changes.

1.2.11

• Same speed fix as 1.2.10, with one internal component put back as it was. 1.2.10 accidentally included an early copy of a shared component that every ElmsPark plugin uses, ahead of its planned release. This version restores the copy that 1.2.9 used, so nothing about how your other ElmsPark plugins look or behave changes. The 1.2.10 fix (no more reading the PHP error log on every page load) is unchanged.
• If you are on 1.2.9 or 1.2.10, update to this version.

1.2.10

• Fixes a site-wide slowdown on PageMotor 0.11. Every page on a site running EP Diagnostics, public pages included, got slower as the site’s PHP error log grew, because the plugin read the whole log each time any page loaded. On a site with a 2.6 GB log that added about 4 seconds to every page.
• The Diagnostics screen no longer reads the log while the page is built. The PHP Error Log panel now fills itself a moment after the screen opens, using the same request as the Refresh Log button.
• The log is now read backwards from the end, so showing the last 100 lines costs the same whether the log is 1 KB or 10 GB (reading is capped at 2 MB).
• The panel now shows the log’s size, in red with a note to ask your host to rotate it once it passes 100 MB.
• No other behaviour changed.

1.2.9

• Fixes “Your session has expired. Please reload to ensure your security.” on PageMotor 0.11. The message appeared on this plugin’s admin screens even though you were signed in perfectly normally, and whatever you were doing failed to save.
• Nothing was wrong with your session. PageMotor 0.11 started handling part of the security check that this plugin was already handling itself, and the two together made every save look invalid. The plugin now checks whether PageMotor has already done it.
• Visitors who were not signed in were never affected, on any version.
• There is nothing to reconfigure, and nothing else changed.