The custom image plugin for the fullscreen rich text editor in the Touch UI is no longer necessary for AEM 6.3. In AEM 6.3 you can drag and drop an image from the lefthand authoring sidebar onto a RTE in inline editing mode (not fullscreen). Once you have the image inside the RTE, you can then swi...
Hi Ashish, these are great questions.Agreed that there is not currently a prompt to publish the root page when you change a shared/global property and then activate a page on the site. Something like this might be a great enhancement to the feature in ACS Commons (which is open source). Being the ...
You can deploy rep:policy nodes from your code package - we do it all the time. You can also see how to do this in GitHub - Adobe-Consulting-Services/acs-aem-commons where they create a handful of service users and deploy their associated ACLs.
NVM, I think I answered this for myself - looks like it works if I grant my service user the following permissions: rep:userManagement,jcr:modifyAccessControl,jcr:readAccessControl
@smacdonald2008 - I found https://helpx.adobe.com/experience-manager/using/jackrabbit-users.html which talks about creating users/groups via the Jackrabbit API, but both that example and your example here use the frowned upon getAdministrativeResourceResolver() method. Is there a set of permissions...
Ok, sounds good, thanks for looking into it!A doc bug in that it is actually deprecated but docs are not showing that it is? If so, is there any info on what superclass the code should be migrated to?orA doc bug in that it is saying it is deprecated when it really is not?
I get this warning when building my project.[WARNING] Component <insert class name here> is using the deprecated inheritance feature and inherits from com.day.cq.dam.commons.process.AbstractAssetWorkflowProcess. This feature will be removed in future versions.Looking at https://docs.adobe.com/docs/e...