Known incompatible themes and plugins

What usually conflicts with KanbanWP, including REST API blockers, caching and minification, and menu restrictors, and how to test with a default theme.

We do not maintain a list of specific themes or plugins that break KanbanWP, because we have not verified one. What we can tell you is the kinds of software that tend to cause trouble for any plugin with a JavaScript interface backed by the REST API, and how to find the culprit on your own site in a few minutes.

Why conflicts happen

The KanbanWP board runs in the browser. It loads its own scripts and styles, and it reads and writes data through the REST API under /wp-json/kanbanwp/v1/, authenticating with your login cookie and a nonce. Anything that interferes with those three things can break it: the scripts, the REST routes, or the logged-in session.

What typically conflicts

REST API blockers

Some security and hardening tools restrict the REST API, for example to logged-out users only, to core routes only, or to an allowlist. Symptoms are a board that never loads, 401 or 403 errors in the browser console, or changes that do not stick. If you use such a tool, allow the kanbanwp/v1 namespace for logged-in users.

Aggressive caching and minification

  • Page caching can serve a logged-out copy of a page with an embedded board to everyone. Exclude pages with a board shortcode or block from the cache.
  • API caching by a plugin, server or CDN can return stale or wrong data. Do not cache /wp-json/ responses for logged-in users, and make sure the X-WP-Nonce header is passed through.
  • Minify, combine and defer options can reorder or break scripts. Exclude KanbanWP’s files, found under /wp-content/plugins/kanbanwp/, from combining, delaying and deferring.

Admin-menu and role restrictors

Plugins that hide admin menu items, or that rewrite roles and capabilities, can remove access to KanbanWP screens. These screens need the kanbanwp_manage capability. If a menu item is missing or you see “not allowed to access this page”, check what the restrictor does with the KanbanWP menu and capability. See Troubleshooting.

Themes that change the front end of embedded boards

Embedded boards render inside your theme’s page. Heavy custom CSS or a page builder that wraps content in unusual containers can affect layout. This usually shows as spacing or width problems, not broken data.

How to test for a conflict

Do this on a staging copy if you can.

  1. Open the browser developer console and reload the board. Note any red errors and failed network requests. See Sending diagnostic info to support.
  2. Switch to a default theme such as Twenty Twenty-Four. If the board now works, your theme is involved.
  3. Deactivate all plugins except KanbanWP and test again. If it works, reactivate the others one at a time, testing after each, until the problem returns.
  4. Clear every cache layer: plugin, server and CDN, and your browser. Test in a private window.
  5. Open /wp-json/kanbanwp/v1/boards while logged out. A JSON 401 response means the REST API is reachable.

Once you find the cause, use that product’s exclusion or allowlist settings first, and write to us with the details if the conflict is on our side.

Last updated October 13, 2026