$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'); ?>custom post types - template id="1921" from inside editor doesnt work?|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>custom post types - template id="1921" from inside editor doesnt work?

    custom post types - template id="1921" from inside editor doesnt work?

    matteradmin8PV0评论

    I have inherited management of a WordPress based site. And suddenly something like this [template id="1921"] typed in the editor isn't working.

    Been looking in the DB and there are posts with a post_type template. But I can't find any plugin or documentation to get these bracket template calls to work again. All I can find is PHP options, but I would rather just fix whatever used to work.

    EDIT: Isn't [display-posts id="x"] suppose to be an official WP shortcode? All it displays on the site where content of post with id x is suppose to be is "[display-posts id="x"]". Why would it do that?

    Articles related to this article

    Post a comment

    comment list (0)

    1. No comments so far