New subdomain does not establish database connection

I’ll do that. I’m supposed to be able to create unlimited DB, thought, so if they put a limit on the tables, I shall be annoyed, to say the least. Thanks for all your help, I know this is frustrating!

If the collation and character set in cpanel has changed, and is different than the db itself and what’s declared in the wp-config, then that can screw it up too.

Sorry it took so long to get back! hopefully you are still in helping mode!

ipstenu: I have unlimited tables

Andrea_r: there doesn’t seem to be a problem with the collation setting.

No super admin is able to create new sub-domains, my host claims the connection from the main site (www.provocate.org) to the DB is fine, and we have not made any unusual changes to the site itself.

yesterday another problem cropped up – one super admin, not myself, was not able to add posts correctly. When they where published only the titles showed up, but not text. He created a new super admin account and the problem was fixed. This may be unrelated, but I thought with all the little problems we seem to be having, might there be a bug on the WP side that could be causing all of our problems?

really out of my depth here haha. Any help is appreciated!

Issues are considered bugs when other people can reproduce them on other servers. ?? If not, then it’s your setup.

I’ve been testing all kinds of stuff – it’s not WP out of the box.

Standard troubleshooting: disable every single plugin you have, even ones in the mu-plugins folder. By disable, I mean rename the plugins folder. that turns everything off for everyone at once. And revert to the default theme.

THEN see if you can replicate the issues.

and we have not made any unusual changes to the site itself.

What about seemingly insignificant changes? ?? I notice you have more than one super admin – any particular reason? Usually these are limited. Sometimes, in these kinds of situations, people changes things and other people don’t notice. ??

I feel pretty silly about not disabling ALL of the plugins before, instead of just the ones we have recently added, but that did the trick! Now we are just in the process of figuring out which particular plugin is the culprit.

Thanks so much!