22

You can do this with Sitecore PowerShell Extensions. PowerShell Extensions 4.5 or Higher Use the Set-ItemTemplate commandlet with the -FieldsToCopy parameter. $rootItem = Get-Item master:/content; $sourceTemplate = Get-Item "Template-B-Path-Or-Guid-Here"; $targetTemplate = Get-Item "Template-A-Path-Or-Guid-Here"; Get-ChildItem $rootItem.FullPath -recurse ...


19

A safer method would be to use the DbBrowser. You can find this by going to <yoursiteurl>/sitecore/admin/dbbrowser.aspx. You will get a screen where the content tree loads up on the left and you get a raw view of fields on the right: This screen does not run any of the validation elements from the main content editor. It just browses the database ...


18

You can rename Title2 to match name of Title1 and then simply change the template. Sitecore will preserve data if the names of the fields match. Template A Title1 Single-Line Text SubText1 Multi-Line Text Body1 Rich Text Image1 Image Template B Title2 -> Title1 Single-Line Text SubText2 ->SubText1 Rich Text ...


18

This seems like a perfect taks for Sitecore Powershell Extensions First of all I would get a list of template IDs to remove $templateIds = Get-ChildItem /sitecore/templates/you/better/know/where/to/look -Recurse | ? { $_.TemplateName -eq "Template" } Then you can search your other templates for inheritance Get-ChildItem "/sitecore/templates/...


17

Sitecore doesn't expose the version manager [you've shown] on templates. However, you can use the DB Browser (~/sitecore/admin/dbbrowser.aspx) and manage items, templates, etc. that way. Simply point your browser to http://instance/sitecore/admin/dbbrowser.aspx: Then navigate to the template you're looking to modify and select the version you're after and ...


16

With Sitecore Experience Accelerator you can forget about previous methods, however, there is nothing that will block you from using them. Before - NO SXA: you had to decide how your page will look like before you entered content (because the presentation was stored either on SV or somewhere inside different branches) you couldn't easily switch your ...


14

If the workflows are not drastically different, you can achieve 'site-specific' workflow via content security. Step 1: Workflow security Create a single workflow definition with some generic access roles for each state. Use these only to grant access to the workflow states. Step 2: Content security Create a security role for each site and assign it to ...


14

In reality, you have only 3 options. However the combination of checkboxes gives you 4. The Answer A versioned field (default) This acts like one would expect. The field can have multiple values and multiple versions of a value; for multiple languages. The Unversioned Field Essentially this field gets 1 version per language, so the designation "...


11

Yea. Change your code to this: var templatePath = "User Defined/Project/Common/Content Types/Links"; var template = TemplateManager.GetTemplate(templatePath, Context.Database); If your path starts with "/", Sitecore will assume it to be absolute.


10

Sitecore stores fields for templates as individual Items. As they are Items, they have a unique ID that can identify them. When Sitecore stores the values of fields for an item (most commonly in the SQL database), it references them via this unique ID rather than the field name. Because of this, this means that a Sitecore item can inherit from multiple ...


10

You can use the ID instead of the path in your initial source: DataSource={C46A-4...CE}&ExcludeTemplatesForSelection=Bar


10

Whenever I do this, I create a new template that I inherit. If wanted to add a new field called widget, I would create a new _template called _widgetdata (notice the _ to dictate the fact that this should only be inherited). And in _widgetdata add my widget field. Now go to /sitecore/templates/System/Templates/Standard template and inherit the _widgetdata ...


9

It sounds like you have a matching item in /sitecore/System/Dictionary/. I did a quick test by adding a Dictionary item that matches the name of a field and the Content Editor picks it up.


9

Template field sections are for grouping purposes only. It doesn't matter if there are multiple sections with the same name. If there are multiple sections with the same name, Sitecore will display all their fields under one section while author wants to edit item based on that template in Content Editor. It's different with fields. It is possible to use ...


9

A solid option is to build components that have a data source item rather than relying purely on fields defined on the page. Here's a scenario to help explain what I mean: Let's say you need to render a hero on the page, along with a few promotional items. I would imagine that the hero image is defined on the page, since many of those page types could use ...


8

You're going about it wrong. Or - I should say - not in accordance with Helix principles. First and foremost, your idea of a common base template to be used on all websites is not recommended practice. What Helix Documentation States The architecture does not have the concept of a single common base template across all templates – which is a practice ...


8

From my understanding Default Value In the definition item for each data template field, you can specify a value for the Default value property. When a user creates an item, Sitecore copies the default value from the field definition item into the corresponding field value in the new item. Standard Value The Standard Value can be a token or set of ...


7

If you have not already used a base template with presentation, this will be tricky. Normally I would have a base page template with some core presentation elements and then all other page templates would inherit from that - also I try to have very few page templates. For your problem you are probably going to have to add the element to the standard values ...


7

It is a quite interesting question. I've never thought about it. I fully agree with previous answer except using tokens. Tokens can be used in the Default Value as well as in the Standard Value. I also want to add some differences between them: Default Value is a shared field and if you develop a multi language solution it will be impossible to set a ...


7

The main difference is, one stores an Integer and one stores any number, e.g. 12.50. There are a couple of caveats. The decimal separator is different between countries. And Sitecore's default input validation will be based on the current locale of the Content Editor user. Which is fine if they all run Sitecore in "en", but more of a challenge if some run ...


6

In a clean install of Sitecore 8.1 update-3, the templates and their related sections/fields are always created in English, no matter what language the user may be working in from the ribbon: But if your user/developer has changed their language preference in their profile (Control Panel > Region and language options > Display language) then the ...


6

Branching off of @SzymonKuzniak's answer, the simple answer is "no" but the complex answer is "yes, with some trickery, by tapping into the getLookupSourceItems pipeline." In order to minimize development cost and maximize your extensibility, maintainability, and reusability, my recommendation would be to write a processor for the getLookupSourceItems ...


6

Another way to do this is using Sitecore Powershell Extenstions. There is a cmdlet called Remove-ItemLanguage, this removes the specified language version from the item. Example that removes the German version of a template: Get-Item master:\templates\User Defined\MyTemplate | Remove-ItemLanguage -Language de-de You could create a script that would load ...


6

Try putting the below in the standard value's raw values: <link text="link text" linktype="internal" class="" title="" target="" querystring="" id="$id" anchor="" />


6

Standard values are default field values used as fallback, if the item does not have a field value defined. If your item has a field value (even an empty field value), the standard value is ignored. If you want to revert back to the standard value, simply deleting the field value is not enough, since this will just change the field value to empty. Instead, ...


6

Sitecore PowerShell Extensions At first your question made me think of this where the user wants to find media items of a certain length. I encourage you to check that out to see some different ways you can use SPE to query items. Option 1 Your case is similar but may be a little expensive. In that case the Sitecore Content Search API may be ideal for you....


6

When you are creating new Tenant and Site in SXA we have it automated with our scaffolding logic, you will find actions to create tenants and sites and they basically do all the work for you. You don't need to think about defining any inheritance as those scripts will do this for you (unless you have any custom extensions). When you are creating tenant then ...


6

Yes, but not OOTB. You would need to roll a custom token. Maybe something like $namelower. To do this you would extend the ExpandInitialFieldValueProcessor Here is an example: using Sitecore.Diagnostics; using Sitecore.Pipelines.ExpandInitialFieldValue; namespace CustomExpandTokenProcessors.Pipelines { public class CustomTokenReplacer : ...


6

welcome to SSE. If I'm understanding your question right, it sounds like you need to use branch templates to do this. A branch template will allow you to set a predefined tree structure, like a parent item with 1 or more child items. Then you would setup your insert options so that instead of inserting a new item based on the parent template, you would ...


6

This is what Standard Values are for. You can set the value of the field on the __Standard Values item underneath the template of the item you're creating (or a base template, if you prefer): If the __Standard Values item does not exist under your template, you can add it: Select on your template in the Content Editor Ensure the Builder content tab is ...


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