sontru

Just to update. I finally upgraded WordPress MS to 3.5.1 today.

The missing header images issue was non-present, so it must have been caused by the serialized data due to the change of domain name.

However, I did experience one weird issue, and this being one of the subsites got marked as ‘deleted’, to which I had to ‘restore’. After undeleting, the subsite had no admins, so I had to re-add them!

Use a network plugin manager plugin such as https://www.ads-software.com/extend/plugins/multisite-plugin-manager/ to manage and restrict plugins being available to subsites.

I would change the login name directly in the database. If this is not possible or a PITA, then forcing strong passwords on admin accounts.

Can anyone recommend a good double password challenge plugin?

I don’t think my domain has changed. My live site is ‘wp.mydomain.com’ and my test site is ‘wptest.mydomain.com’.

Unless we are saying that the whole of string ‘wp.mydomain.com’ is the domain, then ‘wptest.mydomain.com’ IS different and therefore is changed.

I mean, on the live site, one of the uploaded images is set to show and is showing. On the (test) upgraded site, nothing is checked to show. I am comparing the live against to test to see what has happened after the update to 3.5.1.

I have found another issue after the update, not just the header images, and this again is under the theme’s appearance. It is the ‘Theme Location’ under the Menus options.

Somehow the update does not keep some of the theme options for subsites… This is not a great issue for me personally, as my multisite only has a few subsites (which will need adjusting), but I can see for larger sites with lots of subsites, then it is going to be a hassle going into each subsite and setting some of the theme options, after an update…

(I remember, no it is not related to the clone, once the clone was setup, all header images were just fine. I verified that the clone was working in exactly the same way as the live site before upgrading.)

The header image(s) have reverted to whatever the default for that theme. For example a subsite using the Twenty Ten theme, has uploaded two images and have selected selected one of them to show.

Inspecting the page source say:

<img src="https://subsite.testsite.domain.com/wp-content/themes/twentyten/images/headers/path.jpg" width="940" height="198" alt="">

Which shows the default Twenty Ten ‘country lane’ image. If I go into the Dashboard -> Appearance -> Header, none of the check buttons against any header image option is checked.

None! They just don’t appear – as if they are not set.

The header images I am talking about are the ones the admins are setting in the theme’s Appearance Header options.

Looks like ‘used the uploaded image’ option is not checked as it should.

(Maybe it is the cloning and renaming process that is causing this. Although, I would have thought a search and replace of all strings ‘livesite’ to ‘testsite’ would have also re-pointed the header images set this way..?)

Nevermind, I’ve found this plugin: https://www.ads-software.com/extend/plugins/wordpress-https/

‘Participants’ you say? Do you have bbPress network enabled for all your subsites? If yes, then bbPress 2.2.6 is your problem!

See: https://www.ads-software.com/support/topic/stop-bbpress-automatically-adding-network-users-as-participants-of-subdomains?replies=6

And: https://bbpress.org/forums/topic/two-bugs-with-bbpress-2-2-4-and-wordpress-multisite-3-4-2/

No you do not. You might need to create a blogs.dir if you are not using the latest version 3.5 (3.5.1).

https://codex.www.ads-software.com/Create_A_Network

Get file or command-line access and delete or move the plugin file or folder.

The other thing I have to do is to configure my webserver to resolve the wildcards.

1) You can set up one or the other – not both methods.
2) Yes, you can install a theme and not make this network available.

In your cPanel for your domain name, go to the DNS setting and create an entry with ‘*’ resolving to your server’s IP.

There is a problem with the wildcard entry as test.mikecrosby.com (or xyz.mikecrosby.com) does not resolve to 108.179.221.206 which mikecrosby.com (and https://www.mikecrosby.com alias) resolves to.

It doesn’t look like the *.mikecrosby.com DNS entry is present.

Strange that show work.

You will have to do it manually, by going to the subsite dashboard and to the All Users page under Users menu item. Select all the users and remove (bulk action).