Sending diagnostic info to support

What to collect before you contact KanbanWP support: versions, debug log output, browser console errors and REST responses, and how to remove secrets.

A report with the right details can usually be answered in one reply. Collect the items below, remove anything private, and send them through Contact us.

1. Describe the problem

Write down what you expected, what happened instead, and the exact steps to repeat it. Include the page or screen, the board involved (ID is enough), and the role of the user who sees the problem. Exact error messages are more useful than paraphrases.

2. Versions

  • KanbanWP version: shown on the Plugins screen. You can also find it in readme.txt in the plugin folder.
  • WordPress version and PHP version: both appear under Tools → Site Health → Info. Use Copy site info to clipboard there for a ready-made summary.
  • Active theme and the list of active plugins.
  • Whether the site uses a page cache, CDN or security plugin, and whether it runs on HTTPS.

KanbanWP requires WordPress 5.8 or newer and PHP 7.4 or newer.

3. WordPress debug log

Turn on logging in wp-config.php, above the line that says to stop editing:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

Repeat the problem, then open wp-content/debug.log. Copy the lines that appeared at the time of the problem, not the whole file. Set WP_DEBUG back to false afterwards.

4. Browser console and network

In your browser’s developer tools:

  1. Open the Console tab, reload the page, repeat the problem, and copy any red errors.
  2. Open the Network tab, filter for kanbanwp, and repeat the problem. For any request that failed, note the URL, the method, the status code and the response body.

5. REST responses

If you suspect the API, request a route directly. A logged-out request to this URL should return JSON with the code kanbanwp_unauthorized and status 401:

curl -i https://your-site.com/wp-json/kanbanwp/v1/boards

Send us the status line, the headers and the body. If you get an HTML page or a 404 instead of JSON, say so. See REST API.

6. Remove secrets before sending

Never send these:

  • AI provider API keys.
  • The MCP token, and any Authorization: Bearer header.
  • Application passwords, passwords, and Authorization: Basic headers.
  • Slack or Discord webhook URLs, and webhook secrets.
  • Public link tokens (the kwp_token part of a URL).
  • Cookies and X-WP-Nonce values from copied network requests.
  • The full JSON export from Settings, which contains settings and secrets.

Replace each value with REDACTED. If you ever pasted a key or token somewhere public, rotate it: regenerate the MCP token on the MCP tab, and create a new API key with your AI provider. Do not share a login. We will never ask for your password.

7. Send it

Use the Contact us page and include the items above. Attach screenshots of the problem if they help, but do not screenshot screens that show keys or tokens.

Last updated October 13, 2026