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 ...
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, ...
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 ...
From my point of view, the answer is yes, you can update the Sitecore Base template or add the template as base.
When upgrading the Sitecore instance, this may impact those templates. You may need to re-add those base templates to the standard field template. You'll need to keep track of the items so that if you are upgrading the Sitecore instance, you'll ...
Why does Standard Values inheritance break?
Inheritance of Standard Values works until the field does not change on the item itself. So if you have filled the Standard Values in Final Renderings field the inheriting stops when the created item Final Layout changes (adding/removing/changing renderings to the page).
What you could do better?
In short, fill ...
Sitecore items inherit security settings by default. An item can inherit the access rights that have been specified for other items that are higher up the content tree. Any item can be configured to inherit the security settings of its parent item.
Sitecore allows you to configure which items should inherit security settings and which should not. The ...
You need to navigate to your new template "Promo1" and for each template field change Title field to your desired value like depicted below:
I am using Promo as example here so change path to your cloned template.
to verify this scenario and root cause, can you please do this activity.
Change the field name and display name of both the fields just for testing purpose, You can add an abbreviation like Filed A and Field B.
Search those field under inheritance section
Let me know if you are not able to find these fields there
So if you want to match exactly your template inheritance, then your SpecificProduct should derive from BaseProduct as you have it already.
There are a couple of principles you should follow here tho:
YAGNI - do you need to do that now? No, then don't worry about it, move on to the next problem. Worry about that when you need to and you can refactor then.
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 ...