Based on @jraps research, this is what I believe is happening:
$date is taking the current UTC date and storing that in the DB - if you are in UTC-4 and you create the date when the UTC date has crossed over but your local date has not, then the date will appear to be stored incorrectly. This is because when Sitecore displays that date, there is no time ...
Sitecore PowerShell has a function called Add-BaseTemplate. This function can add one or more base templates to a template item.
There are multiple ways to call it, but the simplest is to get both template items and then pass those to the function:
Add-BaseTemplate -Item <Item> -TemplateItem <TemplateItem>
You can use that to add Template B ...
I often find that field section sort order does not work across inherited templates if the sort orders are not greater than 100.
Try updating the sort orders of the field sections on your Person template to be > 100 and see if they merge better.
When you check the "Reset blank" in the field's definition item, then it will set the standard value [which you entered in the _standard value of that template] whenever you clear/delete the field value.
I used the rules engine to fix this. I created a rule under Item Saved (/sitecore/system/Settings/Rules/Item Saved/Rules/Language Fallback) that sets the enable item fallback to true on every save.
It looks like this:
where the item is the my-root-item item or one of its descendants
set __Enable item fallback value to 1
You can add any condition you ...
You need to update the Subitems sorting field on the standard value of the item. Go to the standard value and in the Appearance section of the standard fields select the Subitems sorting field, update the field and see the changes -
Using the Sitecore Powershell Extension, you can easily create the templates without going through all this process.
The below .csv file shows the entry of 1 template which contains 3 Sections.
When creating more than 1 template, the .csv will look like
Note, you can add new columns if you need to add datasources.
Sitecore Powershell Script
I wouldn't recommend creating artificial value "Choose" in the Drop list even it is possible and rather follow default Sitecore behaviour.
Solution would be a combination of setting proper help Short and Long Description texts for this field (following this Q&A -> How to add helpful text to a Sitecore field )
and setting of Validation rule (Required) ...
A treelist source can be set (and filtered) with a query. More info can be found here: https://getfishtank.ca/blog/treelist-data-source-hidden-functionality
This way you can include/exclude items or templates for display and/or selection. It is important to understand the difference between those. To be able to select the desired items, the tree needs to be ...
Technically removing the standard template from the base template of your custom template will not create any issues at system level. But you will be missing the out of box features something like setting the presentation details, Workflow, Insert Options etc.
If you don't need the out of box features or your requirement is just to create the data item in ...
I think there is some confusion here about how the template inheritance works in Sitecore.
Let's say you have Template B with Field BB, and Template A that has Field AA. Template A also inherits Template B.
Now when you create a Page based on Template A, the page will have 2 fields, AA and BB.
To read those fields, you would just get the Page item:
You need to create an instance of your template and specify your Name Value pairs in that item. See the example below:
Alternatively depending on your requirements you could employ a custom field rather than Name Value List to specify the list of values that will rarely change in the template itself. I've done this before ...
We also encountered this issue and solved it by creating an extra layer of templates - might not be the best solution but it works. So what we did:
create an extra template on top of the one you normally create as developer
keep these templates in a separate folder (structure) for convenience
pages are create based on these templates
these templates cannot ...
Finally figured this out! Most of the links I was trying to apply this validator to were of type General Link with Search. For a field type validator to run, evidently you need to have a Field Type Validation Rules template in the Field Types folder that exactly matches the name of the field you're trying to validate. The path to this field types folder is ...
You may not able to achieve this in a multilist with out-of-box features.
The query for your requirement should be like this query:/sitecore/content/FAQ/*[contains(@FAQCategory, 'Current-FAQ-Category-ID')] but unfortunately you can't build like this in source field of a multilist, because there is no way to pass your "Current FAQ Category ID" in the ...
There are many ways to go about it. You could add all the language versions you need for your Branch Template items, and add Presentation Details for all of them.
Alternatively you could edit the Shared Layout as opposed to the Final Layout in Experience Editor. Find it under the Presentation ribbon.
The short answer is, no there is not a place you can hook into for this.
As for other options, a general good practice would be to not inherit that field for every single derived template and have unique fields for each part, then you can fill out the short and long help text for those fields to be specific to that field. Ultimately, help text is part of a ...
Upload options are there only for the template:
The options can be found under /sitecore/templates/Branches/System/Media node:
If you can see upload option as administrator and another user cannot see those options, there must be something with the access rights which does not allow that user to upload files....
You can do it by implementing a custom pipeline that will change Data Sources on all renderings when new branch template is instantiated. So it will adjust all the paths for renderings to point to a newly created sub items. See more here:
Note: there was some sort of small bug that would not ...
Standard values and default values work very similarly, in that the both store values which are used on all derived items that do not specify their own values for those fields. So the value of many items are all controlled in a single place. Change it in that one place and the items all update. You can prevent updates to individual items by ...