Explore how to transform Optimizely’s streaming catalog traversal into a production‑ready scheduled job. This tutorial covers practical patterns for timing, resource throttling, and fault tolerance, enabling large catalog walks to run reliably without blocking API threads.
Part 2 shows how to convert the streaming‑based, memory‑efficient catalog traversal service into a production‑ready scheduled job. It covers practical patterns for timing, resource throttling, and fault tolerance, allowing catalog walks to run without blocking API threads. Optimizely developers can copy these patterns to schedule large catalog traversals reliably in their own Commerce projects.
In this edition, we highlight how Optimizely’s new JsonProperty field type lets you store JSON in a compact binary format, cutting storage overhead and speeding up data retrieval for smoother content authoring and rendering.
Optimizely now supports a more efficient way to store JSON in content properties by using a compact binary format through the JsonProperty field type. This reduces storage overhead and speeds up data retrieval, allowing developers to handle complex data structures more easily. The change is small in code but delivers noticeable performance gains for content authoring and rendering.
New Packages: A2Z.Optimizely.Tiny.AI v1.0.0 lets Optimizely developers add an AI‑powered Assistant button to TinyMCE, enabling editors to rewrite, improve, summarize, expand, or translate content directly within the CMS. Install the NuGet package to streamline content creation and editing workflows with instant AI assistance.
Optimizely developers can now install the A2Z.Optimizely.Tiny.AI v1.0.0 NuGet package to add an OpenAI‑powered AI Assistant button to TinyMCE. The new toolbar button lets editors rewrite, improve, summarize, expand, or translate content directly inside the CMS. This in‑editor AI integration streamlines content creation and editing workflows.
Optimizely’s Package Explorer has been updated to fully support the increasingly complex SaaS CMS exports—including inline (nested) blocks, Visual Builder compositions, and upcoming CMS 13 layout hierarchies—eliminating previous visibility issues. This makes package debugging and migration for SaaS/CMS 13 environments faster and less error‑prone.
Optimizely’s Package Explorer now fully supports the increasingly complex SaaS CMS exports, including inline (nested) blocks in CMS 12, Visual Builder compositions, layout hierarchies, and display templates that will arrive in CMS 13. The update clears up previous visibility issues, letting developers inspect and understand package contents with greater clarity. This makes package debugging and migration for SaaS/CMS 13 environments faster and less error‑prone.
Release Notes: EPiServer.CMS.AspNet v11.21.5 is now available, delivering core ASP.NET assembly updates with several bug fixes and performance enhancements that improve site stability and build efficiency. Optimizely developers are encouraged to upgrade to take advantage of these improvements.
EPiServer.CMS.AspNet v11.21.5 has been released, updating the core ASP.NET assemblies for Optimizely CMS. This update includes a number of bug fixes and performance improvements aimed at enhancing site stability and build efficiency. Optimizely developers are encouraged to upgrade to benefit from the latest enhancements.
The Forum highlights three critical issues: CMS 12’s shortcut navigation strips URL fragments, imported CMS 11 pages fail to invalidate cache upon publishing, and the Projects UI does not list any projects. Each bug requires a temporary workaround—preserving fragments manually, purging caches, or using the API—and close monitoring of the issue tracker for an official fix.
Shortcuts to content in CMS 12 incorrectly strip the URL fragment when navigating, breaking deep‑link functionality. This regression is reported as a bug and may affect any use of anchor links or fragment identifiers. Developers should monitor the issue tracker for a patch or apply a temporary workaround by preserving fragments manually.
Imported CMS 11 pages do not trigger cache invalidation when they are published, causing stale content to be served. Developers may need to manually purge or refresh caches for these pages until a fix is released. Keep an eye on Optimizely updates for a permanent resolution.
Optimizely developers have reported that the Projects UI is failing to list any projects. This issue disrupts project navigation and can hinder workflow. While a fix is pending, consider using the API to retrieve project data until the UI issue is resolved.
Check out the latest release of **CmsContentScaffolding.Optimizely v1.9.2**, which adds a streamlined unit‑testing helper for content scaffolding and includes bug fixes and performance tweaks that make CI‑driven tests for Optimizely CMS projects more reliable and easier to maintain.
v1.9.2 of the **CmsContentScaffolding.Optimizely** NuGet package rolls out a new unit‑testing helper that streamlines content scaffolding and test setup for Optimizely CMS projects. The update also includes bug fixes and performance tweaks to make CI‑driven tests more reliable. This makes it easier for developers to write and maintain robust CMS content tests.