Alex Phelps

Yes, I’m proposing to disable using Port 443 if you dont absolutely need and given you have SSL certificate issues.

To disable it, you’ll probably want to replace Port 443 with Port 80 which is the default port most people use.

To enable / disable the site running on port 443 (ssl) it should be server configuration for the domain the site is on and probably wouldnt affect other things on the server.

Here is an example for Nginx – https://rtcamp.com/wordpress-nginx/tutorials/ssl/thawte/

Hope this helps.

Is it the first site on the list? If so, it doesn’t have the delete option because the site is the “Network Home” which cannot be deleted.

Can you check in the site’s General Settings? /wp-admin/options-general.php

Or you can check in the Network Settings /wp-admin/network/settings.php

If neither one of these work I think the title must be in the Theme your using or in a Plugin.

I dont think this is an issue in WP itself. We have a development environment that has this same issue but can easily be worked around. My best advice is to disable SSL on your host (either in Nginx or Apache) and serve the site on Port 80 instead of Port 443. Then run the the network update. If you still want SSL afterwards (without a valid cert) you can re-enable the site to run on Port 443.

I think your best best might be to use redirects from the province specific domains to a global domain because you’ll most likely never have enough domain authority for province2.com and province3.com. It’ll be better for you to invest in building SEO strength and optimizing one domain (inbound links, etc) which will help your province specific pages rank higher than having them on fresh province domains. This plugin can help with managing the redirects – https://www.ads-software.com/plugins/safe-redirect-manager/

If you want to go forward with having multiple domains, you can use MU Domain Mapping and “Disable the Primary Domain Check” which will allow you to point and serve pages from multiple domains on the same site. https://www.ads-software.com/plugins/wordpress-mu-domain-mapping/

Yes, this is completely possible with Multisite. Use the Domain Mapping plugin for the different domains – https://www.ads-software.com/plugins/wordpress-mu-domain-mapping/

During your search and replace is it possible that the sidebar widget area is being renamed either as a registered widget area in the db or in the files themselves?

I ask this because your widgets are being moved from the sidebar which is an active area that widgets can go in and then after your clone process that widget area cannot be found anymore so they go to inactive.

I believe that something about your clone process is changing the name of the widget area so the options table doesn’t line up anymore.

I’m running into this same problem. I think the best way to handle this might be to make all of the Admin Bar Links use the Network Domain instead of the Mapped Domain.

Still looking for how to do this in a straight forward way though.

@ron – any idea how to make the Admin Bar Links use the Network Domain instead of the Mapped Domain?

Great, let me know how it goes. Interested to hear if works for others.

@sudar – sorry for the late reply.

Here is a zip with our forked version of Domain Mapping to utilize Transients stored in Memached instead of querying the DB – https://www.dropbox.com/sh/8whw4a3rvdmixkx/AAAHLTHF80Spok4IAzX3SY5Wa

You’ll need to be using Object-cache.php backend with Memcached

Notes
domain_mapping.php is a forked version of the original domain mapping file to store into trasnisents.
sunrise.php is also forked to store into transients
pronto-memcached-purge.php are the hooks to purge memcached transients when you change the domain on a site.

Obviously I recommended testing this in a development environment before production.

If you have any issues let me know.

We forked Domain Mapping a bit to cache the queries in memcached for an install of about 1500 sites.

Would be happy to share the code if someone was interested.

Having the same problem here.

Is there any update to this or a known work around?

My localhost is a pretty standard mac setup, I’ve downloaded the plugin a few more times now and each time I get the whitespace in the bottom when opening the file – really dont understand how it is happening.

Sounds like you guys want to keep the closing ?> – just thought it would be better to follow WP coding standards that recommend omitting it.
Here are some articles out in the community for fixing the problems caused by a whitespace after a closing ?>. Googling a bit, it’s pretty easy to find hundreds of articles from people who have broken feeds and can’t track them down. We just never thought to look in sunrise.php or domain_mapping.php

https://wejn.org/stuff/wejnswpwhitespacefix.php.html
https://www.alex-wells.co.uk/wordpress-rss-feed-white-space-fix/

The whitespace issue breaks the following things:

• RSS feeds
• XML-PRC
• Anything on the admin that requires Ajax
• Admin XML response for adding new categories on a post, need to refresh

I downloaded it again just to confirm, and they are there for me when I open the zip file again. I also now see after looking in trunk and they are not there so that is good news but still confusing how I am getting them. I’m using Sublime to open the files, not really sure how the blank line is getting added.

https://plugins.trac.www.ads-software.com/browser/wordpress-mu-domain-mapping/trunk/sunrise.php
https://plugins.trac.www.ads-software.com/browser/wordpress-mu-domain-mapping/trunk/domain_mapping.php

I’m not sure, but I would assume that my problem is experienced by most people. There are hundreds of posts about White space problems and the issues they cause.

Would it be better to remove the closing ?> tags so the problem can’t occur and it would follow WP coding standards closer?

Is there an argument for keeping the closing ?> tags?