I tried it and it's the same fatal error as I described before. But since the 1.2.5 I didn't encounter this
