Getting StartedTroubleshooting

Troubleshooting

Fixes for the most common Protuno issues, from the Proton widget not appearing in Elementor to the AI chat not responding, themes not applying, and dynamic content showing raw text.

Find your symptom below and follow the fix. If the issue is not listed, check the Requirements & Compatibility page to make sure your environment is supported.

Proton Widget Does Not Appear In Elementor

Symptom: You search "Proton" in the Elementor widget panel and nothing shows up.

Fixes:

  1. Go to WordPress → Plugins and confirm Protuno is active (status shows "Active", not "Inactive" or "Deactivate")
  2. Confirm Elementor is also active on the same screen
  3. If both are active, deactivate Protuno, save, then reactivate it — this re-registers the widget with Elementor
  4. Clear any server-side or object caches that may be holding a cached widget registry

Edit With AI Tab Is Missing

Symptom: The Proton widget's Style panel shows Edit Code but no Edit With AI button.

Fix: Edit With AI is a Protuno Pro feature. It is not available on the free plan. To build sections on the free plan, use the Edit Code tab (Developer Mode). See Free vs Pro: What's Included for the full plan breakdown.

AI Chat Is Not Responding

Symptom: You type a message in the Edit With AI panel and nothing happens, or you see an error about a missing provider.

Fixes:

  1. Go to Protuno → Settings and open the AI tab
  2. Check that an AI provider is connected and that a valid API key is saved
  3. Verify the API key has credits or an active subscription with the provider
  4. If the key was recently added, save Settings again and reload the Elementor editor

AI Response Is Cutting Off Or Incomplete

Symptom: The AI generates a section but the HTML is truncated mid-tag, or the section only partially renders.

Fixes:

  • Ask the AI to continue: "Finish the section, it was cut off"
  • Simplify the prompt — very complex sections with many elements in one request can exceed the AI provider's response limit
  • Break the request into parts: ask for the header area first, then the body, then the footer of the section

Slots Are Not Appearing In The Content Tab

Symptom: After saving the Proton widget, the Content tab in the Elementor left panel is empty or missing expected text fields.

Fixes:

  1. Click Save inside the code editor (not just the Elementor Update button) and wait for the save to complete
  2. Close and reopen the Elementor panel by clicking away from the widget and back onto it
  3. Check that the HTML has content that Protuno can extract — at minimum, text nodes inside elements like <h1>, <p>, <a>, and <button> are detected automatically

CSS Styles Not Applying

Symptom: Styles you wrote are not reflected in the canvas preview or on the live page.

Fixes:

  1. Confirm your CSS is in the CSS tab, not the HTML tab — CSS inside a <style> block in the HTML tab is not auto-scoped and may be ignored by some hosts
  2. Save the widget and do a hard reload of the Elementor editor (Ctrl+Shift+R / Cmd+Shift+R)
  3. If the live page is cached, clear your caching plugin's cache and reload
  4. Check for CSS rule conflicts — open the browser dev tools (F12) and inspect the element to see which rule is winning

Theme Builder Template Not Applying To A Page

Symptom: You created a Theme Builder template but the site still shows the default theme layout on the target page.

Fixes:

  1. Go to Protuno → Theme Builder, open the template, and verify Display Conditions are set
  2. Check for a conflicting template — if two templates have overlapping conditions, the more specific one wins (Single Post → specific post ID wins over All Posts)
  3. Make sure the template is published (not draft)
  4. If you are using a caching plugin, clear the cache after saving conditions

Dynamic Twig Expressions Showing Raw Text

Symptom: On the front end, you see {{ post.title }} as literal text instead of the post's actual title.

Fixes:

  1. Check for a syntax error — common mistakes are missing closing braces ({{ post.title } instead of {{ post.title }}), wrong quote types, or a typo in the provider name
  2. Check whether the expression uses a Pro-only provider (site.*, user.*, term.*, request.*) — these return empty on the free plan. See Dynamic Data With Twig for which providers are free vs Pro
  3. Make sure you are on a page where the context is correct — {{ post.title }} only resolves on a single post or page, not on a static homepage unless it is assigned as a page

Plugin Conflict Or White Screen After Activating Protuno

Symptom: Activating Protuno causes a white screen, PHP fatal error, or breaks the WordPress admin.

Fixes:

  1. Access your site via FTP or File Manager and rename the /wp-content/plugins/protuno folder temporarily to deactivate it without the WordPress admin
  2. Check your PHP error log for the specific error and the plugin it points to
  3. Deactivate all other plugins, reactivate Protuno, then reactivate other plugins one at a time to find the conflict
  4. Make sure your server meets the minimum requirements

MCP Connection Not Working

Symptom: Your external AI client (Claude, Cursor) cannot connect to your WordPress site through the Protuno MCP integration.

Fixes:

  1. Go to Protuno → Settings → MCP and confirm the integration is enabled
  2. Copy the MCP endpoint URL from that screen — verify you are using the exact URL shown there in your AI client's MCP configuration
  3. Confirm your site is accessible over HTTPS from outside (local or localhost sites require a tunnel like ngrok)
  4. Check that your WordPress user has the permissions needed to perform the actions the AI is attempting
Was this page helpful?