hamellr

Thank you, I’m familiar with both those links. I’ll go through them again and see if I can figure where the problem is arising.

Done, thank you very much

No fork anymore?

No, that is not what I asking for. In the URL Markup Field, under “Auto Display Content” the last box is “URL Markup.” It says “Markup to use for the submitted URL (when auto-display is enabled). Can use %%url%%”

I’m looking for more variables to put in that field, specifically User Name and Post Title that they entered above.

I forgot to mention that the sites I want to split out are all subdomains of the same domain so i believe that if I take one down, all will be down. Which will mean all the sites will be offline for the duration which we’d like to minimize.

It ended up being an issue with the theme. I switched to a responsive theme and the problem went away. Still not perfect, but much more tolerable.

If it is a multisite, I personally would prefer it to be hidden on the Network Admin Page and kept from the admins. I would like, if possible, a way to see from there which domains are getting hit the most so that I can remind admins about security when an event is happening.

Yes, I am using is successfully on a MU install with 3 sites ex. – Pacific Northwest Photoblog

I have this issue also, disabling the Cloudflare plugin fixes. I’ve submitted a bug report on ticket #377444 to CloudFlare

Another bug found; On WordPress MU with ZenCache Pro Network enabled. Every blog says that ZenCache now needs to be updated to the latest version. If I do so, the message goes away for that blog only.

Thank you, as soon as I get to internet access that was built somewhere after 1999, I’ll check it out and see if it works!

Yes, that is correct.

Hmm… maybe that is the problem. I’ll try to disable the Jetpack Mobile theme and see what happens.

Do you have JetPack mobile enabled on those sites?

It is enabled on every single site listed above.

As far as can be done, considering its MU and many of these sites are in production, yes.
That has not been conclusive though as the problem is not consistent.

It feels like it might be related to Jetpack’s mobile theme. But the fact that it is coming up in Browser windows seems like the problem is somewhere else. The mobile theme should only come into play if WordPress did not read the browser settings correctly. Correct?