Ah okay! Thanks for the information. :) I'll post a reply here when we've found that bug. >:)
This has (most likely) now been fixed. Thanks again for reporting this issue. :)
