9

Yes, you can do it by the following way. Configuration: <configuration xmlns:patch="http://www.sitecore.net/xmlconfig/"> <sitecore> <pipelines> <mvc.renderRendering> <processor type="YourAssembly.LogExecuteRenderer, YourAssembly" patch:instead="processor[@type='Sitecore.Mvc.Pipelines.Response.RenderRendering....


6

You can answer this question on your own by using DotPeek. The GetSiteLevelCaching processor in GetRenderingCaching pipeline is responsible for processing those items. The code looks like this: public void Process(GetRenderingCachingArgs args) { ... var renderingId = args.Rendering.RenderingItem?.ID.ToString() ?? args.Rendering.RenderingItemPath; ...


6

I've not completely test this using Sitecore PowerShell Extensions, but it should get you pretty close. $item = Get-Item -Path "master" -ID "{961563FC-3445-4558-BF3A-06DF06BA6298}" $renderingItemId = "{93F07F46-F356-419A-B937-A5EB2A9D63DD}" $placeholderId = "/content-body/secondary-column-left" # Accepts Hashtable, Ordered Dictionaries, etc. $parameters = [...


5

Got the answer, here is the complete code. In my case I'm updating the Display Subtitle field but you can change this field or make the field name a variable if you want to: public void SetRenderingParameterValue( Item item) { using (new SecurityDisabler()) { string defaultDeviceId = "{FE5D7FDF-89C0-4D99-9AA3-B5FBD009C9F3}"; ...


4

Turns out it was a bug - reference number 355958. The issue was related to the fact that sxa data-source selection dialog overrides default dialog for EXM(non-sxa) site. Hotfix available from Sitecore support.


3

SetImageStyleParameters from Sitecore.XA.Foundation.SitecoreExtensions.Pipelines.RenderField is responsible for that. It is used to add HSpace and VSpace from image properties. I don't know which version of SXA are you using but in the newest version, it should not add any additional margin when both HSpace and VSpace are 0. If you don't need it, simply ...


3

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

By default __Final Renderings is versioned and not shared, so make sure __Final Renderings filed in template "/sitecore/templates/System/Templates/Sections/Layout" as below.


2

The main difference is how the components are rendered in the experience editor when editing the partial. When editing a Meta Partial Design, it uses a special Metadata Snipped Layout.cshtml. This enabled 3 placeholders that are not available during normal page or standard partial design editing. They are: head body-top body-bottom It also renders out raw ...


2

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


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

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

Based on this blogpost, you can do it in the following way: item.Editing.BeginEdit(); layoutField.Value = layoutDefinition.ToXml(); item.Editing.BeginEdit();


1

What you want can be done like this: <h2>@Model.Title</h2> <div>@Model.Paragraph</div> <hr /> @foreach (Sitecore.Data.Items.Item section in Model.Sections) { @Html.Sitecore().Rendering("/sitecore/layout/Renderings/MySectionsRendering", new { DataSource = section.ID }); } Side note: I do encourage you to ...


1

It doesn't look like you can access the placeholder in the getRenderingDatasource pipeline unfortunately. There is an potential solution posted for this here from Ruud van Falier though: https://stackoverflow.com/questions/26225480/sitecore-dynamic-data-source-locations?rq=1 Create a processor for the getPlaceholderRenderings. The ...


1

Depending on what you want to achieve. If you will use standard Variant Field you will see something like this: for such field: If you want to have a more fancy look & feel I would suggest writing your own Variant Token. A sample implementation can look like this: public class ResolveNameValueList : ResolveVariantTokensProcessor { public override ...


1

I don't think you are using Helix in your project. But if you want to still use the same structure. You can update your current architecture like this: -Global -All the data that can be shared -Site 1 -Home -All the pages here -Data - Only data related to Site 1 here -Settings - Site related setting only -Site 2 -Home -All the ...


1

Apologies for the Short answer. What you can try to implement is to use PageContext.Current.Item which will give you the Current page item or RenderingContext.Current.Rendering.Item Hope this helps!


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