Sentient Forms
| 开发者 | twptech |
|---|---|
| 更新时间 | 2026年6月19日 11:43 |
| PHP版本: | 8.2 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
安装:
- Upload the
sentient-formsfolder to/wp-content/plugins/, or install the plugin through the WordPress plugin installer. - Activate Sentient Forms in WordPress.
- Open the Sentient Forms admin screen.
- Connect OpenRouter for direct local-first execution, or connect Sentient Forms Managed Execution if you want managed paid usage.
- Create or select an action, map it to a Gravity Forms form, and run a test submission. Current form-action workflows require Gravity Forms.
屏幕截图:
常见问题:
Do I need a paid Sentient Forms account?
No. The plugin is intended to provide a functional direct path through your own OpenRouter credentials. Sentient Forms Managed Execution is optional.
Does Sentient Forms receive my form data when I use direct OpenRouter execution?
No. Direct OpenRouter execution is performed from your WordPress site to OpenRouter. Sentient Forms does not receive direct OpenRouter BYOK/free execution payloads.
Can AI generate Site Context with OpenRouter free models?
No. AI-generated Site Context requires either Sentient Forms Managed Execution or a configured paid, web-capable OpenRouter model because the generation step uses public-site research. Free OpenRouter routes can still be used for supported form-action workflows where the selected model and provider allow them. You can also write Site Context manually without any paid model.
What data is stored locally?
The plugin stores local provider settings, action templates, custom actions, form mappings, execution events, selected results, consent records, and migration records in WordPress.
Can I remove local data?
The plugin includes WordPress personal data export/erase integration for local execution results that contain a verified email address. It also supports retention cleanup for execution events and configurable uninstall behavior.
Which form builders are supported?
Gravity Forms is required for the current form-action workflows. Other form builders are planned but are not supported in this release.
Where is the source for the compressed admin JavaScript?
See "Source" above and assets/dist/SOURCE.md in the package.
更新日志:
- Make generated admin asset source and build instructions prominent for WordPress.org review.
- Harden realtime structured-output requests so reasoning-capable OpenRouter models do not consume the completion budget before returning JSON.
- Fix paginated realtime suggestions and add safe structured-output failure diagnostics.
- Enforce strict OpenRouter JSON Schema output and require structured-capable models for realtime suggestions.
- Harden public realtime suggestions so stale WordPress REST nonces cannot block logged-in visitors; realtime requests now use only the Sentient Forms form-scoped nonce.
- Remove UTF-8 BOMs that could contaminate WordPress JSON responses, add source/package encoding gates, and improve admin diagnostics for invalid JSON responses.
- Remove admin app development source and build tooling from the WordPress.org package, document the public source tag for generated assets, and harden WordPress.org review checks.
- Prepare the WordPress.org production package pipeline, include admin app source for generated assets, and harden serviceware disclosures.
- Initial local-first migration baseline.