Thanks for reporting this. And sorry for the trouble. I’ve just released version 188.8.131.52 which should fix the issue. I say should because I wasn’t able to replicate the error easily, but wanted to roll out a fix as quickly as possible. I have an idea of what caused it – accessing the site frontend before accessing the MT interface after upgrading. I have implemented some code that should avoid the error based on that scenario, and a few others. But please could you confirm that the error goes away after upgrading to 184.108.40.206 so I know for certain?