IM-Press Release Notes

IM-Press 5.2.3 is a stability and WordPress 7 compatibility release. It includes all improvements from 5.2.0 through 5.2.3 and was validated through staged, rollback-protected deployments before broader availability.

5.2.3 — WordPress block-binding compatibility

• Registers the native Block Bindings source using only properties supported by WordPress 6.5 and newer.
• Removes invalid-property registration notices on WordPress 7.
• Supports native WP_Block objects while preserving legacy array callers.
• Forwards post ID and post type context through binding callbacks.

5.2.2 — Related Articles recursion fix

• Prevents Related Articles from recursively re-entering the_content when a related post has no manual excerpt.
• Builds display-only excerpts from the stored excerpt or raw content without changing the post.
• Strips shortcodes and HTML, limits the result to 20 words, and escapes output safely.

5.2.1 — Sitemap, schema, health, and agent guidance

• Makes the sitemap rebuild endpoint flush the actual sitemap transients and report failures truthfully.
• Uses the static front page’s real modification time for sitemap lastmod.
• Adds an explicit, target-authorized schema DELETE operation with verified clearing.
• Adds bounded and paginable page-health scanning.
• Updates the agent-facing SEO/AIO contract with evidence-first guidance, public-output verification, crawler distinctions, and review-first handling of optional llms.txt.

5.2.0 — AI-adoption and live-render hardening

Version 5.2.0 introduced the larger AI-adoption hardening batch, including safer authenticated rendering without WooCommerce, corrected attribute-only blocks, promoted-import CSS and SVG preservation, working per-page noindex output, asset preflight improvements, secure custom-schema rendering and clearing, sitemap homepage deduplication, a page-level wpautop bypass, content sanitization tools, import sessions, package validation, and expanded regression and block-stress coverage.

Compatibility

• WordPress 5.9 or newer
• PHP 7.4 or newer
• Tested through WordPress 7.0

Existing WordPress content is not rewritten during a normal plugin update. As with any production plugin deployment, take a rollback backup first and verify important public pages, schema, sitemaps, logs, and editor behavior after updating.