Common problems
When your agent can't do something, it passes on a message from your site. Every message below means nothing was changed.
Your agent doesn't see Fancy Bricks
- Reload the agent. Claude Code and Cursor read their MCP settings when they start.
- Check the connection. In Bricks › Fancy Bricks › Connect your AI, all four checks must say Ready. See Connect your agent.
- The password was revoked or mistyped. Your agent gets "401 Unauthorized". Create a new password from Connect your AI and paste the new configuration.
License and library
- "This site has no Fancy Bricks license…" Verify your key in Bricks › Fancy Bricks › License. See Install and license.
- "This license is not active, so templates cannot be fetched." Your plan ended. Templates already on the site keep working; renew to fetch new ones.
- "The library does not recognise this site's license key." The key changed or was mistyped. Copy it again from My account › Fancy Bricks plugin and verify it.
- "This site is deactivated or over the license's site limit." Turn the site back on in My account › Fancy Bricks plugin › Sites.
- "Too many templates fetched in a short time." Wait a few minutes and ask again.
- "The template library did not answer." Try again in a moment.
- "The library has no version of this template for the framework this site uses." Check Bricks › Fancy Bricks › Template library: the framework shown there should be the one your site uses.
The page
- "… is editing this page right now." Someone has it open in the Bricks builder. Ask your agent again once it's closed.
- "You cannot edit that page." The password belongs to a user who can't edit that page. Create the password with a user who can.
- "Bricks abilities are switched off on this site…" Turn them on in Bricks › Settings › AI.
The change you asked for
- "… is not a background tested with this template. It offers: …" Pick one of those. Other backgrounds weren't tested with that template's layout.
- "This template has no knob …" The message lists the knobs it has. Not every template has knobs; try a component property or the background.
- "… is not an option of …" The message lists the options, by the names you see in the component's panel.
- "… needs a value of type …" The knob takes a color, a length, a time
or another kind of value, and the message gives examples. Your framework's
variables, like
var(--space-l), always work. - "This section has … more than once." Tell your agent which one, for example "the first button".
- "This section is not a Fancy Bricks template I recognise…" It was built by hand, or renamed. Your agent can still edit it with Bricks' own tools, but without the library's checks.
Inserting a template
-
"… needs …. Turn that on and try again." The template needs something this site doesn't have on yet. The message says what:
- code execution: some templates have a small script (sliders, marquees, tabs). Turn it on in Bricks › Settings › Custom code › Code execution. See Requirements.
- WooCommerce: install and activate it first.
- «Enable advanced modular elements»: some shop templates use Bricks' newer cart, checkout and account elements. Turn it on in Bricks › Settings › WooCommerce.
Your agent can tell you this before inserting: when it searches the library, templates this site can't use yet come with what they need.
-
"… is a header" / "… is a footer" Headers and footers live in their own Bricks template, not inside a page. Create a header or footer template in Bricks › Templates (your agent can do it with Bricks' tools) and insert it there.
-
"… is a page section, and this is a header template." The other way round: insert it into a page.
-
"This template uses Bricks elements this site does not have…" Update Bricks.
After inserting
- A check says it couldn't compare. The section was pasted from an older version of the template. Ask your agent to insert it again if you want the full check.