Just to let you know that with your metadata.db file I can recreate the issue.
I will now see if I can identify exactly what is triggering the issue so that I can give you a short term workaround, and also whether the problem has already been fixed for the 3.2 release I am working on (and fix it if not)
|