Yep. Database error. Fixed now. Apologies for any misinformation that resulted - we had to manually change some things in the spreadsheet and it had ripple effects. Everything should be working correctly now, but... well... don't put any money on it.