| 开发者 |
motherxai1
emtiazzahid |
|---|---|
| 更新时间 | 2026年9月3日 17:13 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
Install and activate the plugin, open AnswerX in the admin menu, paste your API key and click Connect. The plugin validates the key with MotherX and registers your site for crawling in one step.
In the MotherX dashboard. The plugin intentionally does not duplicate those settings: the widget reads its configuration from your account at runtime, so a change in the dashboard takes effect on your site without a plugin update or a cache clear.
Pause it in the MotherX dashboard, under Widget settings. As of 1.1.0 this replaces the plugin's own show/hide toggle, so the setting applies wherever the widget is embedded, not just on this site.
Add one line to wp-config.php:
define( 'ANSWERX_ENV', 'staging' );
Accepted values are production (the default), staging and local. Individual URLs can be overridden with the ANSWERX_API_URL, ANSWERX_WIDGET_SCRIPT_URL and ANSWERX_APP_URL constants, or the matching answerx_api_url, answerx_widget_script_url and answerx_app_url filters — but the API and the widget script must always come from the same environment.
motherx.ai only processes the data explicitly provided through the plugin, such as blog posts, pages, and product listings, plus the questions your visitors ask the widget. For more details, please refer to our Privacy Policy.
Yes. motherx.ai employs advanced encryption protocols and secure servers to protect your data. For additional details, please review our security policies.
New accounts start on a trial. Sign up at motherx.ai — as of 1.1.0 accounts are created in the dashboard rather than through the plugin.
Only its WordPress settings are removed. Your MotherX account, knowledge sources and conversation history are unaffected.
[answerx_search] shortcode no longer makes an API call while rendering your page — it did so on every page view — and no longer ships its own input, button or stylesheet. MotherX renders and styles the field, so it matches your dashboard settings.ANSWERX_ENV in wp-config.php. The old .env support never worked in a released build.manage_options capability, and the widget configuration is no longer written to MotherX from the browser.uninstall.php, which removes the plugin's settings and nothing else.