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/coral/foundation/tabs which is responsible for rendering the tabs but dont see anything there.
Does anyone know if it is possible to remove/customize the "Insights" table? We are using AEM 6.3.
Thanks,
Solved! Go to Solution.
Views
Replies
Total Likes
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 custom javascript which will loop through and hide the insights tab something like -
$( document ).ready(function() {
var dataElements = document.querySelectorAll('[data-foundation-tracking-event]');
for(var i=0; i < dataElements.length; i++) {
if(dataElements[i].textContent == 'Insights') {
dataElements[i].style.display = 'none';
}
}
});
As this is not documented - we asked the team to look here.
The Insights form exist at location [0]. Try overlay the form using [1] and hide. If it doesn't work then log a hotfix request to get fix from Product.
Thanks
[0] /libs/dam/content/schemaeditors/forms/insights
[1]Apache Sling :: Resource Merger (org.apache.sling.resourcemerger)
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 custom javascript which will loop through and hide the insights tab something like -
$( document ).ready(function() {
var dataElements = document.querySelectorAll('[data-foundation-tracking-event]');
for(var i=0; i < dataElements.length; i++) {
if(dataElements[i].textContent == 'Insights') {
dataElements[i].style.display = 'none';
}
}
});
Then I would consider this as a product bug and overlay extension should work.
The form under /libs goes to /conf when extended at the project level (Administrator role).
All customizations needed at a project level for OOTB forms /libs go to /apps. (Solution Integrator role)
Say at the project level, it is decided to hide Insight Tab so that any user admin can't see when metadata schema is being defined under /conf for the project. Then OOTB form offered from location /libs should be extensible through /apps overlay and further User Administrators can define project level forms under /conf using the merged resource form (/libs + /apps).
The JS approach works but not elegant as Project administrator can still see Insights under /conf structure.