WordPress 5.3 “Kirk” Released, Brings New Default Theme, Editor Improvements, and UI Tweaks
Credit: Heinrich Klaffs CC BY-SA 2.0
WordPress 5.3 “Kirk,” named in honor American jazz musician Rahsaan Roland Kirk, is now available for download. The update includes a new default theme named Twenty Twenty, user interface improvements aimed at accessibility, and new block editor features.
This release saw contributions from 645 volunteers, which is the largest contributor group ever for a WordPress release.
The release was led by Matt Mullenweg, Francesca Marano, and David Baumwald. They were joined by the following contributors in supporting roles in getting version 5.3 released.
- Editor Tech Lead – Riad Benguella
- Editor Design Lead – Mark Uraine
- Core Tech Lead – Andrew Ozz
- Default Theme Design Lead – Anders Norén
- Default Theme Wrangler – Ian Belanger
- Docs Coordinator – Justin Ahinon
- Accessibility Lead – JB Audras
- Marketing Lead – Mike Reid
- Media Focus Lead – Mike Schroder
WordPress 5.2 had 84 million downloads before WordPress 5.3’s release.
The PHP native JSON extension is now required for any site running WordPress 5.3 or later. This should not be an issue for the majority of users because the extension has been bundled with PHP by default since 2006. WordPress will output an error and cancel the update procedure if it detects the extension is missing. Users who are unable to update will need to contact their web hosts to have the extension enabled.
Twenty Twenty: New Default Theme
WordPress is getting a fresh coat of paint. Anders Norén led the design team for the new Twenty Twenty theme, which was a fork of his original Chaplin theme.
The Twenty Twenty theme is completely geared toward creating content with the block editor with its bold and opinionated styling. It comes with a cover page template and has a custom color system designed to keep the site’s color contrast accessible.
Block Editor Features and Improvements
WordPress 5.3 includes features from the versions 5.4 – 6.5 of the Gutenberg plugin along with bug fixes and performance improvements from versions 6.6 and 6.7. For users who have not been running the plugin, they should see faster loading times and quicker responses from keystrokes.
WP Tavern has covered every major release of the Gutenberg plugin that will be bundled in WordPress 5.3, except Gutenberg 5.6. Catch up on any features you missed with the following articles.
- Gutenberg 5.5 Adds New Group Block for Nesting Child Blocks
- Gutenberg 5.7 Adds New Block Appender for Group and Columns Blocks
- Gutenberg 5.8 Released with Prototype of New Block-based Widgets Screen
- Gutenberg 5.9 Brings Major Improvements to Block Grouping, Introduces Snackbar Notices
- Gutenberg 6.0 Adds Layout Picker to Columns Block
- Gutenberg 6.1 Introduces Animation to Block Moving Actions, Adds Block-Based Widgets Screen Experiments
- Gutenberg 6.2 Adds Nesting Capabilities to Cover, Media & Text Blocks
- Gutenberg 6.3 Improves Accessibility with New Navigation and Edit Modes
- Gutenberg 6.4 Adds New Typewriter Experience, Cover Block Resizing, and Block Inserter Help Panel
- Gutenberg 6.5 Adds Experimental Block Directory Search to Inserter and New Social Links Block
Other Core Features
Work toward large image handling went into the update. Instead of checking file sizes, images larger than 2,560 pixels are scaled down and used as the “full” image size. This change makes large images web ready and will significantly decrease file sizes for many users who upload images without optimizing them beforehand. This is common with mobile phone uploads.
For those who prefer to maintain the original sizes of image uploads, which is sometimes the case with photography sites, grab the Disable “BIG Image” Threshold plugin.
The site health screen introduced in WordPress 5.2 has some user experience improvements, such as tweaking how the grading indicator works for clarity. WordPress site owners will also need to verify their admin email every six months. This feature is to help make sure site recovery emails are being sent to the right place when an error occurs. It also lays the groundwork for future features that may build upon it.
Developer Changes
Developers should read the full WordPress 5.3 field guide to make sure none of the changes affect their plugins or themes. Some of the changes include the following.
- Full support for PHP 7.4.
- Improved date/time handling.
- Robots meta tag now used for discouraging search engines from listing a site.
- New meta key comparison operators added.
- Integers are no longer allowed for nav menu slugs.
wp_die()now allows custom HTML.
32 Comments
·
Hated the new UI styles for borders. Need to be softer and smooth
Report
·
Me too. The style for secondary button is bad (primary button is fine).
Report
·
The same here however, thanks to the community for the update.
Report
·
Same here. Admin input and select borders are way to prominent.
The new image size names (1536×1536 and 2048×2048) aren’t very expressive/beginner friendly.
I appreciate the large image size handling and filter. Looking forward to large file size handling for more granular control.
Report
·
Yep, those borders are fugly
Report
·
On first sight yes. But seconds later and working in it, i love the new UI. It’s much clearer. And important: better for accesibility.
Styling is always personal. As long as it improves UX & accesibility for everyone, i’m totally fine with it.
Remember: the admin doesn’t need to win prices on beauty, but on functionality.
Report
·
“..periodically asked to confirm that your admin email address is up to date..”
I don’t know… isn’t it getting a bit tedious?
Report
·
I have just updated to this version but my site still under maintenance and am scared of losing my contents
Report
·
Hi Wasiu,
this should help:
https://kinsta.com/knowledgebase/wordpress-stuck-in-maintenance-mode/
Report
·
Why would this be an issue if you’ve already backed the site up and are also using a staging site cloud copy of the site before updating your live production server?
Report
·
WordPress 5.3 appears to be a solid version, tightening the ship on a broad array of fronts.
Many resisted WP 5.0, and many others who upgraded to 5.0+ are now using the Classic Editor plugin.
If that’s you, listen up: WP 5.3 with the new and improved editor is your friend. Give it a fresh look; you won’t be disappointed.
Report
·
I tried it out (again). I still can’t drag and drop a sentence from one paragraph to another in the block editor, so I’m already back to the Classic Editor plugin. I won’t even consider switching until I can do that one simple thing.
Report
·
Seems like a solid 5.x release that should bring over people reluctant to the Gutenberg way of life (?). 😃
Report
·
Well I’m off to a good start… if I try and edit a Post or Page I get an error message: “The editor has encountered an unexpected error.” But only on one of my sites (so far).
An afternoon of problem solving, deactivating plugins etc. awaits :-(
Report
·
I thought something had gone wrong with the update when I saw those borders in the admin area…. no design subtlety at all. (I get that is the point, but we aren’t all impaired)
However, as with all changes like this, I’ll give it a go for a few weeks and see if it still rankles, if so it’s easy enough to add tweaks to my custom admin style sheet. (or someone else will develop a plugin)
Report
·
About time Rahsaan got some love!
Say a little prayer
Volunteered Slavery
Hat-tip to Matt for the righteous dedication.
Report
·
This UI update is horrible and painful for the eyes. Why so much attention to the borders? Take a look at Google design, don’t reinvent the wheel. Hope this is not permanent.
Report
·
I always used the Gutenberg plugin, so I follow updates before they get into the core. As for the design update, I found it positive for usability, not beautiful, but clear.
As for the new theme, I found it excellent, so much so that I use it on my site with the AMP plugin. I hope they release plugins that increase their features.
Report
·
I just tried this version and really liked the New Default Theme it has to offer. Looking forward to more updates.
Report
·
Yup 5.3 is great update by wp which supports 7.4.
I am with hosting they upgrade version automatically and due to that 3 of my old sites got errors of theme and plugins and after all hurdle i’ve to downgrade to previous version of wp.
Report
·
Likely you’ve got an issue with themes/plugins that are not ready for PHP 7.4, rather than being a problem with WP 5.3.
Report
·
which plugins, specifically?
Report
·
the new WP UI is awesome i recently upgraded to it and i must tell you i love…so far i haven’t had any issues working with it
Report
·
I updated 4 production sites to WordPress 5.3
No problems after a week.
Great job to the WordPress 5.3 developers and to the 20-20 Theme team. This by far has been my favorite WordPress update in a long time…
Report
·
Some of my older permalinks with /%year%/%monthnum%/%day%/%postname%/ are suddenly broken with 5.3.
I was getting Google Search console warnings, probably my SEO score droped like a rock.
Have rolled back to 5.2.x, the links work again.
How can this even happen, are there no tests?
Report
·
I use the same structure for permalinks on some websites, and I had no problems after update to 5.3. I doubt that the problem is directly related to WordPress, maybe you have some conflict with plugins or some plugin is causing a problem.
Report
·
Yes, this is a known issue being addressed here: https://core.trac.wordpress.org/ticket/48623
Report
·
Sound like this issue https://core.trac.wordpress.org/ticket/48623
The existing links, aren’t broken, but when you try to generate a link for some of existing posts it comes out wrong (which in turn might affects canonical tags and so on).
This is caused by caused by date_default_timezone_set() calls to change default PHP timezone setting an a theme/plugin, which is something WordPress core doesn’t support.
Counter-intuitively this was caused by work on preventing changing PHP timezone from breaking things, it’s just that improving it in one place made it break in adjacent one.
In a nutshell – core still works fine under normal circumstances, but if you already had the issue then that broke things in different way in 5.3.
This happened because core it unit tested under “normal” configuration and the issue is rare enough and affects few enough post that it was never reported during development and pre-release versions.
There will be a unit test for generating permalinks breaking in this way now and there is proposal to check for this in Site Health tool.
Report
·
It appears that lots of plugins and themes are using this code in one form or the other.
Why is there no “deprecated” notice at least a few month before such a breaking change?
This change should be rolled back immediately, it probably affects millions of sites which did not even notice yet due to no monitoring at google or similar.
A weird quote can beo found here, “For the context while we consider date_i18() legacy function now”, but there is not one word about that in Code Reference nor is there a doing_it_wrong migration hint or similar.
Something went pretty wrong with this commit, sorry to say.
Report
·
It doesn’t. There are about 600 hundreds of plugins in official repo that do it, by my count (those not calling it with UTC argument, which is harmless). None of them are especially widely installed (100K active and less) and a lot of instances seem to be in externals SDKs. libraries, unit tests, and such.
I am not sure what do you consider breaking change here. The problem with permalink was certainly unfortunate, unplanned, and will be fixed in patch release.
While there were some changes to edge case behaviors in older Date/Time functions, the work was done with usual commitment to backwards compatibility and there are a lot of unit tests added to ensure that.
It is hard to estimate, but I would say millions is too pessimistic. There are no major plugins that break things in this way. And changing default timezone broke things long before 5.3, just not like this.
To be clear “legacy” here does not signify a formal deprecation status, is signifies that a function is an old mess.
date_i18n() is not formally deprecated and there is no hard immediate need to migrate from it, though that is certainly advisable due to problems inherent in its design (chiefly use of WP timestamp).
Certainly did, I very much would have preferred that permalink breakage was caught before release.
Report
·
I rarely update wordpress, each update makes it more difficult to use, but this version is quite smooth, although there are some points I do not like much.
Report
·
A year on from the release of the Block Editor “Guttenberg”, and as much as its come along way and going in the right direction. Unfortunately, it’s still way off from replacing any page builders. Hopefully 2020 is the year for migration for a lot of businesses.
Report