WordPress Integration changelog
All notable changes to OCMLabs WordPress Integration are listed here. This module follows Semantic Versioning.
2.1.0
Features
- Blog Home Page Content setting (Blog Settings). The blog home can show your WordPress front page, the one set in WordPress under Settings > Reading, on its own or above the recent posts. The default is still the recent posts list. See Blog Settings.
- Sidebar Menu setting (Menus). Pick a menu from WordPress Appearance > Menus to show at the top of the blog sidebar. Links to posts, categories and tags point at the Magento blog. See Menus.
- Page Layout settings. Put the blog sidebar on the left or right, or use 1 column, with separate settings for listing pages and single posts. The default is still the left sidebar. See Page Layout.
Fixes
- Enable WordPress Menus now has an effect. Before, the setting turned menus on but no layout placed a menu and there was no way to choose one, so nothing rendered.
- Loading the list of WordPress menus no longer fails. The module did not read the menu list the plugin returns, and failed on menus assigned to a theme location.
- Upgrading from 1.x (
OrangeCollar_WordPressIntegration) no longer failsbin/magento setup:upgradewith a “Duplicate entry” error. The upgrade step that moves saved settings to the new names now works whatever is already in the database. Where a setting exists under both the old and new name, the new one is kept.
No WordPress plugin update is needed. Update ocmlabs/module-wordpress-hyva to 2.1.0 as well, which requires ocmlabs/module-wordpress 2.1. Run bin/magento setup:upgrade and bin/magento setup:di:compile after updating, then flush the cache. The new settings default to the 2.0.5 behavior, so nothing changes on the storefront until you change them.
2.0.5
Fixes
- Blog pages show the store’s top navigation menu (the category menu) when Varnish is the full page cache. Before, the blog home, post, category, tag and author pages rendered without it, on both Luma and Hyva. Magento renders the top menu on cached pages through an ESI include, and that include was rejected because the blog router did not set a route name. Blog search results were not affected because that page is not cached.
- On installs with more than one store view, blog pages on a non-default store view now keep that store. Before, blog pages did not set Magento’s store and currency context, so with Varnish a visitor on a second store view could be served the default store’s cached pages (the wrong store and theme) after opening a blog page. Blog pages on every store view are now cached per store, like the rest of the storefront.
No WordPress plugin update is needed. Update ocmlabs/module-wordpress-hyva to 2.0.5 as well. Run bin/magento setup:upgrade and bin/magento setup:di:compile after updating, because the blog controllers’ constructors changed. If you have plugins or preferences on the blog controllers, check them against the new Context constructor argument.
2.0.4
Fixes
- Blog post pages have a single H1. The post title was rendered twice, once by Magento’s page title block and once by the post template. The post template’s heading is now the only one, on both Luma and Hyva. Blog listing, category, tag, author and search pages were not affected.
- The
<title>tag, meta description and Open Graph and Twitter Card tags are unchanged: the Yoast or RankMath SEO title still drives<title>, and the on-page heading is still the post title.
No WordPress plugin update is needed. Update ocmlabs/module-wordpress-hyva to 2.0.4 as well. If your theme customizes ocmlabs_post_view.xml or post/view.phtml, check that post pages still render one H1.
2.0.3
Fixes
- Editing a post in WordPress now shows on the storefront on the next page load. The cache purge webhook clears the full page cache (built-in or Varnish) as well as the module’s data cache. Previously, cached blog pages kept the old content for up to 24 hours.
- Blog pages, the blog sidebar, the Recent Posts, Featured Post and Category Posts widgets and the WordPress menu now carry WordPress cache tags, so a purge clears only the pages that show the changed content. See Cache Tags.
No WordPress plugin update is needed. Update ocmlabs/module-wordpress-hyva to 2.0.3 as well.
2.0.2
Fixes
- Related Posts now show the related posts with their titles, links, images and dates. Previously they showed a single empty card.
- Yoast and RankMath SEO data now reaches the page: the
<title>, meta description, robots, Open Graph and Twitter Card tags. The Open Graph URL is the storefront post URL. The on-page heading stays the post title. - Post pages output Article structured data (JSON-LD).
- The share buttons on post pages include Email.
No WordPress plugin update is needed. Update ocmlabs/module-wordpress-hyva to 2.0.2 as well.
2.0.1
Fixes
- Paginated blog listings (blog home, category, tag and author pages) no longer return a 500 error when there are more posts than Posts Per Page.
- Blog pages on Luma-based themes no longer return a 500 error. Blog styles are now compiled into the theme’s
styles-m.cssby the standard Luma LESS build. - On installs that mix Hyva and Luma store views, Luma store views now render the Luma blog templates instead of the Hyva ones. Update
ocmlabs/module-wordpress-hyvato 2.0.1 as well. - Test Connection now tests the WordPress URL and API key currently in the form, so you can check them before saving. It reports a rejected API key separately from an unreachable URL.
2.0.0
Breaking
- PHP namespace and module renamed from
OrangeCollartoOCMLabs(OCMLabs_WordPressIntegration). Layout handles are nowocmlabs_*, config pathsocmlabs_wordpress/*, and the log filevar/log/ocmlabs_wordpress.log. Saved settings migrate automatically onsetup:upgrade. See Upgrading from 1.x. - The Hyva companion package
ocmlabs/module-wordpress-hyva2.0.0 requiresocmlabs/module-wordpress2.x.
Compatibility
- Magento Open Source and Adobe Commerce 2.4.9 support (framework
103.0.9). - Verified on PHP 8.4.
Security
- Post content and Featured Post excerpts are now sanitized with an HTMLPurifier allowlist instead of a pattern denylist.
- Requests to WordPress no longer follow redirects, and the admin connection test no longer shows raw error messages.
- New optional Webhook Secret setting, so cache purge webhooks can be signed with a dedicated secret instead of the API key.
- JSON-LD output hex-encodes HTML-significant characters, and blog URL slugs are validated before any API call.
Fixes
- A missing post, category, tag or author page now returns a 404. Previously it returned a 500 after repeated WordPress API calls.
- Featured images now render on post listings and post pages.
- Category, tag and author archive pages are purged by the matching webhooks.
- The WordPress API client is no longer built on every storefront page, and the HTTPS warning is no longer logged when no WordPress URL is configured.
1.0.0
- Initial release.