Thanks for replying so quickly! ??
We’re running a sub-domain install. We were getting the error when our main install was running on https://www.example.com (which we achieved through an htaccess/mysql hack).
As a workaround we’ve setup example.com as a network and moved our other sub domain sites to that network.
We’ve then added an htaccess rule to rewrite traffic from https://example.com to https://www.example.com.
A bit confusing, but at the end of it we have a multiple network WordPress, with multiple sub domain sites all working exactly as we want it to. ??
Thanks
Stating obvious, but for clarities-sake example.com is not the real domain name ??