26

This should give you what you want: @using (Html.Glass().BeginRenderLink(Model, m => m.MyLinkField, null, true) { @Html.Glass().RenderImage(Model, m => m.MyImageField, null, true) }


19

Maybe not an easter egg, but MainUtil class contains some "useful" methods like: My favorites: /// <summary>Returns false.</summary> /// <returns></returns> public static bool False() { return false; } /// <summary> /// Returns <c>true</c>. /// </summary> /// <returns></returns> public static ...


16

In multi-site solutions, when you edit an item in the Experience Editor, Sitecore will by default resolve the site context using the value of the setting Preview.DefaultSite. It's located in Sitecore.config, and my guess is that you currently have it set to mysite1: <setting name="Preview.DefaultSite" value="mysite1"></setting> This means the ...


16

I wrote a PowerShell cmldet for merging Final Renderings back into Shared Renderings. function Merge-Layout { [CmdletBinding()] param( [Parameter(Mandatory = $true,Position = 0,ValueFromPipeline = $true)] [item]$Item ) process { $layoutField = New-Object "Sitecore.Data.Fields.LayoutField" -ArgumentList ($Item.Fields[[...


16

I have previously found 2 secret CLI commands in Sitecore JSS: elephant-in-the-room: > jss elephant-in-the-room JSS CLI is running in global mode because it was not installed in the local node_modules folder. _.-- ,.--. .' .' / | @ |'..--------._ / \._/ '. / .-.- \ ( / \ \ ...


14

Answers here are a good start but the database the page/experience editor is using is configurable in the <site name="shell"> node of this website. On Sitecore 8.0 and older, in your web.config file. On Sitecore 8.1+, in the /App_Config/Sitecore.config file. The default configuration is: <site name="shell" virtualFolder="/sitecore/shell" ...


14

Ensure that the component (either the sublayout, view rendering item or the controller rendering item) has it's "editable" checkbox checked.


14

As long as your app is capable of server-side rendering (SSR) then you can render it in a Sitecore Content Management (CM) role and use Experience Editor (EE) to manage the app and content for the app. Beyond that, your app can live on a Node.js server somewhere (separate from Sitecore) and consume Layout Service data for rendering. You are not able to use ...


13

This is a known bug. I've seen it fixed in the 8.2 release notes. https://dev.sitecore.net/Downloads/Sitecore%20Experience%20Platform/82/Sitecore%20Experience%20Platform%2082%20Initial%20Release/Release%20Notes - reference 82835. Unfortunately, I've not seen any workarounds for your release. I suggest you get in touch with Sitecore support. Eventually, I ...


13

The minimal out of the box sitecore role that gives you such capabilities(considering no overrides were done) is sitecore\Sitecore Client Designing If you need to assign a role to your own custom role you can give read access over the buttons chunk beneath /sitecore/content/Applications/WebEdit/Ribbons/Chunks/Layout Modes And the the actual tab sections ...


12

Well, now it's working all of a sudden after having spent most of the day on this... What I've done recently is run the Clean up databases from the Control Panel and rebuild the link database and the search indexes. So, if you run into this issue try that. The generated sprite files are located here: \sitecore\shell\client\Sitecore\Speak\Ribbon\Assets\...


11

The page editor (a.k.a Experience Editor) is used to edit content, so it uses the master database.


11

The replace button doesn't appear on Experience Editor in 2 cases : When rendering doesn't have any renderings or sublayouts in Complatible Renderings field. When Renderings or sublayouts are not in Allowed Controls of the Placeholder Settings.


10

So it's took me all of yesterday and most of today to figure this out. In the end it was nothing to do with my code or configuration at all. The log files showing some errors were a Red-Herring and leading me in the wrong direction. It is a Sitecore bug with 8.1 Update-2 (public reference: 108023). This blog post was really useful for identifying it: http:...


10

There's a straight-forward way to add an Insert button to the Edit Frame of components. Set Experience Editor Buttons Sitecore comes with some Custom Experience Buttons which can be added to renderings. To achieve what you want, add the Insert one to your rendering: When added, you'll see the icon appear in the Edit Frame of the rendering: Set the Insert ...


9

For those who can't upgrade to 8.2, sitecore support has provided a solution. I'll post the code here as I don't know a better way of sharing the library. As a reference Ticket number: 471609 | Sitecore Support - Bug #109428 Code provided contains 2 classes and a javascript change. LinkRenderer.cs overrides default RenderFieldResult method ...


9

I'll gather information from the comments and post them as a community wiki since not everyone is reading the comments and answer is always an answer. This issue might occur if there are multiple site definitions. Potential reasons: Accessing sites using different hostname that is defined in the site definition Preview.ResolveSite property in the Sitecore ...


9

This is normal behaviour if you didn't set Datasource Template for your rendering. If you don't set the template is it normal to not enable that button because you don't know what kind of template your component support like a datasource. Please check this link to find more information : https://varunvns.wordpress.com/2015/04/28/page-editor-experience-set-...


9

As jammykam has said above I'm not aware of any OOTB way of doing this, despite dictionaries being part of Sitecore for quite some time. I spoke to a friend who has implemented this and I thought they wrote something from scratch, but apparently they based it on the blogpost above mentioned by Sitecore Climber: http://jockstothecore.com/editable-dictionary-...


9

What you want to do is take advantage of Sitecore's branching functionality. A branch in Sitecore is basically a prebuilt item tree that will be copied and inserted where you want it. It could be one item or a thousand items. In your case, what it helps you do is to build out a page, with all the related data folders under the page. All delivered in an ...


9

This is an issue for Sitecore XP 9.1.0 (Initial Release). It is not reproducible in the Sitecore 9.0.x and pre-release version of Sitecore 9.2. If you need a hotfix for Sitecore 9.1, you can request the fix from Sitecore Support. Public reference number is 312777.


8

Yes - you are using the Raw Value when you do @Html.Raw(Model.SampleItem.Text.Raw) - this bypasses the field renderer and so will not be editable in the Experience Editor. Instead of .Raw use .Rendered - this will render the field using Sitecore's Field Renderer and add the page editable parts. @Html.Raw(Model.SampleItem.Text.Rendered)


8

The value of the checkbox is set on a per user basis and stored against their profile (which means it is remembered across sessions and browsers/computers). Force Field Validation to be Enabled To force this checkbox to be enabled, you can set it against the user profile when they log in. using Sitecore.Diagnostics; using Sitecore.Pipelines.LoggedIn; ...


8

Stiecore have a few ways to enable content editing in the Experience Editor. This is not specific to treelist field but can be used for other fields as well like multi list etc. As alternative to Edit Frames the similar functionality can be implemented quite simply with the help of Custom Experience Buttons. You can use standard Sample Item template, item ...


8

I think you should Try disabling .config file of any additional modules in your Sitecore instance. Since it's possible that some module is built by old WebEditCommand which was in Sitecore.Client.dll whereas in Sitecore 8 it's moved in Sitecore.ExperienceEditor.dll as suggested here https://sitecore.stackexchange.com/a/2464/172


8

I believe the item you're looking for is here: /sitecore/system/Settings/Security/Policies/Page Editor/Navigation bar/Can Edit in the core database. By default, the Sitecore Limited Page Editor or Sitecore Minimal Page Editor roles seem to deny read privileges to that button.


8

http://jockstothecore.com/defaulting-shared-layout-editing-sitecore-8-1/ A simple setting is not available, but in the blog post above you can find code for a custom processor for the loggedin pipeline that will do the trick. You can still choose on which environments you add the pipeline processor (live only dev). The code itself will set the Registry ...


8

I was able to supply the view layer with EditFrame HTML by adding the opening and closing HTML markup into my MVC Model. HTMLHelper Step 1: Obtain access to HtmlHelper using your current context Controller and a "Fake View". public static HtmlHelper GetHtmlHelper(this Controller controller) { StringBuilder sb = new StringBuilder(); ...


7

The sites are recognized using hostname and virtualPath. If your users login to EE using hostname from mysite1 and edit items they are using following url: http://mysite1?sc_itemid={...} so Sitecore, when attempting to recognize the site will match it to mysite1 because the hostname will match even if the actual item is from mysite2


7

No, it's not possible without custom code. And to be honest, I don't think this is really what should come out of the box with Sitecore. Your component uses Datasource Folder item as datasource and that datasource will be published. And it's your own code which takes children of that datasource and uses them to display some content. That's why I would say ...


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