Comment 1 for bug 1209232

I recently upgraded my instances of Plone to version to 4.3.2, and one of my users just reported this same problem. I'm wondering, then, if anyone has had a chance to take a look at this problem. If it's helpful, I can offer that applying the same page I originally mentioned to this latest version of Plone addresses the problem. Thanks.