Troubleshooting in AEM with real time use cases

In this blog, I will talk about some of the real-time issues, I faced while working on a project. Here we will talk about the problem statement and how to tackle these problems.

1. The multiple PDFs were not able to move to a specific location: In AEM, ideally, you can select multiple PDF’s and move to a specific location. While working on a project in AEM 6.5.2, The authors in this project were able to move a PDF to a certain location but they were not able to move multiple PDFs in one go.

When I found the issue, I checked the console and realized that the OOTB JS
(/libs/dam/gui/coral/components/admin/moveassetwizard/clientlibs.js) is breaking.

I raised this as a Product Bug to Day Care and below is the solution which they provide me. “This is an issue with 6.5.1 and 6.5.2 which should be fixed in 6.5.3 release”.

Workaround:
The present workaround is to replace line 251 at
/libs/dam/gui/coral/components/admin/moveassetwizard/clientlibs/js/wizard.js
with the below code.

Old code snippet:
var newName = $(".rename-item-name").val().toLowerCase();

New code Snippet:
var newName = $(".rename-item-name").val();

you can create an overlay for the above mentioned JS file and later uninstall it when you plan to install 6.5.3.

2. While using reference components, the authors are not able to decide which component they need to refer in the path browser.
There is a real-time scenario where we need to use the same component in several pages and for that particular use, the case reference component is very helpful.

Let's suppose we are having some tables which are being shown on many pages. Now suppose the author created a page "P" to put all the tables and try to reference the tables in actual pages from that centralised page.

Now as the page "P" is having so many table components, so while using reference
components to point to a specific table, it is difficult to identify by the content-authors which table they need to point because, in the path browser, the component node name is being shown.

Fig1: Reference Component dialog for choosing a table component

While debugging out the pathbrowser behavior, I figured out that in
“/libs/granite/ui/components/foundation/form/pathbrowser/render.jsp”, line No 42,
the pathbrowser shows the “jcr:title” of the resource value and if not available then shows
resource name.

Fig2: PathBrowser component render.jsp logic

So to solve this issue; We can provide a title field with name property “jcr;title”
in the table component so that if the authors can provide a “title” to the table to define what this
the table is about, then in the pathbrowser, the title will be visible and authors are able to
point to the correct component while using the reference component.

You can do it for all the components by making a generic tab, so that whenever authors
face this issue, they can immediately provide a “jcr:title” to the component.

Fig3: After providing jcr:title the view in pathbrowser in reference component

3. While login via a user which is part of "content-authrs" group, the “Modified By”
for Asset is visible as “External User” but not as the actual person name:
Usually, to set up content-authors permission for a specific project, we take reference
from OOTB content-authors and then add more permissions based on the additional
hierarchies for the specific project.

But there can be some permissions which AEM OOTB content-authors don’t have but you need to provide them.For the assets, content authors are not able to see who modified the image last, but can
see “External User” as ” Modified By” for all the images.


Fig4: The "Modified By" as "Extenal User" while logging from content-authors

Solution: I go through the code and found out that the column preview ‘s HTML is
getting rendered from here:
/libs/dam/gui/coral/components/admin/contentrenderer/column/columnpreview/columnpreview.jsp

Fig5: The logic from where modified by is visible in Assets columnnview

So basically to fetch the value of "Modified by" the code is trying to get the formatted Name which can only be accessed when the author has "/home/users" permission.

To solve this issue, you need to give read permission to “/home/users” hierarchy to content-authors and it will start showing the actual user who modified the assets last.

Fig6: After fixing the permission, the "Modified By" is showing "Actual User"