The following section defines some problems and provides answers to frequently asked questions in AEM.
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, you must 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 call were made. Subsequently, you can trace the error handling function and change the error message as per your requirement.
Content-Authors need to have the permissions on /content/projects for using the create language copy feature.
If one requires the authors to manage projects as well, then the workaround is to add the author to project-administrators group.
You need to create a language root and language copy inside the root, before creating a translation project.
Create a language root inside /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 so they can be audited at a later time. By default, the entries will be written to the error.log file. To make monitoring easier, it is recommended that they be redirected to a separate log file.
To learn about redirecting 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.
For more information on how to enable SSL by default, please refer to SSL by Default.
Why the Assets workflow repeats itself while uploading mp4 files (for instance, 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.
Installing Feature Pack 14410 provides new capabilites for Dynamic Media with a new architecture. Installing Feature Pack 18912 is optional - you only need this Feature Pack if you want to migrate Dynamic Media Classic assets and/or use FTP to bulk upload assets.
If you use Adobe Experience Manager set up for different environments, such as one for development, one for staging, and one for live production, you need to configure Dynamic Media Cloud Services for each one of those environments.
To learn in detail on how to install feature pack and configuring Dynamic Media Cloud Services, see
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, please refer to 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.