I am facing an issue with the custom icon library for our project. Issue is that the custom icons are not visible in the touchUI dialog but on selecting it will come on page.
Similar issue is faced by others which i found but were not helpful:
I am using :
path="/etc/acs-commons/lists/font-awesome-icons"/> (Here Instead of acs-commons path, I have given the path where my project icons are stored)
I found a solution for this:
Kept icons in a separate client library folder and added it as a dependency in the acs-commons touchUI clientlibs ( /apps/acs-commons/touchui-widgets ).
Its working fine as expected.
But the problem here is that i feel this is not right to do modifications under acs-commons directly.
So if there is any other way to display the icons in the dialog then it would be helpful.
I am working on AEM6.4
This looks like a ACS-COmmons issue. I would proceed as you have stated to make this fix.
Please let us know whevever this is fixed.
I would log a bug against this part of AEM and in mean time - you can use the workaround you found.
I found a better solution for this in which there is no need to modify acs-commons.
We're using AEM 6.4 SP3 and experiencing the same issue.
Could you provide more detailed info on how to fix it?
Which dialog have you added extraClientlibs?
Have you make any changes to the widget wrapper?
Sorry i dont have the dialog code as of now but let me explain you in a better way. You have written some custom css for the custom icons right so this css files you can put in a clientLibrary folder and give it a category for this clientlib folder. Now you will have to load your custom css in the touchUi dialog (the dialog where you want to see your custom icons). So using extraClientlibs property in the dialog you can include your clientlib folder category. (extraClientlibs: ["category1","category2"]).
No changes to the widget wrapper.
Its like the TouchUi dialog is not able to load your custom css and will show square boxes sometimes instead of your custom icons or sometimes nothing will be displayed. So you have to make sure the dialog should have access to your custom css for which we are using the extraClientlibs property. extraClientlibs property will load your css for your touchUi dialog and not for your AEM webpage.