We have a requirement where the requirement is like - under the location /content/dam/site, user should not be able to create the folders, however they user should be able to create assets.Under the /useradmin console if we uncheck the create checkbox for /content/dam/site then they will not be able...

We found that our element was getting loaded after the java script loaded and that is why it was not working.  So instead of binding the event on the element like $(".my_button_class").click(function() {...we had to do like -$(document).on('click',"my_button_class", function()) {...and this has fixe...

We have a new button in the global nav which has a class assigned using granite:rel. We have a Client Library javascript code which listens to the click event for that button and calls the our javascript. In our javscript ClientLib, we have assigned the categories as - dam.gui.coral.metadataeditor,g...

My co-worker came up with an idea to overlay the /libs/granite/ui/components/shell/clientlibs/shell/js/omnisearch.js  and customized this javascript file for adjusting pathPredicate.value line 616. This has worked for us.

Were you able to find the fix for it? I am also having the similar requirement.

Thank you but the above option let us customize the "Assets Admin Search Rail". However my requirement is that in the top search panel itself, either I by default prefix the path predicate along with the "Location: Assets" or internally search only under the location - /content/dam/myrealcontents in...

We have a requirement where our main contents are under - /content/dam/<site> and we have big chunk of assets on /content/dam/archive folder.We are trying to figure out how we can customize the default behavior of the search so that it always checks under /content/dam/<site> and fetch results. Our u...

Overlay solution did not work because the configuration are under /config folder in aem 6.3. If it was under /app or /etc then we could have used overlay.We created a separate clientLib with the categories as - categories="[dam.gui.coral.metadataeditor,granite.ui.coral.foundation]"/> and added our c...

We are trying to implement custom meta along with some OOTB meta data. Our issue is that the last tab always comes up with the "Insights" tab which our product team does not want. It is coming OOTB but wondering if there is a way for us to hide it. We try looking at the - /libs/granite/ui/components...

Thank you very much. It seems to have worked .  I did not have to do the #2 updates for Adobe Granite CSRF Filter as OOTB it was allowed (may be it is the case in AEM 6.2).