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


6

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}"; ...


5

You are trying to get Datasource from an item which is retrieved using Get-Item. Instead you should get datasource from Item retrived using Get-Rendering Change this code $Properties = @{ RenderingItemName = $renderingItem.Name RenderingItemID = $renderingItem.ID RenderingItemPath = $renderingItem....


3

The manifest API is a JavaScript API; we just provide a default input via YAML. You can modify the handling in /sitecore/definitions/*.sitecore.js to source content from whatever you like, including multiple items in one JS file. Example here, note that the manifest contains TypeScript typings to make constructing objects easier.


2

By default Sitecore does not do such a thing. You still need JavaScript to reload the Article in the other component. On the like button click event you can search for other Articles on the page which has the same ID as the liked Article and then do an AJAX call to the rendering which needs to be updated. So you will have 2 actions in the Controller (if you ...


2

Post analysis and confirming that there is nothing wrong at the code/project side, we decided to raise a Sitecore Support ticket for the this experience. Later on the support team identified it as a BUG in Sitecore. This weird experience was due to an issue with improper parsing and double quotes, which was registered as a bug in their bug tracking system. ...


2

Starting form SXA 1.7 we've added an option to extend the component's script and we are using it also in the SXA to change the behaviour of few components in the Edit mode. You can create new Theme which will be extending our scripts or include those scripts in your current theme. Here is how this is done in SXA. Navigate to /sitecore/media library/Base ...


2

For reference we were experiencing the same error and found that it was caused by having a Controller HTTP Post action with the same name as the view (when using SXA). Changing the action name resolved our issue.


2

Find out the name of the placeholder that you are inserting into by hovering the mouse over the "Add here" button. Let's assume it is the 'content' placeholder, go to Content Editor > navigate to content (/sitecore/layout/Placeholder Settings/content), Go to the "Data" section, "Allowed Controls", click Edit and then add the desired rendering (or all of ...


1

I think you might already have checked these though, but if not this would be helpful: Did you add the renderings in the Allowed Controls? If not, you should add the renderings in the Allowed Controls of that placeholder present in the Placeholder settings. Screenshot below for reference.: Check the "Editable" checkbox is checked for the ...


1

Welcome to Sitecore community. Url rendering is explained here . Url Rendering This rendering type renders the response of a HTTP GET request onto the current page. You can use it if you need to screen scrape HTML from another system. Can sometimes be used to avoid using iframes. In Genreal, if you need to display any website in iframe in ...


1

Having contacted Sitecore support it seems that there is a bug when creating an SXA 1.8 instance on Azure, it does not include all of the necessary items for the Master database. The workaround to this problem is to install Sitecore 9.1 and then to manually install Powershell 4.7.2 (or 5.0) and SXA 1.8 To track the future status of this bug report, please ...


1

Based on the wording of using "Sitecore instance" I think you have decentralized your authoring? One architectural approach would be to use a centralized authoring pool that manages all the content as multiple sites and then have your separate CD's with separate publishing targets so that you can maintain your end-user performance. In this way, you could ...


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