I understand this bug has been around since at least 11/12/2009 identified as Bug 14055. does anyone know if it has ever been resolved (in the last six years)?
I have a client on SL2015 CU1 that still has this problem.
I understand this bug has been around since at least 11/12/2009 identified as Bug 14055. does anyone know if it has ever been resolved (in the last six years)?
I have a client on SL2015 CU1 that still has this problem.