LinuxArchitect

I found my problem. In my apache config for the alternate domain, I pointed the doc root to the primary domain folder, but I forgot to also change the <directory> config that allows the .htaccess file to be read.

I see what you mean, the 404 is coming back from apache rather than a 404 page generated by wordpress. Thanks for your help and suggestions. I’ll let you know what I find.

My testing is on a brand new multisite, with two themes enabled, Frost and the child theme. I tested with just Twentig active. I’ve made no code changes to the parent or child, just a standard child style.css file. You can see images here: https://themc.network/twentig-debug-images/. That’s hosted on my (un-developed) standalone site with the same Frost child theme with Twentig active. My multisite site is being actively developed so I’ve switched it back to the Ollie Child theme for now.

If you need it, I can set up a new multisite and give you admin access to it.

• This reply was modified 5 months, 4 weeks ago by LinuxArchitect.

Guys, don’t forget that WordPress has the concept of home and front pages. The home page is the blog, the front page is the landing page, which may also be a blog or it might be static content without a blog loop.

If you’re having problems, or want more flexibility, compare is_home() with is_front_page().

I’m using v1.0.3 and I sometimes get php timeouts due to the slow speed. Often the plugin takes several seconds, sometimes >20, to display a single comment form on a simple page or post.

Is this to be expected?