The Debugging Tab

The Debugging tab in Omnalingo’s settings is the fastest way to gather everything support needs to diagnose a problem. Instead of describing what went wrong, you can share an exact snapshot of your environment — or even a downloadable fixture of the exact page that’s misbehaving.

Go to Omnalingo → Settings → Debugging to open it.

---

The Three Copy Buttons

At the top of the Debugging tab are three copy-to-clipboard buttons. Each one bundles a different slice of diagnostic data.

Copy (Log + Environment)

The most complete option for support tickets. Copies:

• Recent log entries from Omnalingo’s debug log (JSONL format)
• A server environment block — plugin version, WordPress version, PHP version, active plugins, and server configuration

Paste this into your support message when something went wrong and you want to share both the error trail and your setup in one step.

Copy (Environment only)

A compact snapshot without log entries. Copies:

• Plugin version, WordPress version, PHP version
• List of active plugins

Use this when you need to share your setup quickly — for example, when describing a configuration question rather than a specific error.

Copy (Reference)

Copies the full list of Class::method identifiers that can be traced via Function Tracing (see below). Share this if support has asked you to enable tracing for a specific method and you want to confirm you’re configuring it correctly.

---

Debug Log Viewer

Below the copy buttons is an inline log viewer. It displays the most recent entries from Omnalingo’s debug log — by default up to 1,000 entries. The log is stored at:

wp-content/uploads/omnalingo/logs/debug/trace.jsonl

Each entry is one line of JSONL (JSON Lines): a structured record with a timestamp, log level, message, and optional context fields. The viewer presents these in a readable format so you can scan for errors without opening the file manually.

Note

The debug log rotates at 5 MB. Older entries are archived automatically. If you’re looking for something from a while ago and it’s not in the viewer, check the archived files in the same directory.

---

Fixture Export

Use fixture export when you have a hard-to-reproduce bug — something that only shows up on a specific page, or that requires specific user interaction to trigger. Instead of trying to describe the problem, you bundle the page into a downloadable file that support can load and inspect directly.

1. Enter the URL of the problem page in the fixture export form.
2. Give the bug a short title so the file is easy to identify.
3. Choose whether to include real images. Disabling this replaces images with placeholders — useful if your page contains private or sensitive visual content.
4. Click Export. Omnalingo opens the page in a hidden iframe, captures the DOM and any network requests, and packages everything into a downloadable ZIP file.
5. Attach the ZIP to your support request.

The fixture ZIP contains the fully rendered HTML of the page plus a network log of the requests made while loading it. Support can replay the fixture to see exactly what you saw.

Caution

The fixture includes your page’s HTML as rendered — this may include personal content, logged-in user data, or other sensitive information depending on the page. Review the page URL before exporting if you have privacy concerns.

---

Debug Logging

The Debug Logging toggle controls whether Omnalingo writes detailed log entries as it runs. It is on by default.

When enabled, the plugin logs errors, warnings, informational events, and debug-level events to the trace log. These entries are what the Copy (Log + Environment) button and the log viewer display.

If you turn it off, the log stops accumulating new entries. You would normally only turn it off if you have been asked to do so for a specific test, or if the log volume is causing a concern on a very high-traffic site.

---

Function Tracing

Function Tracing is an advanced diagnostic tool that records the exact inputs, outputs, and execution time for specific internal methods. It is off by default — enabling it adds overhead and should only be used when support has asked you to trace a specific operation.

When enabled, you can select which Class::method identifiers to trace using the method picker. A namespace search lets you filter the full list of traceable identifiers quickly. Trace records appear in the debug log alongside regular entries.

Note

Use the Copy (Reference) button to share the full list of traceable methods with support, so they can tell you exactly which one to enable for your issue.

---

Disabling All Debug Features

On production sites where you want to guarantee that debug tools cannot be activated — by any admin, even accidentally — you can hard-lock the entire debugging tab by adding this line to your wp-config.php:

define( 'OMNA_DISABLE_DEBUG', true );

When this constant is defined, the Debugging tab is inaccessible and all debug features are disabled regardless of what the settings say.