Sitecore Tickets opened in 2025!

This post documents various Sitecore tickets and issues encountered in 2025, including their descriptions, Sitecore's responses, and any available workarounds or solutions. I'm very grateful to Sitecore support for their hard work, responsiveness, and dedication in investigating and resolving these issues. Their thorough analysis and timely responses have been invaluable in helping us navigate these challenges and improve our Sitecore implementations.

Legend: 🐛 = Bug | 💡 = Feature Request | ℹ️ = Observation/Tip | ✅ = Fixed | ❌ = Not Fixed

🐛 ✅ Unable to select SXA Page Branch in Page Branches rules section

Description

We are currently reviewing SXA Page Branches on XM Cloud and have created two page branches. However, when we try to add a rule in the Actions section — specifically the action "Add the specified Page Branch to the insert options" — clicking the "specified" link does nothing. It's expected to open a dialog for selecting a page branch, but there is no response.

This issue is reproducible in our Development environment, and I have also tested it using a Docker image, where the same behavior occurs.

Sitecore Confirmation

Sitecore confirmed this is a bug. I was able to reproduce the behavior you reported in a clean XM Cloud environment. Based on my investigation, the issue appears to be related to a known bug with the reference number SXA-8301 and as of today November 2025 is now fixed.

Workaround

As a workaround, please save the value as it is and then modify the raw value. You can enable raw values via the "View" tab. The value will appear similar to this:

<ruleset>
  <rule uid="{5DF2AE65-D56E-4586-AB65-6C9A27311789}">
    <actions>
      <action id="{D46EC8E5-7B46-47DE-B44A-4C5C30EF48D1}" uid="5066CCCE55BE413AA6DA819CCDF23947" />
    </actions>
  </rule>
</ruleset>

To include the "specified" page branch, manually update it as follows:

<ruleset>
  <rule uid="{5DF2AE65-D56E-4586-AB65-6C9A27311789}">
    <actions>
      <action id="{D46EC8E5-7B46-47DE-B44A-4C5C30EF48D1}" uid="5066CCCE55BE413AA6DA819CCDF23947" PageBranchId="{79B7AF15-E19F-4AD4-B797-FB8650E3D175}" />
    </actions>
  </rule>
</ruleset>

After making this change, you can disable raw values to verify that the rule was applied correctly.

🐛 ✅ Sitecore Search Facet localization shows empty list

Opened: July 7, 2025

Description

In our non-production Sitecore Search environment, we are working on implementing localization for facet labels. However, under Administration > Domain Settings > Facets > Localization, the screen is blank — no facets are listed. Additionally, the Import and Export buttons do not appear to function.

According to the official documentation (https://doc.sitecore.com/search/en/users/search-user-guide/add-localized-values-for-feature-options.html), facet keys should appear automatically after indexing. Our content is indexed, and facets like Content_Type, Markets, etc., are present in the data.

Please advise if this is a configuration issue or if something needs to be enabled for localization to function correctly in this environment.

Sitecore Response

Unfortunately, the facet localization feature is not currently functioning as expected, which is why you are seeing an empty list and non-responsive Import/Export buttons.

However, we can assist you in setting this up manually. To proceed, could you please provide the following:

Domain ID of the environment you are working in
A list of facet attributes that you would like to enable for localization

Once we have this information, we will help configure the localization settings accordingly.

To track the future status of this bug report, please use reference number SEARCH-4712.

Status: As of November 2025, this bug has been fixed.

💡 ❌ SitecoreAI Page builder Thumbnails are not showing when using Page Branches to add a page

Description

We created page branches in our shared site, with idea to use them on all sites after that. We added icons and thumbnails for each page branch. In Page Builder, when we start the process of creating page it shows dialog with insert options configured but only templates ( when we map template to design mapping) are showing thumbnail from Page Design. This seems not working for Page Branches. Can you let me know how we can configure images to be displayed on this screen?

Sitecore Response

Currently, custom thumbnails are only supported for Page Designs. You can set a thumbnail, and when a Page Design is associated with a Page Template, it will be displayed. However, you are using Page Branches, which do not support custom thumbnails at this time.

Given this limitation, I have submitted a new feature request. This enhancement may be considered for future versions. To track the status of this request, please refer to reference number CFW-4747.

Status: As of November 2025, this feature has not been fixed yet.

🐛 ✅ Page Title Character Limit in XM Cloud Pages Builder

Opened: October 23, 2025

Description

We have noticed a discrepancy between the Pages Builder interface and the Content Editor in XM Cloud regarding page title lengths:

In Pages Builder, attempting to enter a page title longer than 50 characters results in a validation error.
In Content Editor, the same title can be saved successfully, up to 100 characters.

Sitecore Confirmation

Sitecore confirmed that when creating new pages in Pages Builder, item names are limited to 50 characters, instead of the expected 100 characters as defined by the MaxItemNameLength setting in Content Management (CM).

This behavior has been registered as a bug in our tracking system. To follow updates on this issue, please use reference number PGS-5591.

Status: As of November 2025, this bug has been fixed.

💡 ❌ SitecoreAI Creating a page from branch template in Page Builder sometimes gives error

Description

When creating page from Branch Template → Error that page cannot be created is thrown in Pages and page is not visible until user fully reload the Pages Builder.

Sitecore Response

When you add page branches in Page Builder, a GraphQL query is executed on the CM instance. The more items you have, the longer it takes to build the item tree. If the process takes too long, you may encounter a server error due to a timeout.

By default, the execution timeout is set to 30 seconds:

<setting name="GraphQL.QueryExecutionTimeout" value="30000"/>

To increase this timeout to 60 seconds, please create a patch file. Below is a sample patch for reference:

<?xml version="1.0" encoding="utf-8" ?>

<configuration xmlns:patch="http://www.sitecore.net/xmlconfig/">
    <sitecore>
        <settings>
            <setting name="GraphQL.QueryExecutionTimeout">
                <patch:attribute name="value">60000</patch:attribute>
            </setting>
        </settings>
    </sitecore>
</configuration>

However, if page branch creation still takes longer than 60 seconds, the request will timeout at the proxy level. This timeout cannot be changed at the moment, though we have registered a feature request to support this. To track the status of this feature request, please use public reference number: SITES-3269.

If a timeout occurs, the item creation continues to run on the CM instance in the background.

🐛 ❌ SitecoreAI - Issue with Publishing Dashboard – Error When Navigating Beyond Page 100

Description

We've noticed that when there are more than 100 pages listed in the Publishing Dashboard, attempting to navigate to page 101 (or any page beyond 100) results in an error.

Sitecore Response

Investigation target: In the Publishing Jobs Dashboard, navigating beyond page 100 causes the request to fail with status code 400.

During our investigation, we confirmed that the issue is reproducible when the dashboard contains more than 100 pages. After further analysis, we've registered it as a bug in the current version of XM Cloud. Thank you for reporting the problem.

As a workaround, you can filter the records using the available options to limit the displayed results to fewer than 100 pages. To do this effectively, you'll need to know either:

the date when the publishing event occurred, or
the user who triggered the publishing job.

Filtering by one of these options will reduce the displayed records and prevent the error.

To track the future status of this bug report, please use the reference number CFW-8494.

Status: As of November 2025, this bug has not been fixed yet.

💡 ❌ Name Value List showing raw value in Page Builder

Description

We noticed that Name Value List isn't working in Page Builder, it shows RAW values. The user need to switch to Content Editor to update values. Please see Periodic table component datasource.

Sitecore Response

Sitecore XM Cloud Page Builder supports inline editing for basic field types such as Single-Line Text, Multi-Line Text, Rich Text, Image, Date, and General Link.

The Name Value List field type is not supported for inline editing out of the box.

As a result, these fields appear as a non-editable string in the Content tab on the right-hand side of Page Builder.

For your convenience, here are several resources that further explain this limitation:

Sitecore Official Documentation – The Simple Field Types
(This official documentation lists all field types supported for inline editing in Page Builder. The Name Value List is not included among the supported types.)
Fishtank – Easier Editing in Sitecore XM Cloud Page Builder
(This resource provides a detailed table of field type support for Page Builder.)

We have registered a feature request to implement inline editing for Name Value List fields in Page Builder so that it can be considered for future implementation of the product. To track the future status of this request, please use the reference number PGS-5710.

Status: As of November 2025, this feature has not been fixed yet.

🐛 ❌ Droplink with multiroot queries does not work in Page Builder

Description

We have fields like ContentType which shows data from two different places - the source on the field is set query:$sharedSites/Data/Taxonomy/Content Types/*|$site/Data/Taxonomy/Content Types/*. It works fine in Content Editor but not in Page Builder.

I see that the same issue we had with Multiroot Treelist is now fixed.

Sitecore Response

Currently, Pages does not support using a multiroot source for the Droplink field. During our investigation, we found that some other field types were also affected. We have logged this issue as a bug in our tracking system. You can track the progress of this bug using reference number PGS-5378. For more information about public reference numbers, please visit this page.

In the meantime, please use the Content Editor to select values until the issue is resolved.

Status: As of November 2025, this bug has not been fixed yet.

💡 ❌ SitecoreAI Video file cannot be selected from Page Builder

Description

Video files cannot be selected from Page Builder when trying to insert media items on a page.

Sitecore Response

The described behavior is expected.

As mentioned in this article, at the moment, only the following media types are supported in the Pages editor:

When inserting a media item on a page using an Image field, the following format are supported: .jpeg, .jpg, .gif, .png, .svg, .bmp, .ico, .webp.

The File, Link, and Rich Text field also support the following format: .pdf, .doc and .docx.

Thank you for sharing your feedback. We have submitted a feature request for this enhancement, and it will be considered for future updates. To track the status of your request, please refer to reference number PGS-4447.

🐛 ✅ SitecoreAI SXA Site Creation Wizard Changing Folder Template Types issue (remove company data)

Description

Here's the workflow we followed:

We created a Datasources folder under our Data folder using the /sitecore/templates/Common/Folder template.
We then used the SXA out-of-the-box site creation wizard with a branch template to create our website.
After the site was created, we noticed that the template for our Datasources folder had been changed to /sitecore/templates/Project/[ProjectName]/Page Design Folder ( {4E3BC3BF-A1F5-4053-8B2E-29A94F1E45AC}).

While we have a workaround by creating a new Datasources Folder template, we believe this behavior may be a bug. Can you please investigate why the wizard is modifying the template of an existing folder during site creation?

Sitecore Response

Hello Nona,

The behavior you reported was registered as a bug in our bug tracking system. Thank you for reporting the problem.

To track the future status of this bug report, please use the reference number SXA-8753.

As a workaround for the issue, please continue using your approach with creating a new Datasources Folder template.

Status: As of November 2025, this bug has been fixed.

🐛 ❌ Sitecore AI Multiroot Treelist not working in Pages

Description

We have a specific field of type Multiroot Treelist in our solution. The field's source works as expected in the Content Editor - the available items are displayed correctly in the selection list. However, when attempting to edit or browse the same field in Pages, the selection dialog opens but no items are displayed in the results list. This behavior is inconsistent between Content Editor and Pages, and prevents content authors from selecting or updating the field values directly from Pages.

What we found was:

The issue is in Pages Builder its not supporting 2 different root folders in query.

Sitecore Response

We were able to reproduce your issue in our own environment when specifying 2 root folders in the "Source" query of the Multiroot Treelist field. Since this is not the expected behaviour, we have registered this as a bug in XM Cloud.

As a workaround for this issue, you can use the Content Editor to edit the Multiroot Treelist field values. You may use the "Open in Content Editor" option to directly navigate to the relevant item located in the Content Editor.

To track the future status of this bug report, please use the reference number PGS-5378.

Status: As of November 2025, this bug has not been fixed yet.

ℹ️ Observations Regarding V2 Publishing Behavior in XM Cloud Environments

Description

We noticed slow publishing in our XM Cloud environment. Publishing a single page still took around 20 minutes — can this process be optimized or expected to be faster?

Sitecore Response

This scenario can be optimized by disabling deep scan related items based on this article: Enable or Disable Publishing Deep Scan.

Here is the code:

<?xml version="1.0" encoding="utf-8"?>

<configuration>
    <sitecore role:define="ContentManagement">
        <settings>
            <setting name="Publishing.DeepScanRelatedItems" value="false"/>
        </settings>
    </sitecore>
</configuration>

Sitecore Tickets opened in 2025!