Skip to main content

XM Cloud - Site folder not visible in "insert from template" dialog box

Hi Team,

Recently, While working on XM Cloud, I ran into wired issue, I did create multiple sites and create templates inside templates->Project-><<my sites folder>>

Now i wanted to now start creating pages from those templates, so i right clicked on my home item of the site and selected "insert from template" option so i can select my "Blog Folder" template and can start creating my Blog items inside it, But with my surprise, it was not showing my site folder at all and i was puzzled as to how do i select my template and why it is not showing those folder? and surprisingly other site which i have it was showing it fine


My template->Project folder actually had those site folders and templates inside it


Solution

I just compared both folder's template and with my surprise the one which was showing fine i.e "TrainingLab" had "/sitecore/templates/System/Templates/Template Folder" and the other site which was not showing had "/sitecore/templates/Foundation/Experience Accelerator/Multisite/Project Folder "

i did not know the reason why both were different, but may be "TrainingLab" was not created locally, but it was created in Cloud by using "Create Site" button, and pulled into my local using serialization, while the other one "BasicSiteA" was created locally using "Create headless site" option when you right click on "Headless Site Collection", So may be there is some different scaffolding happening in different processes.

But i decided to change the template of my "BasicSiteA" to "/sitecore/templates/System/Templates/Template Folder", i just did that and it started showing in the "Insert from Template" dialog


Because i was unsure of what will be consequences of this change, i decided to raise a support ticket and ask them about this behavior and they came up with following

I am able to reproduce the same behavior in my XM cloud instance and the reported behavior is not expected. This behavior has been 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 reference number 582905. 
More information about public reference numbers can be found here: https://support.sitecore.com/kb?id=kb_article_view&sysparm_article=KB0853187
 
As you have reported in the ticket earlier, the workaround of this issue is to replace the template with /sitecore/templates/System/Templates/Template Folder - {0437FEE2-44C9-46A6-ABE9-28858D9FEE8C}. Unfortunately, this is the only workaround that we are aware of.

 So until the bug is resolved this is the correct workaround to get unblocked, I hope this will help others finding the solution to this puzzle

Labels:

Comments

Post a Comment

Popular posts from this blog

High CPU to completely normal CPU - SXA issue, SXA pages not loading in mobile device

  Hi Team, Today i am going to share one of the nightmarish issue with you all, We are having Sitecore 9.1.1 hosted in azure PaaS environment Our site was working just fine and no noise, but we have been working on a feature release where 7-8 months of development needed to be released to production, Big GO LIVE event right?  Also to make the development smoother we also introduced BLUE/GREEN deployment slots in the same release, so we can easily SWAP slots and go live Everything went well, we went live, we even did load and performance testing on our staging and pre-prod and we were confident enough of results Very next day we started getting "SITE DOWN" alerts, and also product owners and clients mentioned that site is very slow for them in US time and in our morning when we were accessing it, it was working lighting fast so we were clue less at start, but we started digging  1) First thing caught our eyes were HIGH CPU spikes, in US time, also without any traffic CPU u...
3 comments
Read more

Sitecore Stream - Platform DxP Evolution

Hi Team, I am absolutely Sitecore Stream enthusiast, and if you also keep following what is new in it and explore it features, This blog post is for you Since it was announced in symposium 2024 and probably the first platform DxP version package was released in FEB-2025 and we are now in Sep end and there have been significant roll outs and we are into 6th release of the platform DxP package. The purpose of this blog post is to summarize all improvements which came along with different releases for all of you and community, If you have not explored all of the packages. NOTE : Remember Stream is "AI capabilities throughout the composable stack, be it Content Hub, XMC, CDP, Personalized but this blog post is only for platform DxP package for on-prem XP/XM. If you see the image above, i have tried to show the package rollout on the timeline as an when they were released and watchout for next package rollout, For other useful features :)  Important improvements 1) Less configurations ...
Post a Comment
Read more

An error occurred while receiving the HTTP response to This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details.

You have noticed many times that everything was working fine and suddenly the below error starts coming and you find no way to work it out An error occurred while receiving the HTTP response to This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details. The reason for this is the receiving size of WCF service is smaller then the data which is coming from service It was working before because it was small,So you will have to try to increase the receiving setting in your end point,Possible settings can be following maxStringContentLength="2147483647" maxReceivedMessageSize="2147483647" maxBufferSize="2147483647" maxArrayLength="2147483647" That would definately help you!!!
1 comment
Read more