inteligr8/alfresco-community-repo
1
0
Fork 0
mirror of https://github.com/Alfresco/alfresco-community-repo.git synced 2025-08-14 17:58:59 +00:00
Code Issues Packages Projects Releases Wiki Activity

MNT-16200: updated share-config-custom.xml comments for aspect and type i18n config

Browse Source 
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/PATCHES/5.1.1/root@125735 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
This commit is contained in:
Martin Bergljung
2016-04-25 10:00:03 +00:00
parent 44330a12be
commit 041e25924e
1 changed files with 30 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

39
src/main/resources/bitrock/bitrock/alfresco/shared/web-extension/share-config-custom.xml
View File

@@ -126,10 +126,20 @@
</tree>
<!--
Used by the "Manage Aspects" action
Used by "Manage Rules" -> "Add aspect" action.
For custom aspects, remember to also add the relevant i18n string(s)
cm_myaspect=My Aspect
If an aspect has been specified without a title element in the content model,
or you need to support multiple languages,
then an i18n file is needed on the Repo AMP/JAR extension side for the aspect to
be visible when creating rules:
custom_customModel.aspect.custom_myaspect.title=My Aspect
Used by the "Manage Aspects" action.
For the aspect to have a localised label add relevant i18n string(s) in a Share AMP/JAR extension:
aspect.custom_myaspect=My Aspect
-->
<aspects>
<!-- Aspects that a user can see -->
@@ -164,15 +174,26 @@
</aspects>
<!--
Used by the "Change Type" action
Used by "Manage Rules" -> "Specialise type" action.
If a type has been specified without a title element in the content model,
or you need to support multiple languages,
then an i18n file is needed on the Repo AMP/JAR extension side for the type to
be visible when creating rules:
custom_customModel.type.custom_mytype.title=My SubType
Used by the "Change Type" action.
For the type to have a localised label add relevant i18n string(s) in a Share AMP/JAR extension:
type.custom_mytype=My SubType
Define valid subtypes using the following example:
<type name="cm:content">
<subtype name="cm:mysubtype" />
</type>
Remember to also add the relevant i18n string(s):
cm_mysubtype=My SubType
<type name="cm:content">
<subtype name="custom:mytype" />
</type>
-->
<types>
<type name="cm:content">