Quote:
Also, I didn't at all HAVE this problem until after upgrading to 2.3.0, so I would jump to the conclusion it's a VB thing before I'd say it's a host problem.
|
as there are a lot of users using vb230 without this, it's surely not a vb problem.
But if it's really not your host, maybe you have made a big mistake while upgrading?
Maybe you should restart the upgradeprocedure from the ground up.