Errors after creation of new site

Just to clarify: this is an existing WP multisite network, and you have created other subsites before, and now it is not working?

When you created the site, did you remember to put in something in the new site url box? I’m asking because the dashboard is trying to link to “https://wp-admin/”, instead of “https:/{what you might have entered}/wp-admin/”.

Have you tried to create another subsite? Do you get the same error?

Hi Bet,

thanks for your Feedback.
Absolutely: the Multisite already exist and I already created other subsites. But I have to add here, that I needed just exact clones until now, so I used the Plugin “Cloner” to clone the sites. That always worked perfect.

This time I need a clean new site. And of course I entered somethin in the URL box ?? I also tried it with entering the http/https in the field, that led to an – expected – error, that the URL is wrong.
Without http/https – as it should be – the new site gets created but I get the errors I stated in the first post.

Interrestingly, the site does not show in the menu at all. So something is going wrong at the creation somewhere ;).

I uploaded a few screenshots for clarification (attention: screenshots in German, as I use WP in German ;).

creation of new site
Error calling the new Site
Error trying to call the Dashboard of the new Site
And the new Site is not visible in the menu

Thanks in advance for any ideas ??

In wordpress setting > General

What url is used in WordPress Address (URL)and Site URL

Hi bugke,

in WordPress Settings –> General are no fields for WordPress Address and SiteURL.
As far as I’m informed these fields are only there when using single-Site, not with MultiSite/Wordpress Network Sites as the URLs are managed over the “Websites” tab in the Network Dashboard.

@all: if it is of any interrest, here is the config part for Multisite in my config.php

define(‘WP_ALLOW_MULTISITE’, true);
define(‘MULTISITE’, true);
define(‘SUBDOMAIN_INSTALL’, true);
define(‘DOMAIN_CURRENT_SITE’, ‘matthaeus-augsburg.de’);

I see in one of the screenshots that you have other subsites in this network. Were you able to create them in the normal way? If so, what has changed in your network since you were able to create them? For instance, have you added new plugins or themes?

Is there a limit for the database tables on your server? Some web hosting providers have weird restrictions.

@bet: thats what I mentioned earlier in this thread: for the other sites in the network I use a Cloner-Plugin. Creating new Sites with that tool works fine, but it only clones Sites. This time I need a new/clean Site, so I’m not using Cloner.
But I’m going to deactivate all plugins (including the cloner) and try to create the Site again. Maybe with more luck this time ??

@toscho: that is luckily not the problem, as I’m the hoster myself (root server, no restrictions in MySQL ;)).

KlyX

Okay, I tested that…
Without the plugins I can create the site and access the site as well as the dashboard.
Site is completely white… but as there is no activated theme etc. that might be possible.
Site is not shown in the network dashboard… Going to try a few things to get the site running… Wish me luck ??

@toscho: the number of database table shouldn’t matter, since multisite uses one database for the entire network.

@klyx: glad you were able to create a site! I wonder if it was the cloning plugin that was somehow blocking access to creating the new site?

Theoretically, your new site should use one of the WP default themes by default. Do you not have one of the WordPress “Twenty-something” themes installed in your network? You will want to leave one of those Twenty-something themes in your network so that you can use it for error testing.

Shared are only user and network management tables. All the others (posts, terms, options, meta) are created separately for each site.

@toscho: default multisite uses one database. Maybe you have something custom set up.

@bet: I guess I did uninstall it ?? Will reinstall the 2016 theme again I guess ??
Wasn’t able to test everything out yet.