Reputation: 1
We are trying to customize the user editor console provided out of the box from AEM (AEM 6.0 SP3, Touch UI). However our changes are not reflected.
Expected: The new fields provided (see provided code segtment below) are shown, merged via the resource merger into the out of the box fields.
Actual: The new fields are not shown.
The overlay xml segment (userdetails) is found below (/apps/granite/security/content/userEditor/.content.xml):
<userdetails
jcr:primaryType="nt:unstructured"
sling:resourceType="granite/ui/components/foundation/container"
class="well user-details-sections-margin">
<items jcr:primaryType="nt:unstructured">
<extendedInfoContainer
jcr:primaryType="nt:unstructured"
sling:resourceType="granite/ui/components/foundation/container"
class="extended-container">
<items jcr:primaryType="nt:unstructured">
<linkedin
jcr:primaryType="nt:unstructured"
sling:resourceType="granite/ui/components/foundation/form/textfield"
class="save-button-enabler"
fieldLabel="LinkedIn"
name="./profile/linkedin"
value=""/>
<twitter
jcr:primaryType="nt:unstructured"
sling:resourceType="granite/ui/components/foundation/form/textfield"
class="save-button-enabler"
fieldLabel="Twitter"
name="./profile/twitter"
value=""/>
<xing
jcr:primaryType="nt:unstructured"
sling:resourceType="granite/ui/components/foundation/form/textfield"
class="save-button-enabler"
fieldLabel="xing"
name="./profile/xing"
value=""/>
<photo
jcr:primaryType="nt:unstructured"
sling:resourceType="granite/ui/components/foundation/form/pathbrowser"
rootPath="/content/dam/arvato"
class="save-button-enabler"
fieldLabel="Profile photo"
name="./profile/photo"
value=""/>
</items>
</extendedInfoContainer>
</items>
</userdetails>
We followed the instructions found in : https://docs.adobe.com/docs/en/aem/6-0/develop/extending/customizing-consoles-touch.html
The same approach has worked fine in different projects, using AEM 6.2.
Upvotes: 0
Views: 696
Reputation: 10241
why are you spending time in building a console which will be used only by admins? Its not a feature used by end users or your content authors. There is no point in building a fancy console. I am pretty sure newer versions of AEM will have a better console OOTB. AEM 6.3 already has a touch ui user admin console. AEM will retire classic UI consoles completely by 6.4. I would recommend just wait for Adobe upgrades especially because there is not much use of this console.
Upvotes: 0