$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'); ?>plugins - WordPress 5 upgrade: until when is it safe to keep project running in 4.x?|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)

plugins - WordPress 5 upgrade: until when is it safe to keep project running in 4.x?

matteradmin8PV0评论

As announced, Wordpress version 5 will be hitting the road this December. Considering the availability of security support and patches for previous versions (4.9.x, 4.8.x, 4.7.x), until when is it considered safe to postpone the 5.x upgrade and keep projects running in 4.x?

As announced, Wordpress version 5 will be hitting the road this December. Considering the availability of security support and patches for previous versions (4.9.x, 4.8.x, 4.7.x), until when is it considered safe to postpone the 5.x upgrade and keep projects running in 4.x?

Share Improve this question edited Dec 6, 2018 at 11:04 Marcos Buarque asked Dec 5, 2018 at 11:36 Marcos BuarqueMarcos Buarque 1572 silver badges10 bronze badges 3
  • 3 Why do you need to postpone it? If you don't want the new editor just install the Classic Editor plugin. – Jacob Peattie Commented Dec 5, 2018 at 11:50
  • I have read version 5 could be more disruptive than usual updates and maybe not backwards compatible in some aspects, but I should maybe dig deeper into that. – Marcos Buarque Commented Dec 6, 2018 at 11:06
  • Only in regards to the editor, which is addressed by the Classic Editor plugin. – Jacob Peattie Commented Dec 6, 2018 at 11:14
Add a comment  | 

1 Answer 1

Reset to default 3

As stated here:

The only current officially supported version is WordPress 4.9.8. Previous major releases before this may or may not get security updates as serious exploits are discovered.

And it has always been that way - only one version is officially supported.

This means it's always a bad idea to postpone updates.

So if you're afraid of Gutenberg, then you should:

  1. Prepare a test version for your site and check if it will cause any problems with 5.0.

  2. Disable Gutenberg, if you don't want to use it.

You can disable Gutenberg with this code:

if (version_compare($GLOBALS['wp_version'], '5.0-beta', '>')) {
    // WP > 5 beta
    add_filter('use_block_editor_for_post_type', '__return_false', 100);
} else {
    // WP < 5 beta
    add_filter('gutenberg_can_edit_post_type', '__return_false');
}

or using one of available plugins.

Post a comment

comment list (0)

  1. No comments so far