Skip to main content

Sitecore SXA "Add here" button not available and not able to move components from experience editor

 Hi Folks,

Hope you all are doing just fine and getting yourself vaccinated and staying home, Today i would like to share one information or a scenario which we encountered last week.

Scenario

We are using Sitecore SXA (Version is not important here as it will same for all), and one of our content author logged a bug that, they neither able to see "Add here" button on specific place holder nor they are able to move the component on the page in different location, Move option was disabled, and they wanted to have a freedom of moving component here and there and also "Add here" is a vital functionality to add component to specific place holders.


 

Troubleshooting

With my surprise as i have never seen this behavior before, 

1) I first check their access rights but they had all of needed permissions and they were able to do things normally before.

1) I started looking into place holder restriction and different settings of allowed renderings to see if there are no such restrictions which content authors are not aware of.

But there was nothing of that sort i found out.

2) Now to dig in further, I concentrated my troubleshooting around partial design, page design and the item or page itself to see how components are placed, and i could see that there was nothing placed on page design or partial design, but everything on a page's presentation details only

As we know, There are three default place holder that comes up with SXA partial design

Header, Main and Footer

Now rule of thumb for SXA is 

"When you put rendering on main placeholder using partial design, you will not be able to add renderings from content item (page)"

And that is why my initial checking was to see if there are any components on partial design, but strangely there were no components on partial design.

3) Now started decided to create one empty page using those same page template where these partial design were mapped, and strangely the behavior was same, so one thing was sure, it was not due to any renderings on the page which was causing issue as with empty partial designs also it was not working, so one thing was ruled out, that page item has no issues.

4) Now i decided to remove one by one partial design from the page design which was mapped to page template, so i first removed header partial design from the page design which was assigned to the page item, and with my surprised things started working, i had no idea why removing header partial design worked, and why header partial design is causing issue to the main page item?

5) Now it was time to inspect rendering on the header partial design, there were standard menu items and other things, at first glance things looked ok, but looking into detail, i decided to look what are the place holder used for those renderings, and one of the rendering had "main" place holder instead of "header"

 

 
So if you are configuring rendering for header, there is no logical point to use "main" placeholder, if you want to utilize "main" placeholder, you would use different partial design which supposed to use "main" placeholder which will reside in center portion of the page

so i decided to remove "main" placeholder and i used "header" placeholder instead, behavior of the component did not change because it does not matter if you put it on a header or main, it was just a global component that should be on all the page, but it fixed our issue 

Solution

In SXA, if you have put item in "main" holder from partial design itself, it will not allow you add item from content item or page item in that same place holder, and that is the reason "Add here" was not shown, because SXA saw that there is already an item in "main" placeholder (though it was added from header partial design, but rule still applies) and hence it locked that placeholder as it was used and did not allow to add items from content items.

And now move button was also enabled and components were movable too, and "Add here" button was also visible on main place holder to add items on to that place holder.



Hope this will help other people running into this type of issues.





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

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

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