<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom"><title type="text">Blog posts by Tomas Hensrud Gulla</title><link href="http://world.optimizely.com" /><updated>2026-04-27T14:52:29.0000000Z</updated><id>https://world.optimizely.com/blogs/tomas-hensrud-gulla/</id> <generator uri="http://world.optimizely.com" version="2.0">Optimizely World</generator> <entry><title>Optimizely CMS 13 breaking changes: GetContentTypePropertyDisplayName</title><link href="https://www.gulla.net/en/blog/optimizely-cms-13-breaking-changes-getcontenttypepropertydisplayname/" /><id>When upgrading from CMS 12 to 13, resolving property display names may not work as before. Here’s what changed.</id><updated>2026-04-27T14:52:29.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Optimizely CMS 13 breaking changes: IValidate&lt;T&gt;</title><link href="https://www.gulla.net/en/blog/optimizely-cms-13-breaking-changes-ivalidate/" /><id>Custom IValidate&lt;t&gt; validators in Optimizely CMS 13 are no longer auto-discovered. They must be registered explicitly when upgrading from CMS 12.&lt;/t&gt;</id><updated>2026-04-27T14:30:57.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Convert Blocks in Optimizely CMS: Now Supporting CMS 12 and CMS 13</title><link href="https://www.gulla.net/en/blog/convert-blocks-in-optimizely-cms-now-supporting-cms-12-and-cms-13/" /><id></id><updated>2026-04-24T13:31:11.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Optimizely CMS 13 and PageReference is obsolete</title><link href="https://www.gulla.net/en/blog/optimizely-cms-13-and-pagereference-is-obsolete/" /><id>Learn what to to with the warning: &#39;PageReference&#39; is obsolete: &#39;Use ContentReference instead.&#39;</id><updated>2026-04-13T17:35:08.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Optimizely CMS 13 and the Alloy demo site</title><link href="https://www.gulla.net/en/blog/optimizely-cms-13-and-the-alloy-demo-site/" /><id>The Alloy demo site now runs on Optimizely CMS 13. Here’s a quick guide to getting it up and running locally.</id><updated>2026-04-10T15:31:13.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Optimizely CMS 13 and the first bug fixes</title><link href="https://www.gulla.net/en/blog/optimizely-cms-13-and-the-first-bug-fixes/" /><id>The first bug fixes for Optimizely CMS 13 is here!</id><updated>2026-04-09T19:49:54.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Optimizely CMS 13 and errors when creating pages after upgrade</title><link href="https://www.gulla.net/en/blog/optimizely-cms-13-and-errors-when-creating-pages-after-upgrade/" /><id>After upgrading to Optimizely CMS 13, I ran into issues creating pages and deleting media. The fix was easy!</id><updated>2026-04-09T07:53:10.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Optimizely CMS 13 and the new login/admin/edit URL</title><link href="https://www.gulla.net/en/blog/optimizely-cms-13-and-the-new-login-admin-edit-url/" /><id>What happened to /episerver/cms after upgrading to Optimizely CMS 13?</id><updated>2026-04-08T11:01:41.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>How to Disable automatic indexing in Optimizely Search &amp; Navigation</title><link href="https://www.gulla.net/en/blog/how-to-disable-automatic-indexing-in-optimizely-search-and-navigation/" /><id>Learn how automatic event-based indexing works in Optimizely Search &amp; Navigation and how you can temporarily disable it.</id><updated>2026-04-01T07:11:38.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Disabling the scheduler also stops event-based indexing in Optimizely</title><link href="https://www.gulla.net/en/blog/disabling-the-scheduler-also-stops-event-based-indexing-in-optimizely/" /><id>If you disable the scheduler in Optimizely CMS, should event-based indexing stop working too? It does!</id><updated>2026-03-13T20:21:25.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Running Optimizely CMS 12 on .NET 10 in Azure</title><link href="https://www.gulla.net/en/blog/running-optimizely-cms-12-on-net-10-in-azure/" /><id>Upgrade your Optimizely CMS website to .NET 10!</id><updated>2025-11-21T07:53:51.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Optimizely CMS Roadmap – AI, automation and the future of digital experiences</title><link href="https://www.gulla.net/en/blog/optimizely-cms-roadmap/" /><id>A summary of the roadmap for Optimizely CMS from the Opticon conference on September 30, 2025.</id><updated>2025-10-06T04:00:00.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Get last edited content from Optimizely CMS</title><link href="https://www.gulla.net/en/blog/get-last-edited-content-from-optimizely-cms/" /><id>Learn how to query the last updated blocks and pages from Optimizely CMS</id><updated>2025-10-04T05:03:00.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Get last run of a scheduled job in Optimizely CMS</title><link href="https://www.gulla.net/en/blog/get-last-run-of-a-scheduled-job-in-optimizely-cms/" /><id>Learn how to get the last execution time of a scheduled job in Optimizely CMS.</id><updated>2025-09-20T05:45:02.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Optimizely CMS and HTML validation message: Trailing slash on void elements has no effect and interacts badly with unquoted attribute values.</title><link href="https://www.gulla.net/en/blog/optimizely-cms-and-html-validation-message-trailing-slash-on-void-elements-has-no-effect-and-interacts-badly-with-unquoted-attribute-values/" /><id>When using the W3C Markup Validation Service, some annoying information messages pop up because Optimizely CMS adds the trailing slash to self-closing tags.&#160;Let&#39;s fix that!</id><updated>2025-09-14T16:55:24.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>SQL addon for Optimizely CMS 12 updated with new features</title><link href="https://www.gulla.net/en/blog/sql-addon-for-optimizely-cms-12-updated-with-new-features/" /><id>First released in 2021, the SQL Studio addon for Optimizely CMS lets you query your database directly from the edit UI. The latest update adds support for GPT-5, a new UI for managing saved queries, and an audit log</id><updated>2025-08-29T21:08:35.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>The remote server returned an error: (400) Bad Request – when configuring Azure Storage for an older Optimizely CMS site</title><link href="https://www.gulla.net/en/blog/the-remote-server-returned-an-error-400-bad-request-when-configuring-azure-storage-for-an-older-optimizely-cms-site/" /><id>How to fix a strange issue that occurred when I moved editor-uploaded files for some old Optimizely CMS 11 solutions to Azure Storage.</id><updated>2025-06-26T09:21:15.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Enable Opal AI for your Optimizely products</title><link href="https://www.gulla.net/en/blog/enable-opal-ai-for-your-optimizely-products/" /><id>Learn how to enable Opal AI, and meet your infinite workforce.</id><updated>2025-06-25T13:53:29.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Exporting Optimizely databases causing errors</title><link href="https://www.gulla.net/en/blog/exporting-optimizely-databases-causing-errors/" /><id>Solutions to a couple of recurring issues when migrating databases to the cloud.</id><updated>2025-06-18T14:40:33.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Opal AI available in Optimizely CMS (SaaS)</title><link href="https://www.gulla.net/en/blog/opal-ai-available-in-optimizely-saas-cms/" /><id>Use Opal AI to translate your content!</id><updated>2025-05-12T12:08:50.0000000Z</updated><summary type="html">Blog post</summary></entry></feed>