$conf, $runtime; function_exists('chdir') AND chdir(APP_PATH); $r = 'mysql' == $conf['cache']['type'] ? website_set('runtime', $runtime) : cache_set('runtime', $runtime); } function runtime_truncate() { global $conf; 'mysql' == $conf['cache']['type'] ? website_set('runtime', '') : cache_delete('runtime'); } register_shutdown_function('runtime_save'); ?>permalinks - Getting 400 Bad request Error when trying to open posts after updating to wordpress 5.0|Programmer puzzle solving

Programmer puzzle solving

    最新消息：Welcome to the puzzle paradise for programmers! Here, a well-designed puzzle awaits you. From code logic puzzles to algorithmic challenges, each level is closely centered on the programmer's expertise and skills. Whether you're a novice programmer or an experienced tech guru, you'll find your own challenges on this site. In the process of solving puzzles, you can not only exercise your thinking skills, but also deepen your understanding and application of programming knowledge. Come to start this puzzle journey full of wisdom and challenges, with many programmers to compete with each other and show your programming wisdom! Translated with DeepL.com (free version)
    你的位置： HOME>matter>permalinks - Getting 400 Bad request Error when trying to open posts after updating to wordpress 5.0

    permalinks - Getting 400 Bad request Error when trying to open posts after updating to wordpress 5.0

    matteradmin11PV0评论

    I have some Wordpress blogs and after updating to Wordpress 5.0, I am getting same error behavior on them. Now When I open the URL of some of the posts, I am getting 400 Bad request error and on some of them there is no error, but the content doesn't render. I've tried to change permalink format and change it back to the first type (post name) as suggested in a few questions in similar problems, but it didn't work.

    EDIT

    If I choose the default permalink pattern (?p=123) The error will fix, but I'll lose all of my links.

    Articles related to this article

    Post a comment

    comment list (0)

    1. No comments so far