Blog posts by Robert Svallin2026-01-23T14:21:45.0000000Zhttps://world.optimizely.com/blogs/robert-svallin/Optimizely WorldFrom 12 to 13 preview: A Developer's Guide to testing an Optimizely CMS 13 Alloy Site<p>The release of Optimizely CMS 13 marks a significant step forward, embracing a more composable and headless-first architecture. While this unlocks powerful new capabilities, it also introduces important changes to the underlying framework.</p>
<p>This guide provides a hands-on walkthrough for upgrading a standard CMS 12 Alloy starter site to the CMS 13 preview. We'll cover dependency updates, code migrations for obsolete APIs, and the new application configuration model.</p>
<h2>Step 1: Create a Baseline CMS 12 Site</h2>
<p>First, let's establish a starting point. Create a fresh CMS 12 Alloy site using the Optimizely templates. This ensures we have a clean, working installation before we begin the upgrade.</p>
<pre class="language-csharp"><code># Create a new Alloy project
dotnet new epi-alloy-mvc -n alloy13preview
# Build and run the site
dotnet build
dotnet run</code></pre>
<div class="fabric-editor-breakout-mark fabric-editor-block-mark css-p8f2xz">
<div class="code-block css-ggxefa"> </div>
</div>
<p>Once the site is running, register a new user account so you can log in. Verify that the site is fully functional. When you're ready, shut down the application.</p>
<h2>Step 2: Update Project Dependencies</h2>
<p>With our baseline established, the next step is to update the project file and NuGet packages.</p>
<ol class="ak-ol">
<li>
<p><strong>Update the Target Framework</strong>: Open the .csproj file and change the target framework to</p>
<div class="code-block css-ggxefa">
<pre class="language-html"><code><PropertyGroup>
<TargetFramework>net10.0</TargetFramework>
</PropertyGroup></code></pre>
</div>
</li>
<li>
<p><strong>Update NuGet Packages</strong>: Update all EpiServer.* package versions to 13.0.0-preview2.</p>
</li>
<li>
<p><strong>Add AspNetIdentity</strong>: CMS 13 decouples the UI's identity management. Add a new package reference for EPiServer.CMS.UI.AspNetIdentity. </p>
<div class="code-block css-ggxefa">
<div class="css-9n57oc">
<pre class="language-csharp"><code><PackageReference Include="EPiServer.CMS.UI.AspNetIdentity" Version="13.0.0-preview2" /></code></pre>
</div>
</div>
</li>
</ol>
<h2>Step 3: Code Migration and Mitigating Obsolete APIs</h2>
<p>CMS 13 refactors several core APIs. The compiler will now report a series of warnings and errors related to obsolete members. Let's work through them.</p>
<blockquote>
<p><strong>A Friendly Pro-Tip:</strong> As you begin the migration, make it a habit to check the compiler warnings in your IDE or build output. These warnings are your roadmap to finding every instance of a deprecated or obsolete API in your specific project. While this guide covers the common changes for the Alloy template, your codebase may have other areas needing attention.</p>
</blockquote>
<h3>Use ContentReference and ContentLink</h3>
<p>The PageReference and PageData.PageLink types are now obsolete. This change reflects a broader shift to treat all content more generically. The fix is a straightforward replacement across your solution:</p>
<ul class="ak-ul">
<li>
<p>Replace PageReference with ContentReference.</p>
</li>
<li>
<p>Replace .PageLink with .ContentLink.</p>
</li>
</ul>
<h3>Replace SiteDefinition with the New Application Model</h3>
<p>The concept of SiteDefinition is replaced by a more flexible <strong>Application Model</strong>. An application connects a starting point in the content tree with a specific rendering mode (e.g., "In-Process" or "Headless") and hostnames.</p>
<p>To resolve this, you'll need to inject IApplicationResolver into your controllers and services to get the context of the current application (IApplication).</p>
<p>Here is an example of how to refactor the StartPageController:</p>
<div class="fabric-editor-breakout-mark fabric-editor-block-mark css-p8f2xz">
<div class="code-block css-ggxefa">
<pre class="language-csharp"><code>using alloy13preview.Models.Pages;
using alloy13preview.Models.ViewModels;
using EPiServer.Web;
using EPiServer.Web.Mvc;
using Microsoft.AspNetCore.Mvc;
using EPiServer.Applications;
using EPiServer.Shell.Security;
using EPiServer.Web.Routing;
namespace alloy13preview.Controllers;
public class StartPageController : PageControllerBase<StartPage>
{
private readonly IApplicationResolver _applicationResolver;
public StartPageController(IApplicationResolver applicationResolver)
{
_applicationResolver = applicationResolver;
}
public async Task<IActionResult> Index(StartPage currentPage, CancellationToken cancellationToken)
{
var model = PageViewModel.Create(currentPage);
var application = await _applicationResolver.GetByContextAsync(cancellationToken);
var website = application as Website;
if (website is not null && website.RoutingEntryPoint.CompareToIgnoreWorkID(currentPage.ContentLink))
{
// Connect the view models logotype property to the start page's to make it editable
var editHints = ViewData.GetEditHints<PageViewModel<StartPage>, StartPage>();
editHints.AddConnection(m => m.Layout.Logotype, p => p.SiteLogotype);
editHints.AddConnection(m => m.Layout.ProductPages, p => p.ProductPageLinks);
editHints.AddConnection(m => m.Layout.CompanyInformationPages, p => p.CompanyInformationPageLinks);
editHints.AddConnection(m => m.Layout.NewsPages, p => p.NewsPageLinks);
editHints.AddConnection(m => m.Layout.CustomerZonePages, p => p.CustomerZonePageLinks);
}
return View(model);
}
}
</code></pre>
</div>
</div>
<p>You will need to apply a similar pattern to other places in the code that reference SiteDefinition.Current. For SiteDefinition.Current.RootPage, you can replace it with ContentReference.RootPage.</p>
<h3>Modernize Dependency Injection</h3>
<p>Service location using InitializationEngined.Locate is obsolete. Instead, use constructor injection to get an IServiceProvider instance.</p>
<ul class="ak-ul">
<li>
<p><strong>Before</strong>: context.Locate.Advanced.GetInstance<T>()</p>
</li>
<li>
<p><strong>After</strong>: Inject IServiceProvider and call serviceProvider.GetRequiredService<T>() In an IInitializationModule, you can access it via context.Services.</p>
</li>
</ul>
<h3>Other Small API Changes</h3>
<ul class="ak-ul">
<li>IContentTypeRepository<T>: The generic argument is no longer needed. Change IContentTypeRepository<PageType>() to IContentTypeRepository()</li>
<li>
<p>PageController.PageContext.Page This property is now of type IContent. Update your code to reflect this change.</p>
</li>
</ul>
<h2>Step 4: Configuration Updates</h2>
<p>Next, we need to make a few adjustments in Startup.cs and appSetting.json</p>
<ol class="ak-ol">
<li>
<p><strong>Enable Database Compatibility Update</strong>: In Startup.cs, add the following to allow the database compatibility level to be updated automatically.</p>
<div class="code-block css-ggxefa">
<pre class="language-csharp"><code>services.Configure<DataAccessOptions>(options =>
{
options.UpdateDatabaseCompatibilityLevel = true;
});</code></pre>
</div>
</li>
<li>
<p><strong>Configure Content Graph</strong>: Content Graph is enabled by default in the preview of CMS 13 and cant be disabled. This will likely change in subsequent releases. You must add your credentials to appSettings.json.</p>
<div class="code-block css-ggxefa">
<pre class="language-javascript"><code>"Optimizely": {
"ContentGraph": {
"GatewayAddress": "https://staging.cg.optimizely.com",
"AllowSendingLog": "true",
"SingleKey": "INSERT SINGLEKEY HERE",
"AppKey": "INSERT APPKEY HERE",
"Secret": "INSERT SECRET HERE"
}
}</code></pre>
</div>
</li>
<li>
<p><strong>Install Visitor Groups</strong>: Due to a known issue in the preview, the menu system will not render correctly unless Visitor Groups are installed. Add this to Startup.cs</p>
<div class="code-block css-ggxefa">
<div class="css-9n57oc">
<div class="css-4osl21">
<div>
<pre class="language-csharp"><code>services.AddVisitorGroups();</code></pre>
</div>
</div>
</div>
</div>
</li>
</ol>
<h2>Step 5: Fixing the Post-Upgrade 404</h2>
<p>After making all the changes, run the application:</p>
<div class="fabric-editor-breakout-mark fabric-editor-block-mark css-p8f2xz">
<div class="code-block css-ggxefa">
<pre class="language-csharp"><code>dotnet run</code></pre>
</div>
</div>
<p>You will notice the site returns a <strong>404 Not Found</strong> error. This is expected. The migrated database still has the old SiteDefinition configuration, which doesn't align with the new Application Model.</p>
<p>Follow these steps to fix it:</p>
<ol class="ak-ol">
<li>
<p>Navigate to the CMS admin interface: <code class="_ca0qyh40 _u5f3m5ip _n3tdyh40 _19bvm5ip _2rkofajl _11c819w5 _1reo1wug _18m91wug _1dqoglyw _1e0c1nu9 _bfhk187e _16d9qvcn _syazi7uo _vwz41kw7 _1i4q1hna _o5721jtm">https://localhost:5000/Optimizely/CMS</code>.</p>
</li>
<li>
<p>Go to <strong>Settings</strong> > <strong>Applications</strong>. If the page fails to render, clear your browser cache and reload. You will see a default "Headless" application.</p>
</li>
<li>
<p>Edit the application and click <strong>Delete Application</strong>.</p>
</li>
<li>
<p>Click <strong>Create New Application</strong>.</p>
<ul class="ak-ul">
<li>
<p>Set the <strong>Type</strong> to <strong>In Process</strong>.</p>
</li>
<li>
<p>Select your original Alloy start page as the <strong>Application start page</strong>.</p>
</li>
<li>
<p>Give it a name.</p>
</li>
</ul>
</li>
<li>
<p>Edit the new "In Process" application you just created.</p>
<ul class="ak-ul">
<li>
<p>In the <strong>Hosts</strong> section, add a new host with the name localhost:5000 and set it as the default.</p>
</li>
</ul>
</li>
</ol>
<p>Your Alloy site should now render correctly on the frontend, and preview in Edit mode will be functional.</p>
<h2>Conclusion</h2>
<p>Congratulations! You have successfully upgraded your Alloy site to CMS 13. This process highlights the key architectural shifts in the new version, particularly the move to a composable Application Model and modernized APIs. You are now ready to explore the new features and possibilities of Optimizely CMS 13.</p>
<p><strong>Important Note</strong>: The steps outlined in this guide are intended for developers to explore the CMS 13 preview with the Alloy template. This is an incomplete preview, and these instructions are not recommended for use with an actual development project and certainly not a live production site. We will share more as we get closer to the release date of CMS 13.</p>2026-01-23T14:21:45.0000000ZBlog postCMP DAM asset sync to Optimizely Graph self service<p>The CMP DAM integration in CMS introduced support for querying Optimizly Graph (EPiServer.Cms.WelcomeIntegration.Graph 2.0.0) for metadata such as alternative texts. Up until now interaction with Optimizely has been needed when adding this integration from CMP to Optmizely Graph but that is no longer the case. CMP now contains a self service feature where Optimizely Graph can be added and initial synchronization of assets started. This makes it easier to get started and reap the performance benefits of moving from REST API integration with CMP to the more performant Optimizely Graph integration.</p>
<p>In CMP simply header over to <strong>Settings \ Organization \ Misc</strong>, scroll to the bottom of the view and hit the <strong>Enable & Sync</strong> button that you will find there. Once the sync has completed you will find a URL to the Optimizely Graph UI which contains the <strong>SingleKey</strong> needed to configure CMS.</p>
<p><img src="/link/ff2c84cbf623455ba306902f5ed5b262.aspx?1739443330051" alt="Enabling and syncing DAM assets to Optimizely Graph" width="195" height="94" /></p>
<p>The URL will look something like below.</p>
<p><a title="Optimizely Graph UI with single key" href="https://cg.optimizely.com/app/graphiql?auth=SINGLE_KEY">https://cg.optimizely.com/app/graphiql?auth=SINGLE_KEY</a></p>
<p>If you havent already read about our integration with CMP, either with REST API, or with Optimizely Graph, then please head over to <a href="https://docs.developers.optimizely.com/platform-optimizely/docs/cmp-dam-cms">CMP DAM in CMS</a> to find details on how to get started.</p>2025-02-13T10:48:51.0000000ZBlog postDAM integration new major version, performance improvements and Library Picker folder selection<p>As you might already have seen we have decided to delist the EPiServer.CMS.WelcomeIntegration version 1.4.0 where we introduced Graph support. Unfortunately a return type was changed that we didn’t catch which means that it became a breaking change. We have decided to delist 1.4.0 and release the performance improvements we have been working on as a new major. We apologize for any inconvenience this has caused and suggest that you either downgrade to 1.3.9 and rely on the CMP API instead of Graph, or upgrade to 2.0.0 instead. We recommend to upgrade to 2.0.0 for the best performance.</p>
<h2><strong>Performance</strong></h2>
<p>The integration between CMS and CMP uses a combination of the CMP Library Picker, in which the editor selects the asset to reference and, either the CMP´s REST API, or indexed assets in Graph. The API or Graph is used to pull metadata regarding the assets such as sizing or alt texts. The integration with REST API has been around for quite some time and the Graph integration was released in the previous version, 1.4.0, and we described how to configure it in <a href="/link/652f47770cce478882e5e0481d69b6c8.aspx">this blog post by Bartosz Sekula</a>.</p>
<p>We are now releasing a change in how metadata is cached in the CMS for assets referenced from CMP DAM. Moving forward from version 2.0.0 the cache will move to the database and stored permanently. This removes the need for any page request that contain CMP DAM assets to perform outbound network requests to retrieve that metadata when cache has expired.</p>
<p>The metadata will be fetched for Image assets from CMP when a content that contains references to those images is <strong>published</strong>. So metadata will be available once the page starts to receive traffic. Please note that fetching the metadata is handled in the background to not block the editor from interacting with the UI. If the images are already referenced by other pages or block then the already existing metadata will be used.</p>
<p>Should for some reason the metadata not have been populated then the image will still render but with the public URL which was stored the first time the asset was referenced, instead of the latest URL provided by CMP through the metadata.</p>
<p><strong>Renditions</strong> of <strong>Images</strong> is a bit different and a topic to which we will return. Currently the renditions for an image asset will render without alt-text. As already stated, we are working on resolving that. The HtmlHelper and TagHelper as well as DamImageAssetViewComponent will still render the correct rendition.</p>
<p>Example of using HtmlHelper</p>
<pre class="language-markup"><code>@model PageViewModel<StandardPage>
@using EPiServer.Cms.WelcomeIntegration.UI.Helpers
@await Html.RenderTagWithMetadata(p => p.CurrentPage.Image)</code></pre>
<p>Example of using TagHelper</p>
<pre class="language-markup"><code>@model PageViewModel<StandardPage>
@addTagHelper *, Microsoft.AspNetCore.Mvc.TagHelpers
<dam-asset content-reference="@Model.CurrentPage.Image" /></code></pre>
<h3>Maintaining asset metadata</h3>
<p>Since the metadata for Images now have moved to the database, how does it get updated? A new scheduled job has been created which will, on schedule, pull metadata from CMP DAM for all assets and update in CMS. This job can be executed manually should the need arise to sync metadata between CMP and CMS.</p>
<p><img src="/link/7771fed1d3e54efbb6c8f8b4142cecc8.aspx?1732854990499" alt="The scheduled job for maintaining CMP DAM asset metadata in CMS" width="834" height="471" /></p>
<p>Metrics from testing scenarios indicate big performance improvements when serving content with DAM assets to visitors.</p>
<h2><strong>Asset Library folder selection</strong></h2>
<p>CMP has the possibility to organize content in folder structures and it is now possible configure either globally or by type which folder to open in the <strong>CMP Library Picker</strong>. Configuration is done at startup or appSettings as usual.</p>
<pre class="language-csharp"><code>.AddDAMUi(o => {
o.Enabled = true;
o.GlobalRootFolderGuid = "a7fd6357c13d49829715f38fe8114c40";
o.RootFolderForTypes = new Dictionary<string, IEnumerable<Type>>
{
{ "57523add60d04e328d7fc1e02c05ed40", new Type[] { typeof(DAMImageAsset) } },
{ "7bce1de28e66411590ac32896eff2ce1", new Type[] { typeof(DAMVideoAsset) } },
{ "72b89ab1b83041acaab861a035db7e7b", new Type[] { typeof(DAMAsset) } }
};
});</code></pre>2024-11-29T04:37:35.0000000ZBlog postEPiServer.CMS UI 12.17.0 delisted from Nuget feed<p style="margin: 0in; font-family: Calibri; font-size: 11.0pt;" lang="sv">The 12.17.0 version of the UI packages have been delisted from our Nuget feed and is no longer available. We are working on providing a patch, 12.17.1 to correct an issue that affects string properties that use <span class="classLib">SelectMany</span> attribute and a <span class="classLib">ISelectionFactory</span> to handle the available options.</p>
<p style="margin: 0in; font-family: Calibri; font-size: 11.0pt;" lang="sv"> </p>
<p style="margin: 0in; font-family: Calibri; font-size: 11.0pt;" lang="sv">The root issue is that the representation of the selected values is now stored in a different way in the database and that needs to be considered a breaking change. We moved from a comma separated list in favor of a Json array. I.e. from "value1,value2,value3" to "[\"value1\",\"value2\",\"value3\"] in an effort to try and broaden the capabilities. The change only applies to properties that have been updated and saved to the database since the 12.17.0 upgrade was done on the installation.</p>
<p style="margin: 0in; font-family: Calibri; font-size: 11.0pt;" lang="sv"> </p>
<p style="margin: 0in; font-family: Calibri; font-size: 11.0pt;" lang="sv">An installation can be checked if it has been affected by the issue, by running a query against the database to see if the properties store a JSON array or comma separated strings. Please note that only installations using 12.17.0 and that uses properties that are using SelectMany attribute is potentially affected.</p>
<p style="margin: 0in; font-family: Calibri; font-size: 11.0pt;" lang="sv">An example would be that 12.17.0 would store</p>
<p style="margin: 0in; font-family: Calibri; font-size: 11pt; padding-left: 40px;" lang="sv"><span class="classLib">["1","2","3"]</span></p>
<p style="margin: 0in; font-family: Calibri; font-size: 11.0pt;" lang="sv"> </p>
<p style="margin: 0in; font-family: Calibri; font-size: 11.0pt;" lang="sv">Instead of the previously used</p>
<p style="margin: 0in; font-family: Calibri; font-size: 11pt; padding-left: 40px;" lang="sv"><span class="classLib">1,2,3</span></p>
<p style="margin: 0in; font-family: Calibri; font-size: 11.0pt;" lang="sv"> </p>
<ul>
<li style="font-family: Calibri; font-size: 11pt;" lang="sv"><a href="/epiui/CMS/Content/support/Bug-list,,149001/bug/CMS-26903?epieditmode=False&epsremainingpath=bug/CMS-26903" title="CMS-26903">CMS-26903</a><br />When addressing the issue <a href="/epiui/CMS/Content/support/Bug-list,,149001/bug/CMS-23405?epieditmode=False&epsremainingpath=bug/CMS-23405" title="CMS-23405">CMS-23405</a> <span lang="sv" style="font-family: Calibri; font-size: 11.0pt;">a breaking change was introduced in how the values for string properties using </span><span lang="en-SE" style="font-weight: bold; font-family: -apple-system; font-size: 10.5pt; color: #272b32; background: white;">SelectManyAttribute</span><span lang="sv" style="font-family: Calibri; font-size: 11.0pt;"> and </span><span lang="en-SE" style="font-weight: bold; font-family: -apple-system; font-size: 10.5pt; color: #272b32; background: white;">ISelectionFactory</span><span lang="sv" style="font-family: Calibri; font-size: 11.0pt;"> are stored in the database. A change was made to serialize the selected options as JSON instead of comma separated strings.</span></li>
</ul>
<p style="margin: 0in; font-family: Calibri; font-size: 11.0pt;" lang="sv">We offer our apologies that this occured and we are sorry that this has affected our customers. For installations that are in the process of migrating to 12.17.0 we ask that you verify if you are affected. Wait for the 12.17.1 version that will arrive shortly and then verify that data is stored correctly.</p>
<p style="margin: 0in; font-family: Calibri; font-size: 11.0pt;" lang="sv">This blog post will be updated as we move forward with this issue. Thank you for your patience.</p>2023-03-01T05:30:45.0000000ZBlog postImproving And Unifying The UI<p><span>We aim to unify and make a seamless user experience across all Optimizely products. This change will make our products more predictable, easy to use, and accessible. T</span>herefor the CMS in Content Cloud has, over the last few versions (starting with 12.3.0), received multiple updates to the UI. This work is still ongoing, and in the coming weeks/months we expect to release even more updates. However, we wanted to pause and talk a bit about what we have done recently.</p>
<p>Let’s start with a direct comparison of how the UI has changed during this period. The screenshots below clearly outline the differences.</p>
<p><img src="/link/e22dea18564b4579a02de912701e2f89.aspx" width="2844" alt="A comparison of form edit between 12.7.0 (left) and 12.2.0 (right)." style="border-style: solid;" /></p>
<p><span style="font-family: helvetica, arial, sans-serif;"><em>Image: A comparison of form edit between 12.7.0 (left) and 12.2.0 (right).</em></span></p>
<p>The UI now uses icons from Font Awesome Pro 6, which is a font-based icon library which in turn means that there are fewer resources to download and the icons scale better since they are vector-based. Icons are no longer solid instead, they are outlined, more sharp, crisp, and modern looking. All products from Optimizely use the same set of icons.</p>
<p>The new icons use the same CSS classes as the old ones did, so for example the home icon still uses the .epi-iconObjectStart CSS class. However, the new icons use a licensed version of Font Awesome 6 Pro, and this limits how the icons can be used. Third-party add-ons and extensions need to use either a free version of Font Awesome 6/equivalent or purchase their license. The new icons have the following sizes, small (16 x 20), medium (24 x 30), and large (32 x 40). </p>
<p>Spacing has also been reworked to introduce more padding to create an improved visual clarity, balancing the layout and making it easier to overview. By introducing more white space into the layout important elements draw the user’s attention, allowing the user to focus on call-to-action items and making everything easier to read. In general, alignment has been given an overhaul as well.</p>
<p>Primary buttons have moved to the right-most side in a button group and the secondary button no longer has a border unless it receives focus or the user hovers on it. This further makes the primary button easier for the eye to catch.</p>
<p><img src="/link/6f5baee0cc0c464799cea3b323ff351f.aspx" width="800" alt="Button placement and disabled state in 12.7.0 (left) and 12.2.0 (right)" height="808" style="border-style: solid;" /></p>
<p><span style="font-family: helvetica, arial, sans-serif;"><em>Image: Button placement and disabled state in 12.7.0 (left) and 12.2.0 (right)</em></span></p>
<p><span>Disabled buttons are not transparent anymore. Instead, they have a specific look to them to make sure that they stand out as inactive. For example, a disabled primary button was previously a muted blue that became brighter when enabled. Now the disabled version is instead grey and becomes blue once enabled.</span></p>
<p>Content Selectors have been reworked to support the user in selecting content without using drag and drop. This was made possible by allowing all content selectors to have a drop-down menu that allows the user to select as well as create content. Drag-n-drop is still present in the UI and the borders of drop zones have been adjusted so that they are coherent and visible.</p>
<p><img src="/link/b7383116577b428e9e0db0cded611f6c.aspx" width="1024" alt="Creating and selecting content in 12.7.0 (left) and 12.2.0 (right)" height="254" style="border-style: solid;" /></p>
<p><span style="font-family: helvetica, arial, sans-serif;"><em>Image: Creating and selecting content in 12.7.0 (left) and 12.2.0 (right).</em></span></p>
<h2><span style="font-family: helvetica, arial, sans-serif;">Multi-targeting .NET 6 and .NET 5</span></h2>
<p>As of EPiServer.CMS.UI 12.4.0 our nugets multi-target both .NET 6.0 and .NET 5.0. EPiServer.CMS.TinyMCE 3.2.0 also supports both as well as EPiServer.Telemetry.UI 2.1.0.</p>
<p>This was a small selection of the many updates that have been made in the UI and as you upgrade you will discover many more. In the coming versions the team will work on more updates, and we are looking forward to your feedback.</p>
<h2><b>New support for tiff files</b></h2>
<p>The CMS UI supports tiff files and adds Tiff to <span class="classLib">SupportedEditExtensions</span> list. Currently, tiff is quite an old image extension and It is supported by a few browsers (for example, safari, IE11).</p>
<h3>What is in the box?</h3>
<ul>
<li>On Chrome/other browsers users can:
<ul>
<li>Upload a .tiff image</li>
<li>Open in Image Editor to edit a .tiff image</li>
</ul>
</li>
<li>On Safari/IE11 browser users can:
<ul>
<li>Upload a .tiff image</li>
<li>DnD a .tiff image into Image property (content reference/content reference list/link item collection/URL to (doc,image, page), XhtmlString, Content Area)</li>
<li>Open a .tiff image on OPE or All properties mode</li>
<li>Open in Image Editor to edit a .tiff image</li>
<li>View a .tiff image on View mode</li>
</ul>
</li>
</ul>
<h3>Known issues</h3>
<ul>
<li>Thumbnails in Media gadget have a hard-coded content-type (image/png) in CMS Core, and they are not going to change it. That explains why tiff or ico files don't show thumbnails.</li>
<li>We only support *.tiff extension. *.tif is not supported</li>
</ul>2022-06-16T14:17:55.0000000ZBlog post