Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • November 22, 2018 at 3:42 pm #1036562
    cg

    hi there,

    i have set a custom 404-page withhin the enfold-settings in a child theme.
    theme > options > custom error 404 page

    Before the update, when entering a “wrong” url, the content of that page was shown and a HTTP status 404 was send back to the client. The URL in the address field of the browser didn’t change. Everything ok and correct.

    But now, with Enfold 4.5, a not existing url is been redirected with a status ‘302’ to the custom error page url with a status ‘200’ … thats not good … and might cause problems with search bots / the google index.

    Test-URL (test with httpstatus.io): https://tabulor.de/hello/test

    result

    • This topic was modified 5 years, 11 months ago by cg.
    November 22, 2018 at 6:26 pm #1036677
    Victoria

    Hey Christian,

    Can you give us temporary admin access to your website in the private content box below, so that we can have a closer look?

    Best regards,
    Victoria

    November 22, 2018 at 7:12 pm #1036724
    cg

    I don’t think it’s a specific problem of my page setup … but you can have a look … :-)
    Access details below.

    November 27, 2018 at 3:41 pm #1038035
    cg

    Update to my issue:

    i solved the 200-status by adjusting the settings of WP Super Cache. Which wasn’t necessary before Enfold 4.5.

    But the requirement to do so seems to result because of a change how Enfold handles 404 errors … i think.
    A missing url is now redirected with a 302 to the custom 404 error page instead of just showing the content of that page while staying at the requested (missing) destination-url with a 404 response directly.

    So … that last part is still in question.

    November 27, 2018 at 5:22 pm #1038083
    cg

    The previous behaviour of Enfold can be seen here at an older version (4.4) example:

    => https://kriesi.at/themes/enfold-elegant-portfolio/a-wrong-url-test

    It stays at the “wrong” url … sends a 404 response … no redirect … just displaying the content of the custom 404 page. That’s how it should be.

    November 27, 2018 at 5:50 pm #1038092
    cg

    The unwanted behaviour is caused by the workaround for WPML by Günter in “functions-enfold.php” line 2211 ff. in version 4.5 of Enfold compared to version 4.4.

    Function: ‘av_error404’

    Maybe you can find a better way to support WPML without that redirect solution?

    Edit: the plugin “404page” (https://de.wordpress.org/plugins/404page/) works as expected and is compatible to WMPL … maybe it can be a source / an inspiration for a solution …

    • This reply was modified 5 years, 12 months ago by cg.
    November 30, 2018 at 11:24 am #1039271
    cg

    Is someone looking into this?
    Would be nice to hear a reply about how and if it will be or not be changed in future releases.

    For now, i will use that additional plugin to achive the accurate behavior without redirect.
    But it would be great if the option from Enfold could work like before.

    December 1, 2018 at 4:49 pm #1039682
    Mike

    Hi,
    Sorry for the late reply, I see that the dev team has opened a issue for this and is working on it. I’m sure they will post here once they have a solution, but I will also try to keep you informed of updates.

    Best regards,
    Mike

    December 1, 2018 at 4:54 pm #1039686
    cg

    Thanks for letting me know and have nice weekend. :-)

    December 1, 2018 at 6:59 pm #1039718
    Mike

    Hi,

    You too :)

    Best regards,
    Mike

  • Author
    Posts
Viewing 10 posts - 1 through 10 (of 10 total)
  • You must be logged in to reply to this topic.