I don't have access to CQ 5.4 instance so I can not check it my self but I am sure there should be some OSGI configuration for enabling the audit logger as pointed by the below pages. http://stackoverflow.com/questions/34398028/node-folder-deletion-history-adobe-aem-cqhttp://cq-ops.tumblr.com/post/3...

You can get the resource bundle without the request object by calling the Sling ResourceBundleProvider API. //Get the reference of bundle provider to get the resource bundle. @Reference(target="(component.name=org.apache.sling.i18n.impl.JcrResourceBundleProvider)") private ResourceBundleProvider res...

-If you install the content packages on the fresh 6.1 instance then the you will lose the version history data as version history is not moved when you install content package on 6.1.  -When you do in place upgrade then the upgrade utility also migrates the existing nodes in the repository if there ...

Thanks for the detailed explanation. I didn't know that you were using sightly to include the components. Please refer the following thread which has solution to this problem - http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manager.topic.html/forum__7wh...

Apologies for the wrong code snippet. You can follow this KB article for the correct API - https://helpx.adobe.com/experience-manager/kb/ComponentDiv.html.  This should fix the problem-<%@ page session="false" import="com.day.cq.wcm.api.WCMMode, com.day.cq.wcm.api.components.IncludeOptions" %> if (W...

Reference documentation - https://docs.adobe.com/docs/en/cq/5-5/javadoc/com/adobe/granite/security/user/servlets/AuthorizableSearchServlet.html

Try with the following servlet - http://localhost:4502/libs/granite/security/search/authorizables.json?query={%22condition%22:[{%22eq%22:{%22property%22:%22profile/@email%22,%22value%22:%22willard.ebbing@geometrixx-media.com%22}}]}. The URL which you are trying does not search for email property but...

I don't know your use case but you can customize the update asset workflow and add a custom process step at the end instead of triggering a new workflow via a launcher. 

You can remove this divs by adding the following lines of code in global.jsp file- (WCMMode.fromRequest(request) != WCMMode.EDIT && WCMMode.fromRequest(request) != WCMMode.DESIGN) { IncludeOptions.getOptions(request, true).forceSameContext(Boolean.TRUE); }

Refer the solution in the following thread- http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manager.topic.html/forum__7whj-i_am_using_sightlyf.html