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

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

Every Sitecore Instance using GQL is prone to this scenario of template not found - Sitecore Component With GQL Queries Broke On Production

Hello Team, Today, I wanted to share a real scenario and a solution of it about what happened  suddenly to our components and how we identified it and how we resolved it, and most importantly it could happen to your installations too Scenario We have one Sitecore 10.2 headless instance and two sites, One site is non-sxa which is legacy site and another site is a new site which uses headless SXA. Now, non-sxa site is already live and working fine with all components etc. and the new headless site was in development and it has separate development team, So we have same DEV/UAT/PROD environments. One fine morning they took their code and site on environment but strangely some of the GQL components like header footer of legacy site disappeared.  Troubleshooting Steps 1) We checked the broken component's GQL query  2) We took that query and fired it in GQL IDE, and we observed that, Some of the templates references we used were not found, which was working just fine and we hav...
18 comments
Read more

401.1 Unauthorized with windows authentication error code 0xc000006d

How many of you have faced this hosting issue when you do everything what it takes to run the site with windows authentication but still you are getting the same error again and again? If you think you also have faced the same issue and you tired of reading MSDN KBs for it and still have not found the issue (If KB has solved the issue, well and good, if not you can try this trick),Please Read below Typical scenario In typical hosting with IIS, i did every possible things like enabling windows authentication, changing it in web.config, configuring connection pool, authorization rules, it asks me for window authentication login and despite of entering correct credentials it always fails and keeps on asking for login, and when pressed cancel it gives 401.1 with 0xc000006d error code Solution (Which worked for me at-least after trying for almost 6-9 hrs) You need to change the Loop Back Check in registry so that it allows the host names which you are giving in url are allowed and au...
2 comments
Read more