What’s New in WordPress 5.1 “Betty” ?
After the WordPress 5.0 Release back in 6th December 2018. WordPress Community just introduced new version 5.1 named as “Betty” in honour of acclaimed jazz vocalist Betty Carter.
Following are the features you can expect in this WordPress 5.1 Release.
With security and speed in mind, this release introduces WordPress’s first Site Health features. WordPress will start showing notices to administrators of sites that run long-outdated versions of PHP, which is the programming language that powers WordPress.
When you install new plugins, WordPress’s Site Health features will check them against the version of PHP you’re running. If the plugin requires a version that won’t work with your site, WordPress will keep you from installing that plugin.
Introduced in WordPress 5.0, the new block editor continues to improve. Most significantly, WordPress 5.1 includes solid performance improvements within the editor. The editor should feel a little quicker to start, and typing should feel smoother.
Expect more performance improvements in the next couple of releases.
5.1 introduces a new database table
wp_blogmeta to store metadata associated with sites and allows for the storage of arbitrary site data relevant in a multisite / network context. This feature helps to retrieve multiple sites data faster without calling switch_to_blog() function initially that used to access via options table in slow way.
The Cron API has been updated with new functions to assist with returning data and includes new filters for modifying cron storage. Other changes in behavior affect cron spawning on servers running FastCGI and PHP-FPM versions 7.0.16 and above.
New JS Build Processes
Other Developer Goodness
Miscellaneous improvements include:
- Updates to values for the
- New test config file constant in the test suite, new plugin action hooks
- Short-circuit filters for
- A new
- Improved taxonomy metabox sanitization
LIKEsupport for meta keys when using
- A new “doing it wrong” notice when registering REST API endpoints
Comments are closed