I think this must be a deployment related issue. The 3.3.0-x branch is quite stable and we aren’t seeing widespread reports of this issue; I can’t reproduce it locally. I’m not sure what guidance to give you beyond what’s on the other thread.
Regards,
Alec Smecher
Public Knowledge Project Team