Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Joeri van Veen

    (@ruigehond)

    Hello @linuxarchitect , thank you for using my plugin!

    You did right by the instructions indeed, but I think something is amiss in your server config, when you compare the 404 from https://makergeorge.me/child-page-1/ with some other non-existing page in your WordPress install, for example https://georgeboyce.me/makergeorge-me/child-page-2/ they are quite different.

    I think your Apache only sends makergeorge.me to the location of your WordPress install, and for some reason does not react when a specific page is requested. My plugin itself will not send a 404, because when it does not find a candidate to display, it will simply pass on the original request to WordPress without interfering. And WordPress will show its own 404 when nothing can be found for that address.

    Does this help, do you have an idea what could be happening?

    Plugin Author Joeri van Veen

    (@ruigehond)

    • You could try / troubleshoot by switching off each-domain-a-page and going to any page on makergeorge.me, when configured correctly, it should show the homepage of your WordPress install, a WordPress 404 or a specific page if you requested an existing page (WordPress reacts to any domain pointing at it).
    • Maybe a RewriteRule in the .htaccess in your root is picking up everything after the root / and sending it to the main domain only, or bust. I would look there first, come to think of it.

    Let me know if you need further assistance. My Apache is a bit rusty (using Nginx now) but I hope we can solve this!

    Kind regards, Joeri

    Thread Starter LinuxArchitect

    (@linuxarchitect)

    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.

    Thread Starter LinuxArchitect

    (@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.

    Plugin Author Joeri van Veen

    (@ruigehond)

    Excellent work, thank you for getting back to me in this thread!

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.