| 开发者 | alitayoko |
|---|---|
| 更新时间 | 2026年9月19日 17:22 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
[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. When the remote page exposes a supported preview image, the plugin attempts to cache that image locally in the WordPress Media Library so frontend visitors do not need to fetch it from the linked site.
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.