4

Versioned layouts make it possible to specify different layouts for different versions and languages of the same item. In the Standard fields of a versioned item, in the Layout section, two fields are for layouts: __Renderings – a shared field where you specify the common layout for all languages and versions of the item. __Final Renderings – a versioned ...


3

You can get the final and shared layout using the following code. You can refer Get amount of components on final layout programmatically // Returns the number of shared and final renderings for an item. // Final renderings are based on language/version of the item. // This presumes there is only one device with renderings configured. public static System....


3

@john, look into your Site Groupings for SXA. This sounds like a case where the web editing functionality isn't available for your page for your site grouping and it's falling to another site grouping or the website site. Ensure that you have Site Groupings that are appropriate for the page that specify the correct database and editing options that you'...


2

This is a known bug in Sitecore 9.1. You can create a ticket with Sitecore Support to obtain the hotfix patch. You can refer to public reference number 315995.


2

Rendering is quite complicated in modern Sitecore versions. (With SXA even more complicated). "Final"(please don't confuse it with Final Renderings field) rendering XML is quite complex. If simplify it, it is merged XML from standard values on template then from Renderings(shared) on the item then with Final Renderings field. I suggest you to check ...


2

Yes you can add any component inside the SXA Accordion component, each accordion item by default has a Page Content component added in the "section-content" placeholder, you can either delete or keep this component, and you can add your CheckList Filter in the "section-content" placeholder.


1

If you have the pageItem which is an instance of Sitecore.Data.Items.Item class, you can wrap your code into a DatabaseSwitcher and DeviceSwitcher using (new DatabaseSwitcher(pageItem.Database)) { using (new DeviceSwitcher(pageItem.Database.Resources.Devices.GetAll().Where(t=>t.Name.Equals("default",System....


1

I guess there are four fields that hold presentation details, or can, potentially more with template inheritance. When an item is requested the first place Sitecore looks is the __Final Renderings field on the item to see if it has a value. Assuming it has a value the next thing is to ask if it is a full set of renderings, unlikely but possible. So lets ...


1

Assuming your code is triggered in an event, you could use an EventDisabler in your code: using (new EventDisabler()) { ... } Or (still in the assumption your code is in an event) you could use the optional parameters of the EndEdit() to do a silent save: use it like EndEdit(false, false) in your case. This will use silent mode (which actually just is ...


1

It should be enough to compare if what you want to set to other versions is really different from what is in your current language version. And only in that case start editing the item. See the code below: public static void ApplyVersionToOtherLang(Item savedItem) { if (Sitecore.Context.PageMode.IsExperienceEditor) { var ...


1

There are a few things you need to fix in your code: You are not using constructor injection in a proper way as you are manually creating your repository in GetModel() method. It should look like this: public class NotificationController : VariantsController { private NotificationRepo _repository { get; set; } public NotificationController(...


1

I believe you need to assign the following roles to these users: Sitecore\Designer Gives the user read and write access to the areas of the content tree that are required when changing layout details for individual items and groups of items via template standard values, as well as items required when configuring the Experience Editor Design Pane. ...


1

Check the below setting in Sitecore.config <!-- PREVIEW AS ANONYMOUS This setting specifies whether Sitecore will use the Anonymous user account when you preview an item. If true, Sitecore uses the Anonymous user account when you preview an item. If false, Sitecore uses the current user account when you preview an item. ...


1

This feature was added in SPE 5.1. If you install that version or newer the command should be available. Read more about it in the pull request here https://github.com/SitecorePowerShell/Console/pull/1074


Only top voted, non community-wiki answers of a minimum length are eligible