You're welcome. Thanks for confirming that it was the database upgrade issue, as I suspected. This bug has been fixed but users with prefixes who have already upgraded will have to take the manual step you did.