If whatever you read in that thread doesn’t help you are on your own.
As pointed out there, CS6 and El Capitan is an unsupported configuration. CS6 has reached end of life and will not be updated.
As mentioned: We're planning to update ~100 InDesign CS6 to CC 2015 in February.. Just looking for a small tweak to fix it for 1.5 months on 6 new MacMinis.
Thanks for your post BobLevine, but we know this of course :-)
I don’t recall if I mentioned it in that thread, but have you tried putting the fonts into the fonts folder in the InDesign application folder?
You might also want to consider upgrading those fonts to OpenType. Type 1 fonts have been wonky on both Mac and Windows for ages.
We're using the server version of FontExplorer and the fonts are temporary downloaded onto each user's Mac and stored in "/Users/Shared/.FontExplorer X Server/.....". (as I checked with the root-user)
Apple changed important things in El Capitan (security reasons) so InDesign (CS6) can't get access to the temporary downloaded fonts.
I'm installing CC 2015 at the moment on a new MacMini to test if it's working like it should - if so we should think about ignoring the problem till February.
If some users really need to use a PostScript font we can try to get the OpenType - if necessary .
I personally hate PostScript fonts but there a some we have used over years.. :-)
The problem is that we can't update every InDesign to CC 2015 at the moment ... many other things have to be done network-sides before we can start ... and of course we don't want to mix up CS6 / CC2015.
I'm not using El Capitan in production, but I'm not having any problems with PS fonts and Font Agent Pro 6.5 on my test 10.11 system. FAP loads them with ID 2015 and I can manually load PS fonts via my font folders, so maybe it's a FontExplorer problem?
There is no problem with InDesign CC 2015 - it's a problem with CS6.
The problem with FontExplorer (standalone) / ID CS6 / El Capitan was resolved in the posted thread, but we're using - as mentioned - a FontExplorer Server.. :-)
Anyways.. I don't think that there is any tweak for this specified problem - I think we will try to avoid the problem for 1.5 months.