| 开发者 |
thiagoqvaz
globalai |
|---|---|
| 更新时间 | 2026年6月1日 17:51 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
[growthai_chat] to embed the chat inline on any pageglobal-ai-chat folder to /wp-content/plugins/, or install via Plugins → Add New on WordPress.Yes. You provide your own OpenAI key in Settings → Geral. OpenAI bills you directly for the usage. The plugin stores the key encrypted in wp_options (AES-256-CBC); the plaintext is read on demand for the chat request only.
Yes, fully. There is no license gate on any feature shipped with this plugin. The Pro addon is a separate plugin distributed outside wp.org; it adds optional SaaS-backed features (managed token billing, mobile app, auto-updates, analytics) but installing or removing it never affects the free plugin's behaviour.
In your WordPress database, in the custom tables wp_growthai_conversations and wp_growthai_agents. Nothing about conversations leaves your site unless you configure a webhook or enable the optional Pro addon.
By default WordPress removes only the plugin files and your data stays. If you enable Settings → Geral → "Eliminar todos os dados ao desinstalar", the plugin's uninstall handler additionally drops its tables and clears every growthai_* option, transient, post meta and cron hook.
No. Visitor chat messages are sent to OpenAI for the agent to reply, and are stored in your DB. Nothing is sent to any analytics provider by the free plugin. See External services below for the full list of endpoints the plugin may contact.
No. The free plugin only contacts api.openai.com, using your own OpenAI API key. The Global AI SaaS (saas.globalai.software) is only contacted when you separately install the optional Pro addon — it is not bundled with this plugin and is never reached from the code shipped here.
name, email,
phone, company) to also accept the Portuguese equivalents
(nome, telefone, telemovel, tel, empresa). Without this,
an agent created with a phone field labeled "telefone" (which
sanitize_dynamic_list slugifies into key="telefone") wrote the
visitor's phone number into the lead_data JSON blob instead of
the dedicated column, so the admin UI displayed "Lead: email"
with no phone visible.handoff_owner_device_id (VARCHAR(64), nullable). When the optional
Pro addon's mobile app takes over a conversation, it stamps the
acting device's UUID here so other mobile devices know to lock the
conversation UI. Adding the column lifts the DB schema version
to 3.1 — dbDelta runs on the next admin load.handoff_active=1, the API handler now fires a new
handoff_visitor_message event on global_ai_chat_notify. The Pro
addon's push relay routes this event to the single owning device
(no fan-out), so the human attendant gets a direct push without
spamming every other paired phone.save_lead_info and the visitor's message has an email/phone,
the safety net in class-api-handler.php was persisting the lead
silently — it now also fires the global_ai_chat_notify action so
push, email and webhook integrations on the Pro side hear about
these captures (previously only AI-tool-call captures triggered
notifications).growthai:collect-agent-fields event. The previous
Save handler only persisted lead_enabled + lead_fields, silently
dropping every extra Pro field rendered in that tab (push triggers,
email summary toggle/recipient/triggers).lead_info_collected action now also fires
the first time a conversation captures any lead field (not only when
every required field is filled). This lets the optional Pro mobile
app / webhooks notify the admin as soon as a visitor becomes
identifiable, even when the agent's lead_fields list demands more
keys than the visitor has provided so far. Strict completion still
fires the action as before.load_plugin_textdomain() so the shipped /languages files load, and a global-ai-chat.pot template for further translations.Tested up to bumped to 7.0, and the legacy-table migration in includes/class-agent.php now interpolates {$wpdb->prefix}growthai_agents directly into the query string (the trusted $wpdb->prefix property concatenated with a hardcoded suffix) instead of going through an intermediate variable that the Plugin Check static analyser flagged.[growthai_chat] shortcode now builds its wrapper attributes through a strict allow-list (third-party filters must return an associative array of data-* names; values are escaped with esc_attr()) and its return value is wrapped with wp_kses_post() before output. Every builder render callback (Gutenberg block, WPBakery element, Elementor widget, Divi/Beaver modules) runs its do_shortcode() return value through wp_kses_post(). WPBakery/Divi do_action('global_ai_chat_shortcode_disabled') capture buffers are also passed through wp_kses_post() before return.growthai_agents table, multi-agent CRUD APIs (create, delete, duplicate, count, max_allowed, can_create), the agent_id=new admin flow and the agent-id REST routing have all been removed. The agent configuration lives in wp_options['growthai_agent'].[growthai_chat] shortcode no longer expose an "agent" parameter — there is only one agent to render.global_ai_chat_resolve_agent_by_id, _by_slug, _all_agents, pre_update_agent, resolve_request_agent) let an external add-on (sold separately, not hosted here) layer a multi-agent system on top without Free needing any knowledge of it.growthai_agents table is copied into the new wp_option so previously-configured installs keep their settings; the table itself is left untouched.GrowthAI_Extensions::is_pro_active(), plan(), plan_name(); dropped the related filters; collapsed if (is_pro_active()) { ... } blocks in admin/agents/api code so a single, unconditional path renders.global_ai_chat_render_license_panel hook to the neutral global_ai_chat_render_above_api_key; the promotional banner is now controlled by the standalone global_ai_chat_show_pro_banner filter that defaults to true.global_ai_chat_model_dropdown_label so extensions can append price multipliers without touching plugin code.global_ai_chat_agent_submenu_highlight instead of branching on add-on presence.admin/js/admin-script.js (from 1130 to 330 lines) and admin/js/agents.js; Pro now injects its own JS for the features it ships.Atendimento ativo badge, license-tab callouts, platform-quota notices) from class-admin-settings.php and admin/js/conversations.js.GrowthAI_Vector_Store_Free) which calls api.openai.com directly with the customer's key — no Pro addon required.wp_check_filetype_and_ext and is_uploaded_file; preset icon paths sanitised against traversal and run through wp_kses before output.global-ai-chat text domain.content_sync Pro feature so Free skips the query entirely; tab redirects whitelisted; brand strings renamed to "Global AI Chat".class-smtp.php, analytics.js, meta-box.js; widget footer simplified to passive Powered by Global AI Chat attribution.api.openai.com. All optional SaaS endpoints moved to the Pro addon.wp_kses before rendering; visitor session tokens use window.crypto.getRandomValues (Math.random fallback only on legacy browsers).global-ai-chat text domain).Domain Path: /languages header added.global-ai-chat).GrowthAI_Extensions) lets Pro hook cleanly into Free.