The issue (the one reported in the last post) has been fixed.