AEM 6.1 Touch UI Component Inplace editing

Make sure you have editorType="text" or editorType="textImage" property added to the inlineEditing node.
Refer to xml below:
<jcr:root xmlns:cq="http://www.day.com/jcr/cq/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0" xmlns:nt="http://www.jcp.org/jcr/nt/1.0"
    cq:actions="[text:Text/Image,-,EDIT,DELETE]"
    cq:dialogMode="floating"
    cq:layout="editbar"
    jcr:primaryType="cq:EditConfig">
    <cq:inplaceEditing
        jcr:primaryType="cq:InplaceEditingConfig"
        active="{Boolean}true"
        editorType="text">
        <config jcr:primaryType="nt:unstructured">
            <rtePlugins jcr:primaryType="nt:unstructured">
                <subsuperscript
                    jcr:primaryType="nt:unstructured"
                    features="*"/>
            </rtePlugins>
        </config>
    </cq:inplaceEditing>
</jcr:root>

Comments

Post a Comment

Popular posts from this blog

AEM 6.3 Migration -osgi bundle whitelist error-osgi-service is NOT whitelisted to use SlingRepository.loginAdministrative

Are you facing such errors while migrating to AEM 6.3 : osgi bundle whitelist error-osgi-service is NOT whitelisted to use SlingRepository.loginAdministrative Here is a quick hack but please ensure not to use it in production I believe most of the AEM developers are aware that ResourceResolverFactory.getAdministrativeResourceResolver   and   SlingRepository.loginAdministrative   methods have been defined to provide access to the resource tree and JCR Repository .  Consequently the following methods are being deprecated  ResourceResolverFactory.getAdministrativeResourceResolver ResourceProviderFactory.getAdministrativeResourceProvider SlingRepository.loginAdministrative and alternatively we started using service authentication method  getServiceResourceResolver to get the resourceResolver and then making a systme user and mapping service with user in felix congigurations. like this  < service - name > [: < subservice - name > ]= < authorizable id of
Read more

CQ/AEM Quick Bits

Image
OSGI 1. Bundles = jar files + Manifest 2. Components = java classes 3. Services = special components used to interact between bundles 4. OSGi is a container in which any bundle can be added at runtime 5. Bundle jar files are dropped in folders called install to add them to CQ Annotations: To add properties @Properties({ @Property(name = "scheduler.expression", value = "*/5 * * * * ?") ,// Every 5 seconds @Property(name = "scheduler.expression.meta", options={ @PropertyOption(name="prop1", value="Option 1"), @PropertyOption(name="prop2", value="Option 2") }), To read properties: componentContext.getProperties().get(“prop-name”).getString(); Sling 1. URL Decomposition – get the contentPath, method and selectors from the URL 2. Content Resolution – identify the content and access the sling:resourceType Property 3. Resource Resolution - /apps or /libs 4. Script Resoluti
Read more