Fixing TinyMCE Initialization Failures in Optimizely CMS: A Hidden Pipeline Issue with .NET SDK Versions

Over the past few weeks, several Optimizely CMS projects began experiencing a puzzling failure: XHtmlString fields stopped initializing TinyMCE in the edit interface. The editor simply refused to load, leaving users unable to manage rich text content. This issue surfaced in multiple unrelated projects, so it was clear the root cause wasn’t project-specific code. After …

Continue reading Fixing TinyMCE Initialization Failures in Optimizely CMS: A Hidden Pipeline Issue with .NET SDK Versions

Building a Custom Payment in Optimizely Commerce 14 (with a simple “Account” method)

This post outlines a simplified method for integrating Account payments into Commerce 14, detailing a minimal working path without extensive exploration. It covers creating a Payment Option and Payment Gateway, registering them in the Admin UI, and optionally persisting Account numbers in a custom database table.

How to Use IPlacedPriceProcessor in Optimizely Commerce to Preserve Custom Line Item Prices (Donation Example)

Optimizely Commerce 12+ automatically validates line item prices based on catalog data, which can overwrite user-entered prices for donations or custom amounts. To avoid this, you can extend the IPlacedPriceProcessor to preserve user-defined prices by using a custom flag. This method maintains the pricing system's integrity while accommodating unique business models.

Getting Started with Optimizely SaaS Core and Next.js Integration: Deploying to Vercel

This article illustrates the benefits of Vercel as a quick and convenient platform for deploying Next.js applications. It guides through the process of creating a Vercel account, connecting to GitHub, importing a repository, and configuring it for deployment. On successful deployment, Vercel assigns a public domain name, automatically updated with any changes pushed to GitHub.

Getting Started with Optimizely SaaS Core and Next.js Integration: Testing Content Updates

The blog post discusses the challenges of content updates on a website using Optimizely CMS, Next.js, and the Apollo Client due to Apollo's local caching feature. The local caching enhances application speed but fails to reflect real-time updates. A temporary solution used is the revalidate parameter set to revalidate the cache every 5 seconds, ensuring content updates are reflected. However, this is not ideal for long-term use, and more targeted cache updates are preferable in a production environment.

Organize page content into folders dynamically

Why do we need organized content into folders or containers? As your content tree grows, it gets more difficult to locate items and performance can decrease.All the items inside the folder or container are automatically organized in a logical format. When to use dynamic folders? When you need to manage large number of items in …

Continue reading Organize page content into folders dynamically