= Changelog archive = This is an archive of older changelog entries. Most recent entries are maintained in readme.txt = 4.4.2 = Release date: 19 September 2026 **Security** * Hardened thumbnail dimension handling to prevent stored cross-site scripting through block attributes. = 4.4.1 = Release date: 5 September 2026 **Added** * Features tab and Feature Manager for disabling unused plugin components without changing existing defaults. * [Pro] Independent controls for the Query Loop, Featured Image, Related Posts Pro, page builder, bot protection, lazy loading, custom tables and WooCommerce modules. **Security** * Hardened settings sanitization for users without the `unfiltered_html` capability. * Hardened Query Loop REST meta filtering and taxonomy searches against unauthorized or private data access. * Password-protected post excerpts were served through the shared HTML cache. **Fixed** * Cache invalidation, dry-run cleanup and persistent object-cache invalidation were incorrect, and ordered IDs and taxonomy slugs could collide. * [Pro] Custom-table indexing did not run after REST metadata and taxonomy updates, and large term refreshes now run in bounded background batches. * [Pro] Query Loop block callbacks accumulated across repeated renders. = 4.4.0 = Release date: 29 August 2026 Release post: https://webberzone.com/contextual-related-posts-v4-4/ **Added** * [Pro] WPBakery, Elementor and Bricks Builder integrations (experimental), with a native "Related Posts (CRP)" element in each builder carrying the full set of CRP options. * [Pro] "Use precomputed taxonomy score" setting, which reads the taxonomy score from the indexed `tax_score` column instead of calculating it per query, at the cost of ignoring per-taxonomy weights in live queries. **Changed** * The site-wide "Exclude terms" setting is now applied to the related posts query; it was previously only honored per post in the metabox. * "Exclude terms" now splits on commas only, so `black friday` is matched as a phrase rather than as two separate words. * The REST API `limit` parameter is now capped at 100. Use `crp_rest_api_max_limit` to change it. * Renamed "Include only posts that contain these words" to "Also match posts that contain these words" to match what the option actually does. **Fixed** * Plugin data was deleted when uninstalling one version while its paired free or Pro counterpart was active. * Schema changes did not reach existing installs; `dbDelta()` now runs on version upgrades instead of on activation only. * The per-request post meta cache was keyed on post ID alone, so the same post ID on two sites of a multisite network shared one cache entry. * HTML entities survived tag stripping, so `&`, ` ` and `…` were indexed as the words "amp", "nbsp" and "hellip". * Stopword stripping failed when the stopword list contained a `/`. * "Exclude terms" ignored the post content when content matching was enabled. * Style stylesheets were always enqueued for the default style instead of the requested one. * Feed thumbnail size settings were ignored; both width and height must now be greater than 0 for a size to be applied. * The contextual match SQL was built twice on every query. * [Pro] The cache collided across differently-configured shortcode, widget, block and builder calls on the same post. * [Pro] "Order by: Date" was overridden by relevance ordering, and an `Unknown column 'score'` error occurred when contextual matching was disabled with Include words set. * [Pro] `orderby="relevance"` used the unweighted core match instead of the Pro weighted score. * [Pro] Taxonomy term-count sorting was applied after the date sort instead of before it. = 4.3.1 = *Release Date - 17 August 2026* * New features: * Search for settings: a search field on the settings page lets you quickly find options by keyword. * Updated plugin icons. * Modifications: * Consolidated FULLTEXT index names across WebberZone plugins with legacy alias support and automatic self-healing of missing indexes on `admin_init`. Also fixes a PHP 8.1 deprecation in the Sync Manager. * Synced Settings API framework from Better Search Pro with `get_locked_settings()`, disabled repeater handling, and flexbox sidebar layout improvements. * Standardized `@since` tags in shared Settings API and Admin Banner files. * Added smooth scroll-to-top on settings tab switch. * Bug fixes: * Fixed `$wpdb->show_errors()` not restoring prior state after `hide_errors()` — re-enabling raw DB-error output for the entire request and corrupting AJAX/JSON responses. * Fixed default-value label lookup for empty-string select/radio options showing "None" instead of the actual option label. * Fixed settings page sidebar overlapping tab content by switching to flexbox layout. * [Pro] Fixed the Index Custom Tables wizard step appearing or disappearing while the wizard was running. * Fixed the settings wizard silently dropping repeater field rows on save. * Improvements: * Setting defaults are now resolved from a single lightweight list instead of building every settings field, so reading an option early in the page load no longer risks loading translations too early. * Added `crp_pre_index_content_parts` filter for recovering shortcode-stripped content before `do_blocks()`/`do_shortcode()` processing discards it. = 4.3.0 = *Release Date - 18 July 2026* Release post: [https://webberzone.com/announcements/contextual-related-posts-v4-3-0/](https://webberzone.com/announcements/contextual-related-posts-v4-3-0/) * New features: * New "Clear cache when a post is trashed or restored" toggle (off by default) under the Performance tab. When enabled, the entire CRP cache is cleared on the `wp_trash_post` and `untrashed_post` transitions, so stale related-posts lists no longer continue to show trashed posts with broken links or missing thumbnails until the cache TTL expires. * [Pro] New "Keyword" setting on the Related Posts block and the CRP Query Loop block: enter a word or phrase to find related posts using that keyword instead of the title and content of the current post, matching the existing metabox behaviour. The advanced algorithm honours the keyword on both the custom tables and native tables paths. * [Pro] Lazy load related posts: a new setting under the Performance tab loads the related posts via JavaScript only when they are about to enter the viewport. This speeds up the initial page load and plays better with page caching plugins. Note: search engines may not index the related posts links when this is enabled, since they are no longer part of the initial HTML. Applies to all display methods — content, shortcode, widget and the Related Posts block — with the configured options preserved via a signed payload. The Query Loop block variation is rendered by WordPress core and is not lazy loaded. Use `lazy_load="0"` in the shortcode (or the `crp_lazy_load` filter) to disable it per instance. Skipped on feeds and AMP pages. * [Pro] Cart Related Products: displays a grid of contextually related products on the WooCommerce cart page when the cart subtotal is below the free shipping threshold. Products are filtered to a configurable price band anchored to the gap-to-free-shipping, and ranked by CRP relevance using the most expensive cart item as the source. Configurable options include product count, price upper-bound percentage, custom heading, and cart page hook position. Coupon discounts are correctly accounted for when calculating the gap. * [Pro] New option to control which post types should show the metabox when editing the post. * Modifications: * Related posts with equal relevance scores are now returned in a stable order: post date and post ID are used as tiebreakers after the relevance score. * New `crp_pre_related_posts` filter to short-circuit the related posts output for all display methods. The lazy load feature uses this; developers can return a non-null value to replace the output entirely. * [Pro] New REST API endpoint `contextual-related-posts/v1/posts//html` that returns the rendered related posts HTML. Display arguments are only honoured when accompanied by a valid signature generated during a server-side render. = 4.2.4 (2026-06-06) = *Release Date - 6 June 2026* * Modifications: * [Pro] Renamed the "Reindex Custom Tables" tool to "Custom Tables" and added a "Recreate Custom Tables" button that drops and recreates the table structure, with success/error feedback displayed in the admin. * [Pro] Added "Convert Custom Table to InnoDB" tool that upgrades the table storage engine and automatically regenerates FULLTEXT indexes. * [Pro] Custom table creation is now skipped entirely when the Efficient Content Storage and Indexing setting is disabled, avoiding unnecessary database queries on every admin page load. * [Pro] Custom table creation is now blocked on MySQL versions below 5.7.8 and MariaDB versions below 10.2.7 (which lack JSON column support), with a clear admin notice instead of a silent failure. * [Pro] Admin notices: FULLTEXT index and missing-table warnings now respect the ECSI setting; removed ECSI upsell and wizard notices; DB errors use the Admin_Notices_API. * Bug fixes: * Fixed broken `aspect-ratio` on the rounded thumbs style caused by CSS variables carrying `px` units. A unitless `--crp-aspect-ratio` variable is now used, consistent with the grid and thumbs-grid styles. = 4.2.3 = * New features: * (Pro) Added ACF field support for thumbnails: specify an Advanced Custom Fields Image or Text field name in the thumbnail settings. Supports all ACF Image field return formats (Image Array, Image ID, Image URL) as well as plain Text fields containing a URL. * Modifications: * [Pro] Scheduled reconciliation cron: a twicedaily background job now automatically syncs any published posts that are missing from the custom search index table — keeps the index complete without manual intervention. * [Pro] Custom table upsert optimized to use `INSERT ... ON DUPLICATE KEY UPDATE`, reducing write contention on high-traffic sites. * [Pro] Database check results are now cached within a request, reducing redundant `SHOW TABLES` queries on pages that check table status multiple times. * [Pro] Tools page migration and undo scripts are now loaded as external JavaScript files (via `wp_enqueue_script`) instead of inline `