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

Zero to Hero - A real life RCA of exact issue in Sitecore Managed Cloud environment

Hello All, The purpose of today's post is to share a real life burning and escalated scenario which was new to me and how did I approach it and how big the escalations were and what was the outcome Sitecore's goodwill was at stack not because Sitecore is not capable of handling it but just because our environment was Sitecore Managed Cloud, and any issue that comes if its infra, back end code, front end code will be first pointed as Sitecore issue and that is where our consultancy and experience will play a role to prove that it is not Sitecore issue.  Issue we faced Out of the blue our site started giving "504 Gateway Time-out", and it was reported that almost everyone is getting this error, but when we used to browse the site, everything looked good and never 504. 504 Gateway Time-out error tells that, That the request went to Content Delivery servers of Sitecore from gateway, but gateway did not get response in time from those CDs and hence it gave time out error. ...
2 comments
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

Set up leprechaun code generation with Sitecore XM Cloud Starterkit

Hi Sitecorians, It has been amazing learning year so far and with the change in technology and shift of the focus on frontend frameworks and composable products, it has been market demand to keep learning and exploring new things. Reasons behind this blog Today's topic is something that was in my draft from April-May, and I always thought that there is already a good documentation out there for  Leprechaun  and a blog post is not needed, Until I realized that there was so many of us facing same kind of issues and same kind of problems and spending same amount of time, That is where I thought, if I could write something which can reduce that repetitive troubleshooting time, That would really help the community. 1)  In a project environment, if we get into some configuration issues, we resolve them, we make sure we are not blocked and continue, but if you think same issue, same step and same scenario will come to other people, so if we can draft it online, it will help othe...
Post a Comment
Read more