Forums
(@omallee)
12 years ago
The issue appears to be still unresolved; what a shame; I am not 100% certain but I think it only came up after WP3.5.1