New answers tagged

0

For this kind of Issue, would recommend to uncheck caching on related component(Rendering Item) where facing issue while testing. After the change no additional step would required. For reference attached screenshot. Only change/update Sitecore item, save and publish. Try to render page, if still facing caching issue just to hard refresh (CTRL_Shift+R or ...


0

The accepted answer contains many incorrect assumptions that have been perpetuated for quite some time. The full answer to your question is below: Sitecore does this constantly. All CRUD operations (create, read, update, delete) modify the prefetch cache. This includes scaled topology such as a content delivery server. During a publish, the CM server queues ...


0

So, its making it to the web database but not showing on the site. It is most likely caching but based on how your application is coded, it could be multiple things: Output caching - If that is turned on for your layouts or renderings, they may not be getting cleared properly. It is supposed to when you publish but you may want to check your pipelines to see ...


0

Issue: Indexes are not listed in Indexing Manager. Error log: 5844 11:31:27 WARN Error connecting to solr. Solr is not running on the provided url [Url:https://<solr server URL>:8983/solr/] 5844 11:31:27 ERROR Unable to connect to Solr at [https://<solr server URL>:8983/solr/] Exception: Sitecore.ContentSearch.SolrProvider.SolrConnectors....


0

It seems that your index data directory is OK, but with some file missing. If you delete (or backup) the data directory (D:\KPSolr\solr-7.5.0\server\solr_master_index\data in your case for master index), Solr will recreate a new index automatically on startup. Of course it will be empty and you will need to rebuild index to populate it with data. I hope, you ...


0

In that case, you can define your index's root to your tenant instead of the site, then make sure you only index whatever you need and is strictly necessary (templates/field) to avoid ending up with a huge index. I hope it helps you.


1

The Sortorder takes over the default sorting by Name. When changing the Sortorder manually Sitecore will insert a value into the Sortorder (_sortorder) standard field in the Appearance section. The higher Sortorder's value the lower item's position will be. Also if an item has an empty or invalid Sortorder value then Sitecore will use 100 for calculations by ...


0

Renderings and Layout are just more fields on the template. They are a combination of the __Renderings and __Final Renderings fields. Simply add those fields to your -FieldsToCopy parameter: Set-ItemTemplate -Item $_ -TemplateItem $targetTemplate ` -FieldsToCopy @{ ` "__Renderings" = "__Renderings" ` "__Final ...


1

I see only two possible options that might hide this button in Experience Editor: Check security configuration of /sitecore/content/Applications/WebEdit/Ribbons/WebEdit/Page Editor/Publish/Change Restrictions item in core database. The current user might not have read permissions. I see the following security details on my Sitecore instance: Button state ...


Top 50 recent answers are included