| 开发者 | uosamuel |
|---|---|
| 更新时间 | 2026年9月5日 04:06 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPL v2 or later |
| 版权网址: | 版权信息 |
ariadne-related-posts folder to /wp-content/plugins/.Not in the free version. Every signal (tags, categories, title overlap) is computed locally, with no external API calls, no account, and nothing to configure. Pro adds an optional AI-powered semantic-matching signal, which does call a third-party API (Voyage AI) using your own API key — entirely opt-in, and the plugin works fully without it.
No. Nothing is ever scored at page-render time. Every related-post list is precomputed in the background (in small, budgeted batches) and simply read from a cache when a page loads.
Yes — auto-insert after your content, or place it yourself anywhere with the [ariadne_related] shortcode, the Gutenberg block, or a widget. (Pro adds choosing the exact paragraph it lands after, and Pro+ adds boxes placed naturally inside the article body.)
Nothing is lost. Anything that depends on a Pro/Pro+ feature (custom styling, pinned posts, etc.) simply stops being applied while locked — the underlying data stays saved, and everything picks back up automatically if you upgrade again.
the_content filter, for coexisting with another plugin that also inserts content into posts this way (e.g. an ad-insertion plugin). Distinct from "Custom ad-hook name," which is for a theme's own dedicated ad-placement hook outside the_content entirely.arp-admin, arp-style, arp-blocks, etc. — 11 handles, 19 registration/reference sites) was still the old short prefix; renamed to ariadne-* for the same WordPress.org naming-uniqueness reason as v1.9.38's function/class/option rename. No visible change — same files, same behavior, just how they're registered internally.arp--prefixed names; now consistent with the rest of the v1.9.38 rename.[arp_related] name — now [ariadne_related], matching what's actually registered.arp--prefixed identifiers from the v1.9.38 rename; now ariadne-dashboard.