This is a bug. It has been reported in trac and will hopefully be fixed with the release of WordPress 3.1 soon. If you really want to dive into it, you could apply the patch that is with the ticket.
This is a bug. It has been reported in trac and will hopefully be fixed with the release of WordPress 3.1 soon. If you really want to dive into it, you could apply the patch that is with the ticket.