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

Why SitecoreAI - Getting into the shoes of the customer how to select right CMS

Hi Team, Lately, I have been talking to lot of our customers / potential customers and having pre-sales demos where one question always comes is "Why Sitecore" ?  Now this question can be for any product which is out for sell. And as a technician I always get into product technical features, but at the same time as a pre-sales guy, it also makes me think, surely all competitive products have same features, so definitely answer to this is not in the technicalities.  If you step back and think, we are also a customer in our daily life and buy lot of things, what is that process we go through? When we buy, how can your customer decide if this is a right fit for you or not, why we select A over B? Is it price? is it service? Is it a brand? Is it about features? Is it about brand loyalty?  When it is a technical product, I am sure it cannot start with the technicalities of the product or selecting product itself, 100% not, I feel decision is always business strategy first and ...

Hell of sitecore aliases pipeline breaking the site with 500 error

Hello Friends, I belive this blog post is very important for everyone because, It has some very serious effect on working of your headless website, i will share my experience what we faced and how we resolved it Issue we started facing Our site started giving "Key cannot be null or empty" with YSOD like following  Side affect Because of this 500 error, Our site pages were showing 500 custom error page intermittently and our MAU (Monthly Active User) drop rate increased. Sitecore KB There is already Sitecore KB article talking about this error but the patch which is provided on this link is confusing as well as very huge and it could bring other issues along with it as that upgrade patch also has lot of other things too which i did not want to introduce in our stable CMS. Known Issues - Retrieving the child items of resource items is not thread-safe Observation Though the surfaced exception was looking similar and giving same error and behavior given on this article, We looked...

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