Skip to main content

XM Cloud - Place holders path missing from serialization module

Hi Team,

As i have been setting up Sitecore XM Cloud instance, I have been following the guide Set up local , Which is the best guide available to get started with XM Cloud, i have been following the same but there are some issues with that page which i already have raised previously and have also get them verified with Sitecore support too.

Similar thing i found before few days, After all serialization module given on the https://doc.sitecore.com/xmc/en/developers/xm-cloud/walkthrough--setting-up-your-full-stack-xm-cloud-local-development-environment.html  link, There are some steps given on to create serialization module and it also ships with one .module.json file too

But when you use that guidelines and serialize things in your local by fetching from cloud instance and pushing it into your local instance, One of the item shows GUID instead of item


Solution

If you closely see the module.json given on the guide, it is only showing couple of item paths to be serialized 


As you can see it only suggest to have these three items to be added to module.json file, now when you actually do pull from cloud and push into your local, it uses same module files and syncs items into local (Though it is just a get started guide, and will not have all the detailed serialization, But because if we follow this guide we will end up having GUID instead of item path and hence it think what ever items are needed should be part of this starter guide and hence it needs to be fixed)

But because the site's setting item expects the reference to "Placeholders Path" item too, and Because the Sitecore->Layout->Place holder Settings path is not present in the serialization module, it is not creating that item, but setting item is already expecting that item, and because it is not able to find that physical place holder settings item path, it is showing the GUID

FIX

Because serialization is expecting this item, Just add below in the serialization module 

{
"name": "layout",
"path": "/sitecore/layout/Placeholder Settings/Project/<sitename>",
"allowedPushOperations": "CreateAndUpdate"

Now if you delete all serialized item folders from the disk and re-run the steps by fetching from XM Cloud remote instance and push it into local instance, you will see that now the items is just showing fine, Because it has been included in the serialization module which setting's item was expecting


I have raised this with Sitecore support team about this behavior and they have acknowledged the behavior and they have registered this as a bug, It should be rolled out soon.

Thank you.

Comments

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...

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 ...

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!!!