I strongly believe that there is a coding issue in 3.3 which is really behind this. It could be that it affects certain providers. Hence, it worked for gregpxc and not for you or me.
All I can say is that version 3.2.1 worked fine and that only 3.3 caused the problems we are both experiencing. I am not going to switch off my plugins as that would cause havoc on my site. I think the plugins thing is a red herring and that it is down to the code.
I plan (over Christmas) to set up a testing version by setting up a subdomain on my site and then mirroring the existing site and database to this testing site and playing with it. That way, I can try out the plugins switch off and see if that makes a difference without it affecting my working site.
If you want to do the same (unless you feel comfortable, don't):
- Via MySQL/cPanel copy into a txt file your current site's database
- Create a new subdomain or if you can't set up a subdomain, try creating a new folder in your current site. Give it a distinct name (like "blobby", or something).
- Copy all files (including hidden .htaccess file) to the location of the new subdomain/folder
- Create a new empty database
- In a text editor, global search & replace all instances of "http://www.name-of-your-site.com" to whatever the new address will be (e.g. "http://blobby.name-of-your-site.com" if sudomain or "http://www.name-of-your-site.com/blobby/" if folder. Leave email address as before).
- Upload/import changed database tables txt file directly to new database
- Change the database details in wp-config.php file in your new site to point to your new database
- When you enter the new site address, the mirrored copy of your site will appear as if already installed.
- Protect the site from others by installing a maintenance mode plugin
Keep this site (protected) and try out all changes before you implement them on your "live" site. That way, you won't have any nasty surprises in the future.