You ran into this bug that is currently in 3.11.2, it is hitting LOTS of people upgrading to 3.11 right now.
We are waiting on a 3.11.3 or 3.11.4 to get the fix included, but apparently there is some sort of problem with that release.
You ran into this bug that is currently in 3.11.2, it is hitting LOTS of people upgrading to 3.11 right now.
We are waiting on a 3.11.3 or 3.11.4 to get the fix included, but apparently there is some sort of problem with that release.