WPVibe 1.22: Elementor Pages Checked Before They Save
You switched off an Elementor addon a while back. Its countdown timer still sits on your sale page. Today you ask your AI to add a short FAQ under the pricing, and the save goes through. A week later you notice the countdown is gone. Elementor dropped the widget it no longer knew, and nothing told you.
That’s fixed in WPVibe 1.22, out now on WordPress.org. Before WPVibe saves an Elementor page, it checks every element with Elementor’s own rules. A page with a problem isn’t saved, and your AI is told which element to fix. The same release lets your AI use Elementor’s own AI abilities without switching on Elementor’s MCP setting, makes several changes to a page as one save, and keeps a record of your site’s last PHP fatal errors.
What you can ask for
- Edit an Elementor page without losing pieces of it. Ask “add a FAQ section under the pricing table on the sale page.” Before anything is written, WPVibe checks that every element has its own id, that every widget on the page is installed and active, and that Elementor 4 settings are in the shape Elementor expects. If a widget’s plugin is switched off, the page stays as it was, and your AI hears which element and why, so it can tell you.
- Build Elementor 4 pages with Elementor’s own tools. Ask “build a landing page for the spring workshop as a draft.” On Elementor 4.3 and later, your AI can use Elementor’s own abilities for this, like building a whole layout in one go and editing elements by id. Until now that meant clicking Enable MCP access in Elementor’s settings, which also opens Elementor’s own MCP connection to other apps. Now those abilities work through WPVibe with that setting left off. Everything else keeps the setting as you left it.
- Make five fixes as one change. Ask “fix these five typos on the About page.” Your AI sends all five together, and WPVibe saves them once, as one revision. If one of the five doesn’t match the page, none are saved, and your AI is told which one failed. This works on posts, pages, settings and custom fields.
- Find out what broke your site. WPVibe now keeps your site’s last few PHP fatal errors for 7 days, with the plugin or theme that caused each one. The connection check on the WPVibe page in your WordPress admin names the latest one and what to do next.
The one-revision part matters more than it sounds. Some sites keep only a few revisions per page. Five small edits used to be five saves, and that could push out the revision from before the work started: the one you’d want back if you didn’t like the result. In our test with WordPress set to keep 3 revisions, five separate edits pruned that revision. The same five as one change kept it.
Who this is for
- Elementor sites with a few addons. Addons come and go. Now a page that uses a widget you switched off is caught before a save, not after.
- Anyone building new pages on Elementor 4. Your AI uses the same building tools Elementor made for AI, with no Elementor MCP setting to change and nothing opened to other apps.
- Agencies editing client pages. A round of fixes is one revision, so the client’s version from before your work is still there to go back to.
- Anyone whose site crashed after an update. If you can still reach your WordPress admin, the WPVibe page names the plugin or theme behind the latest PHP fatal error from the last 7 days, so you know what to update or switch off.
How to get started
Already using WPVibe? Update the WPVibe plugin to 1.22.0 from your Plugins page. There is nothing to switch on.
New to WPVibe? WPVibe is an MCP server that connects the AI you already use to your WordPress site. Install the free WPVibe plugin from WordPress.org. Its settings screen has buttons to add it to Claude or ChatGPT, plus a server address for other AI apps. Sign in with a free WPVibe account when your AI asks, then paste the connect line from the same screen into your AI. No passwords ever go in the chat.
Then ask. A good first one on an Elementor site: “Add a short FAQ to my homepage, under the last section.” If anything on the page would stop the save, you’ll hear what and where before a thing is written.
Why it’s worth trusting
Before release we ran 1.22.0 on our test site, a real WordPress install with Elementor 4.3.6, Elementor Pro, WooCommerce and LifterLMS.
- The check on every stored page. We ran it on all 38 Elementor pages and templates on the site. 19 were refused, and every one of them used Premium Addons widgets while that plugin was switched off. With Premium Addons active, all 38 passed. That’s the situation from the top of this post, caught before anything was written.
- Elementor’s setting stayed off. With Elementor’s MCP setting off, WPVibe listed Elementor’s abilities, and the setting was still off afterward. Elementor’s own MCP connection stays closed unless you open it.
- All or nothing. We sent several edits where one didn’t match the page. Nothing was saved, and the answer named the edit that failed.
- A recorded error keeps what helps and drops what doesn’t. WPVibe keeps PHP’s error text, the file inside WordPress and memory use for each error, plus your WordPress, PHP and active plugin versions. It leaves out stack traces, values and request data.
The approvals are the same as with Elementor’s setting on. Building and editing a draft run right away. Anything that deletes, like removing elements or replacing a whole page, waits for your approval in the browser first. WPVibe uses Elementor’s abilities for Elementor 4 elements on new pages and drafts. Classic widgets and changes to a published page still go through WPVibe’s own Elementor save, with the new check in front of it.
What it doesn’t do yet:
- Elementor’s abilities need Elementor 4.3 or later. The ones that build Elementor 4 elements also need Elementor’s Atomic Editor on. It’s on by default for sites first installed on Elementor 4, and often off on older sites. On those, your AI builds with classic Elementor widgets instead.
- The check doesn’t decide which elements may sit inside which. Elementor itself doesn’t enforce that on save, so neither do we.
- The error record covers PHP fatal errors only, and only from 1.22.0 on. It can’t tell you about a crash from before you updated.
Update to 1.22.0 and ask your AI to add a section to an Elementor page. New here? Connect your site with the free WPVibe plugin and the Claude or ChatGPT account you already have.
John