When Your AI Says WPVibe Can’t Do Something

Sometimes your AI tells you WPVibe refused a step. Most of the time the cause is a setting on your own site, or a step that needs you rather than the AI. Here are the ones people run into most, what each means, and what to do.

“File editing is disabled on this site”

Your site’s wp-config.php contains define( 'DISALLOW_FILE_EDIT', true );. Hosts and security plugins often add it as a hardening setting (it’s what hides WordPress’s own theme and plugin file editor). It is your site’s setting, not a WPVibe limit, so reconnecting or switching accounts won’t change it.

While it is on, WPVibe can’t create, edit, publish or delete draft or classic themes. Everything else keeps working: posts, pages, page builders, media, settings and plugins. With WPVibe plugin 1.16.2 or newer your AI can still read your theme’s files and your live pages.

You can keep the setting on: ask your AI to propose the theme change as a diff for you or your developer to apply, or to add the PHP as a WPCode snippet instead. To let your AI edit theme files itself, remove that line from wp-config.php or change true to false, or turn off your security plugin’s “disable file editor” option. You can turn it back on when the work is done. WPVibe never changes it for you.

A related setting shows as File modifications are disabled on this site (DISALLOW_FILE_MODS is set). It also blocks plugin and theme installs and updates, WordPress updates, and updates to the WPVibe plugin itself. Some managed hosts set it for you; remove it in wp-config.php or ask your host.

The edit_themes capability is missing

The theme tools need WordPress’s edit_themes permission.

On a multisite network, WordPress gives it only to network Super Admins. To work on theme files, the site needs to be connected as a Super Admin (see Switching the connected WordPress user below).
On a single site, an Administrator without it usually means a security plugin turned off file editing. Turn that option off if you want theme-file edits, or keep working through content and settings.

“WPCode is not installed on this site”

WPVibe adds custom PHP, JavaScript and CSS as snippets through the free WPCode plugin. Install and activate WPCode from Plugins > Add New in wp-admin (search for “WPCode”), then ask your AI to try again.

WPVibe won’t install WPCode for you on purpose: installing it is your opt-in to custom code on the site. New snippets are saved switched off, and you turn them on in WPCode after reading the code. An edit to a PHP snippet switches it off again; an approved edit to a CSS, JavaScript or HTML snippet that is already on keeps it on. If the message says WPCode is installed but not usable, update WPCode.

“This tool needs the free WPVibe plugin”

Posts, pages and settings work without the WPVibe plugin, but uploading images, the draft and classic theme tools, theme file reads, WP-CLI-style commands and the in-site connectivity check need it. Install it from Plugins > Add New (search for “WPVibe”). If it is already installed, check that it is active and that no security plugin or firewall blocks /wp-json/wpvibe/v1/.

“This action requires the WordPress capability …” or permission denied

Your AI acts as the WordPress user you connected with. If that user is an Editor or Author, settings, themes, plugins and other users are off limits, just as they would be for that person in wp-admin. Either have an Administrator give that user the role it needs (Users > All Users) and ask your AI to retry, or switch the connection to an Administrator (below).

Switching the connected WordPress user

Connecting again doesn’t switch users on its own: while the saved connection still works, WPVibe keeps using it. To connect as a different WordPress user, ask your AI to remove the site from WPVibe, then connect it again and approve the link while you’re logged in to wp-admin as that user.

One exception: if the message is about a single post, check that the post still exists. Asking about a post ID that was deleted can produce the same message.

“eval is blocked” and “Command … is not in the allowlist”

WPVibe’s run_wp_cli tool runs a fixed list of WP-CLI-style commands through WordPress itself. It never runs raw PHP, so wp eval, shell commands and a few high-risk command families (such as core, config and site) are refused on every site and plan. These messages are for your AI, not a problem with your account or site.

For PHP that should run on your site, your AI writes a WPCode snippet with code_snippet, saved off for you to review.
For reading options, posts, files or the database, your AI uses the matching command (option get, post list, db query with a SELECT), the REST API, or read_file.
To see every supported command, your AI can run help.

If your AI gives up after one of these, tell it to run help and find another route. A step that truly can’t be done any other way is something we want to hear about at [email protected].