Troubleshooting

Most problems have a simple cause: a cache that still shows an old page, another plugin that gets in the way, or a server setting. Start with the three checks below, then look for your problem in the sections that follow.

First checks

Update. Make sure WordPress and Urmi are up to date under Dashboard → Updates.
Clear caches. If you use a caching plugin, a CDN or your host's cache, clear it, then reload the page with Ctrl+Shift+R (⌘+Shift+R on a Mac).
Look for a conflict. For editor problems, deactivate your other plugins one by one, ideally on a staging copy of the site, and switch to a default theme such as Twenty Twenty-Five. If the problem disappears, the last plugin you deactivated, or your theme, causes it.

When you ask for help, add the System info report from Settings → Tools.

The editor does not load

The editor stays white, shows a spinner or an error.

Another plugin or your theme may interfere. Deactivate your other plugins one by one and open the editor again after each, to find the one that conflicts. Test on a staging copy of the site if you can.
Security and firewall plugins can block the requests the editor uses to load and save (the WordPress REST API). Check the plugin's log for blocked requests to your own site, and allow them.
Optimization plugins and services that minify or delay JavaScript, such as Cloudflare Rocket Loader, can break the editor. Turn them off for wp-admin and for the editor.
Server limits: very large pages need memory. If System info shows a PHP memory limit under 256M, ask your host to raise it.
Browser extensions such as ad blockers or script blockers can interfere. Try a private window without extensions.

If you see "… is also editing this page", someone else has the page open in the editor. Agree with them who edits it, so you do not overwrite each other's changes.

"Edit with Urmi" is missing

The content type is not enabled. Go to Settings → General and tick it under Post types. See General.
Your role has No access in Settings → Access & roles. See Roles & access.
Your WordPress account may not edit that page, for example an Author trying to edit someone else's page.

Changes do not show on the site

The page is still a draft, or you saved a draft instead of clicking Update. Check the status in the editor's top bar.
A cache shows the old version. Clear your caching plugin, CDN or host cache.
Styles look outdated. Go to Settings → Tools, click Regenerate CSS, then clear the cache. See Site tools.
A template does not appear. In the Theme Builder, a template must be published and have display conditions. Not shown in its status means it has none yet. If two templates target the same pages, the more specific one wins.

The site looks different from the editor

Your theme's styles interfere. Urmi pages use your theme's header, footer and some base styles until you build your own in the Theme Builder. For a clean page, choose the page template Urmi Canvas (no header/footer) or Urmi Full Width in the page settings.
Urmi styles are missing on pages not built with Urmi. Turn on Load Urmi styles on every page in Settings → General.
The uploads folder is not writable. System info shows CSS files writable: No. Urmi then prints styles into each page, which works but is slower. Ask your host to fix the folder permissions.
An optimization plugin combines or delays CSS. Clear its cache, or exclude Urmi's files from it. See Performance.

Fonts do not load

Check Font delivery in Settings → General. With Do not load fonts, Urmi loads none, on purpose.
With Self-hosted, Urmi downloads each font the first time it is used. If your server cannot reach Google Fonts, the download fails and the fallback font shows; it tries again after ten minutes. Switch to Google Fonts CDN or upload the font as a custom font.
A strict content security policy on your server can block fonts from other domains.

Forms do not send email

Urmi saves every submission, even when an email fails. Check Urmi → Submissions first: if the message is there, the form works and only the email is the problem.

WordPress's email is not configured. Many hosts do not send email reliably. Install an SMTP plugin and connect it to your email provider.
The email lands in spam. Send through an SMTP plugin with an address on your own domain.
Spam protection blocked a real person who filled in the form very quickly. Lower Minimum fill time (seconds) in the form's Spam protection settings. See Spam protection.
CAPTCHA fails for everyone. Check that the site key and secret key belong to the same provider and to your domain. See Form settings.

The popup must be published and have display conditions for the page.
Frequency limits how often the same visitor sees it. After you have seen it once, it may not show again for days. Test in a private window.
Check Visitors (everyone, logged in or logged out), Devices and the Who sees it rules. See Popup targeting and Frequency.

Importing fails

The upload fails or stops: the kit may be bigger than the upload limit shown on the card. Ask your host to raise the PHP upload limits (upload_max_filesize and post_max_size), or export the kit without Images & files and move the media separately.
"This is not an Urmi export file": the file is not a template export, or it was changed. Template exports are .json files, site kits are .zip files; they go into different importers. See Export & import templates and Site kits.
The zip PHP extension is missing (System info marks it (missing)): site kits need it. Ask your host to enable it.

After moving the site to a new address

Go to Settings → Permalinks and click Save Changes, to refresh WordPress's address rules.
Go to Urmi → Settings → Tools and click Regenerate CSS.
Use Find & replace… with Links to replace the old domain in your Urmi designs.
Clear all caches.

AI connections

The warning This site is not reachable from the internet on the Connect a client tab — Shown when your site runs on a local address.

Problem	What to do
"The Urmi MCP server is disabled on this site"	The MCP server is off until an administrator turns it on. Go to Urmi → AI & MCP and click Turn on. See AI & MCP overview.
"This site is not reachable from the internet" on the Connect a client tab	Your site runs on a local address. The Claude app and ChatGPT connect from their own servers and cannot reach it. Use Claude Code, Claude Desktop, Cursor, VS Code or Windsurf with an API key instead, or put the site online. See Connect Cursor, VS Code & others.
"HTTPS required"	Connectors need HTTPS. Turn on SSL for your site first.
The connector cannot find your site's sign-in	Check that Settings → Permalinks is not set to Plain, and that Dynamic client registration is on in Server settings.
The sign-in window says "Can't connect this application"	Read the message. "Your account is not allowed to connect AI clients to this site" means your role is not ticked under Allowed roles in Server settings. "The MCP server is disabled on this site" means Server enabled is off: an administrator has to turn it on first.
The app says "Authentication required" or "The access token is missing, expired or revoked"	The key was typed wrong, has expired or was revoked. Create a new key. If the key is right, your server may drop the `Authorization` header: ask your host to pass it through to WordPress. As a last resort, turn on Keys in URLs in Server settings.
"This account is not allowed to use the Urmi MCP server"	The user who created the key has a role that is not allowed any more. Allow the role, or create the key with an allowed account.
"Rate limit reached"	The app made more calls per minute than the rate limit. It usually waits and continues. Raise the limit for large builds.
The app shows no Urmi tools	Restart the app after changing its configuration, and check the connection (in Claude Code, run `/mcp`). Look at AI & MCP → Activity to see whether any request arrived.
An action fails with a permission message	The connection lacks a permission, or your role cannot do it. Check the key's or app's permissions in API keys & scopes. AI apps can never manage plugins, themes, users or site settings, whatever your role. See What AI cannot do.

The Activity tab shows every request with its status, which usually tells you where the problem is.

PHP version or requirements

If WordPress shows Urmi requires PHP 8.0 or newer, your server runs an older PHP version and the plugin stays inactive. Ask your host to switch to PHP 8.0 or newer, then reload. Urmi also needs WordPress 6.6 or newer. See Installation & requirements.

Still stuck?

Ask in the Urmi support forum on WordPress.org (opens in a new tab). Describe what you did, what you expected and what happened, and paste the System info report.