Ghanendra's Tips

This post intends to get you familiar with where Sitecore keeps code for dialogs that are rendered in Experience Editor and how they can be modified using a problem we solved recently. PROBLEM We may want to hide some out-of-box elements in Sitecore's Experience Editor for meeting specific business needs. In our case, w e were upgrading from Sitecore 8.2 to Sitecore 10.1.1 recently and migrated our vanilla Sitecore sites to be SXA site.  We decided to keep content author experience in Sitecore 10 instance as close as possible to Sitecore 8 so that we don't end up re-training our content authors spread globally almost in every country. Obviously, SXA presents a slightly different interface in Experience Editor and we started finding workaround for them. We observed that, in Experience Editor, while creating/selecting a rendering's datasource, there is a new  Clone Current Content option which didn't exist in Sitecore 8 as in snapshot below -  This option was new to Conte

Sitecore server performance depends a lot on underlying SQL server performance. If SQL server performance decreases, Sitecore server performance will decrease too. That's why its important to have SQL server maintenance plans.  Maintenance plans create a workflow of the tasks required to make sure that your database is optimized, regularly backed up, and free of inconsistencies. You can learn more about maintenance plans here . We observed that a poor maintenance plan can lead to SQL timeout errors in application and the high fragmentation level in the SQL indexes can have major role to play in it. Sitecore recommends keeping index fragmentation below 10% If you see error in your logs which read something like below, its time for you to check your index fragmentation levels and revisit your SQL server maintenance plans -  Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. How to know if index fragmentation is