PHP Warning & Specific Page with 404 Error

  • Resolved zeroTAG

    (@zerotag)


    1 month ago

    Hi! Great plugin, it really helped me deal with a sudden need from a client.

    I would like some help with two issues I encountered:

    • I did notice on the error_log file, a sudden spam of this warning:
      • PHP Warning:  Undefined array key “host” in “…/public_html/wp-includes/theme.php” on line 3811
      • This warning only happens when it is successfully redirected to the subdomain. When using the normal page (with full slug without subdomain), this does not happen.
    • A specific page with the slug “/contest” or “/contests” is not redirecting to the subdomain. But the page displays correctly.
      • But any child-page of this one, triggers a 404.

    I tried digging into the plugins code, but I had no luck in finding why the parent page “/contest” doesn’t redirect, even less why the child pages trigger 404 errors.

    Could the undefined array key “host” be the cause of the 404 errors? I’m speculating now.

    If you would like the links for the specific pages, I can provide.

    Thank you in advance!

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

    (@ruigehond)

    1 month ago

    Hi @zerotag , thank you for using my plugin and thank you for bringing this to my attention.

    1. I can reproduce the missing ‘host’ error, will make a fix for that asap.
    2. Please share the urls for the /contest /contests subdomain problem, as I don’t fully understand what you mean. If you need a page to respond to contest.example.com the slug must be contest-example-com .

    Kind regards,
    Joeri

    Thread Starter zeroTAG

    (@zerotag)

    1 month ago

    Hi! Thank you for answering.

    Sorry I wasn’t clear. Here is the topology:

    • [1] (Home) journeysendpublishing.wanderingwordsmedia.com (/journeysendpublishing-wanderingwordsmedia-com)
      • [2] (Contest) …/contest (/journeysendpublishing-wanderingwordsmedia-com/contest)
        • [3] (Any Child Page) …/contest/[page-name] (/journeysendpublishing-wanderingwordsmedia-com/contest/[page-name])

    Pages on level [2] (including /contest) are all right, they redirect, and no 404 errors happen.

    All child pages on level [3] (specifically on /contest), don’t redirect, and if I manually type the URL with the subdomain it triggers a 404 error, I created a test page on level [3], and you can notice that it doesn’t redirect, and if manually entered the url with the intended final url, it triggers the error.

    In contrast the child pages on level [3] for this page are unaffected, they redirect normally.

    I also tried recreating the page /contest (assuming it was an incomplete creation or something similar affecting it’s children), but with no effect, same outcome.

    Let me know if you need more information,
    Cheers!

    • This reply was modified 1 month ago by zeroTAG. Reason: readability
    Plugin Author Joeri van Veen

    (@ruigehond)

    1 month ago

    Thank you, just to let you know, I will pick this up monday (tomorrow).

    Plugin Author Joeri van Veen

    (@ruigehond)

    1 month ago

    Hello @zerotag , thank you for taking the trouble to note and explain these issues. I have just released version 1.8.2 in which I believe both are fixed.

    Let me know if this is not the case, or if there is another issue. Feel free to mark this as resolved when everything is fine.

    Thanks again for helping me make the plugin better,
    Kind regards,
    Joeri

    Thread Starter zeroTAG

    (@zerotag)

    1 month ago

    Hi!

    Thank you so much, indeed it fixed both issues. All pages are working correctly now.

    PS.: I did find out why only the /contest was not working. It was because the /anthology already existed on the main domain, so some kind of shenanigans with slug logic from WordPress I assume.

    Cheers!

Viewing 5 replies - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.

  • 5 replies
  • 2 participants
  • Last reply from: zeroTAG
  • Last activity: 1 month ago
  • Status: resolved