| 开发者 | alitayoko |
|---|---|
| 更新时间 | 2026年10月18日 15:15 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
https://github.com/AlitaYoko99/alitayoko-conversation-engine
The generator is optional. All manually authored conversation, presentation, Gutenberg, import/export, and link-preview features continue to work without enabling it.
Conversation builder
[alitayoko_conversation id="123"]
Examples and portability
Three editable English example conversations are created after first activation. Administrators can recreate missing examples from Conversations > Settings without overwriting examples that still exist.
Conversations can be exported and imported as readable, versioned JSON. Imports create new conversations and never silently overwrite existing content. Persistent UUIDs detect repeated imports, while an explicit option allows an independent duplicate copy when desired.
Avatar and message-image references are portable when the matching image already exists on the destination site. AlitaYoko Conversations does not download external media during import. Link-preview text metadata is included directly in the export.
alitayoko-conversations directory to /wp-content/plugins/.No. AlitaYoko Conversations presents conversations that an editor authors in WordPress. It does not provide visitor-to-visitor or visitor-to-agent messaging.
Yes. Each participant can have an individual name, color, avatar, and left/right alignment.
Yes. Messages can be mixed with Narration, Dividers, and System notices in any order. The Editorial preset also provides a bubble-free book/dialogue presentation.
No. Appearance and reveal settings are stored per conversation, so different conversations can use different presets and behavior.
Yes. The AlitaYoko Conversation block is dynamic and is the recommended embedding method. The shortcode remains available for compatibility and non-block contexts.
Yes. Use Conversations > Import / Export. The versioned JSON format includes participants, conversation-flow entries, ordering, colors, appearance, narration, and reveal settings.
Enter a public http or https URL in a Message and choose Fetch preview. WordPress retrieves the page metadata only after this explicit administrator/editor action. The title, domain, and description are stored with the Message. The plugin tries several standard and fallback image sources, including Open Graph, Twitter Card, Schema.org JSON-LD, image-src, suitable page images, and site icons. When a usable preview image is found, the plugin attempts to cache it locally in the WordPress Media Library so frontend visitors do not need to fetch it from the linked site. Editors can also replace or remove the detected preview image manually.
No. Imported content is created as a new conversation. UUIDs are used to detect repeated imports, which are skipped by default. You can explicitly allow an independent duplicate copy.
Authored conversation content is intentionally preserved. If you want to remove it, delete the conversations in WordPress before uninstalling the plugin.
Only when an authorized editor explicitly requests a generated draft. With the WordPress AI Client backend, the prompt and generator inputs needed to create the draft are sent through WordPress to the AI provider configured by the site administrator under Settings > Connectors. Provider terms, pricing, retention, and privacy practices are controlled by that provider. With the self-hosted AlitaYoko Conversation Engine backend, generator requests are sent only to the engine endpoint configured by the site administrator. If that engine is configured to use Research, it may in turn contact the administrator-configured self-hosted search service and selected public source websites. The generator does not make AI requests during ordinary frontend page views.