This is fixed. Quick response, because it was a major update day (back end stuff primarily), which means fire fighting any issues that made it through was a priority. 🙂
Cookies help us deliver our Services. By using our Services or clicking I agree, you agree to our use of cookies. Learn More.