| 开发者 | uosamuel |
|---|---|
| 更新时间 | 2026年10月10日 02:30 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPL v2 or later |
| 版权网址: | 版权信息 |
[ariadne_related] shortcode or a widget. Change the heading or count for one spot.ariadne-related-posts folder to /wp-content/plugins/.Category-only plugins treat every post in a category as equally related. Ariadne scores each pair of posts on shared tags, categories, title words and text, so the closest matches come first. You can see the score for each match on the post's edit screen.
Yes. Related lists are stored with each post and read from that store when the page is built. Nothing is calculated during the page load, so it works with full-page caching, object caching and CDNs.
Deactivate the old plugin and activate Ariadne. It builds related lists for your published posts in the background, and the Dashboard shows its progress. If you placed the old plugin's shortcode by hand, replace it with [ariadne_related] or the block.
Not in the free version. Every signal (tags, categories, title overlap, and local BM25 text matching) 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.
ariadne_cron_loopback_args filter.ariadne_related_updated action fires for any other cache.ariadne_color_scheme_meta filter.wp arp instead of wp ariadne.ariadne_related_post_ids filter — apply_filters( 'ariadne_related_post_ids', array $post_ids, int $post_id, int $count ) — lets a theme or another plugin see and adjust the final related-post list before it displays. Also adds a matching ariadne_get_related_post_ids( $post_id, $count = 0 ) function for reading that same (already-filtered) list directly.rel="nofollow" to related-post links, and an option to open them in a new tab. Opening in a new tab always adds rel="noopener" automatically alongside whatever nofollow is set to, regardless of tab setting..prose img { height: auto } — so which one won a property like height: 100% came down to stylesheet load order rather than always favoring this plugin's own styling. A theme rule loading after this plugin's could silently win that tie, most visibly making the Related Posts card image fall back to its default square shape and spill down over the title below it. Every affected selector now includes its real, always-present wrapper element in the selector itself, so this plugin's styling always outranks a same-shape theme rule regardless of load order.update_meta_cache(), which caches every meta key WordPress finds for those posts — including the (often large) stored embedding vector, even for the BM25 pass that never reads it. Both now fetch only the specific meta key each signal actually needs, directly. On a real load test this cut scoring time for a 500-candidate pool from ~1.5s to under 250ms for BM25, and removed multi-second variance from the embeddings pass..arp-info-icon/.arp-info-tooltip CSS rule from the 1.9.49 System Health tooltips was overriding the original definition already used by the Settings page's "Why is this locked?" tooltips — merged back into one shared, corrected rule (outline instead of filled, properly centered glyph) so both places benefit consistently.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.