Binary-less distribution is supported for deployments over a shared data store and involves agents that leverage the Vault-based Distribution package exporter (factory PID: org.apache.sling.distribution.serialization.impl.vlt.VaultDistributionPackageBuilderFactory) package builder.
With binary-less mode enabled, the content packages distributed contain references to binaries rather than the actual binaries.
To enable binary-less distribution, deploy with a shared blob store.
Check the useBinaryReferences property in the OSGI configuration with the factory PID (org.apache.sling.distribution.serialization.impl.vlt.VaultDistributionPackageBuilderFactory) that your agent is using.
Check the Network panel (of Chrome browser) where a personal setup (JS has not been minified).
View the Initiator column to determine what the initiator of a request was. It provides the files and the line numbers from where the AJAX calls are made. Later, you can trace the error handling function and change the error message as per your requirement.
To create language copy feature, content-authors need permissions at /content/projects location.
If one requires the authors to manage projects as well, then the workaround is to add the author to project-administrators group.
Create a language root and language copy inside the root, before creating a translation project.
Create a language root at /content/geometrixx with name as fr_LU (and title as French (Luxembourg)). Subsequently, create language copy of page from the references panel and navigate to Create structure only option in Create & Translate. Finally, create a translation project and then add the language copy to the translation job.
For details, refer to the additional resources below:
AEM has introduced the ability to log administrative changes for better troubleshooting and audit. By default, the information is logged in the error.log file. To make monitoring easier, it is recommended that they be redirected to a separate log file.
To redirect the output to a separate log file, see How to audit user management operations in AEM.
Adobe Experience Manager (AEM) 6.4 ships with the SSL wizard and offers a User Interface to configure Jetty and Granite Jetty SSL support.
To enable SSL by default, see SSL by default.
What is the recommended architecture when using AEM’s Content Services from a mobile app, ideally React Native?
The Content Services are based on the Sling Models and the AEM developers must provide a Sling Model pojo for each component that is exported.
To understand how to consume AEM content services from a React application, see Get Started with AEM Content Services tutorial.
Also, if the developers want to export a tree of components they can also implement the ComponentExporter and ContainerExporter interfaces as well as use the ModelFactory to iterate over the child components and return their model representation. See the resources below:
You can opt into usage statistics collection by using either the Touch UI or the Web Console. For detailed instructions, see Opting into aggregated usage statistics collection.
Why the Assets workflow repeats itself while uploading MP4 files (for example, using drag-and-drop method)?
If the user, uploading the movie files does not have delete permissions under asset node, the delete chunk nodes fail and the upload restarts.
Adobe Experience Manager (AEM) 6.4 currently lets you upload up to 2 GB of assets at a time.
For additional information on maximum number of assets that can be operated with AEM 6.4, see Assets sizing guide.
When creating language copies through classic UI, Assets are not moved under the new language hierarchy but used from the language master.
Whereas, when you create a language copy through Touch UI (References -> Update Language Copy), a new DAM folder is created under the new language and assets are referenced from there.
This is default setting for OOTB configurations. You can set Translate Page Assets = Do not translate in Translation configurations.
For AEM 6.4, Tools > Cloud Services > Translation Cloud services.
You can disable the OSGi Component Disabler. To use this service, see OSGi Component Disabler.
As a workaround, you can also manually disable the component either via the UI or via a curl command (example below), after every AEM restart.
curl -u admin:$(pass CQ_Admin) 'http://localhost:4502/system/console/components/com.day.cq.analytics.sitecatalyst.impl.importer.ReportImporter' --data 'action=disable'