Docs FAQ

Technical answers about snippets, safety, and plugin behavior. For licensing and billing, see the product FAQ.

Snippets and storage

In Grafucci Code database tables, not in theme files or wp_posts.

PHP snippets target the frontend unless type and location rules specify otherwise for supported admin hooks.

No. One ZIP from grafucci.com. Pro unlocks with a license key under Settings → License.

We ship Free and Pro in one ZIP with Freemius licensing and our own update channel. See the full answer on the product FAQ (first question).

Safety and recovery

Use Safe Mode (when triggered after a fatal) and error logs to deactivate the snippet quickly. Safe Mode is not always on. Always test PHP on staging first. See Safe mode.

PHP is disabled globally on fresh installs until you enable it in Settings → Safety with a one-time confirmation the first time. Syntax checks, dangerous-function scanning, and duplicate detection run at activation. Runtime errors are logged; Safe Mode can pause execution after critical failures.

AI Connect

The script path in the copied JSON is relative. Cursor looks for it inside the project you have open. If that project is a website and not the plugin folder, Node exits and the server stays red. Put the full path to grafucci-mcp.mjs in .cursor/mcp.json, then reload. Do not paste the site JSON over that file again. Connect Cursor.

Cloudflare’s “Just a moment…” check blocks the script even when a browser can open the site. In Cloudflare, skip the managed challenge and Bot Fight for URI paths that start with /wp-json/grafucci-code/. Reload MCP after the rule is saved.

On older plugin versions the switch posted a request WordPress rejected (“The link you followed has expired”), so the label never changed. Update to 1.5.4 or later. Off stays off after refresh, and Cursor disconnects until you turn it back on.

SSH is for files on a remote computer. Grafucci snippets are stored in WordPress, not as theme files. Use AI Connect to edit snippets. Use GitHub Sync when you want those snippets in the repository.

GitHub Sync (Pro)

No. Tokens are stored encrypted in your WordPress database on your server. OAuth is the recommended connect method. See Security & tokens.

On GitHub Sync, type a commit message and click Push to GitHub. That sends linked snippets whose code changed on the site. Snippets that already match GitHub, or where GitHub is newer, are skipped. Tick a folder under This site to limit the push. Leave those folders empty to include every linked snippet. Pull & push.

GitHub (left) is the repository. Tick the folders the update should scan. This site (right) is optional. Tick a Grafucci folder to limit the update or the push to snippets stored there. Tick none to include every linked snippet.

Multisite

Yes. Licensing is per-site activation for Pro features.

Product FAQ (licensing & billing) →