On June 1 we’ll be retiring our older WordPress.com editor and transitioning to the more recent (and more powerful) WordPress block editor. Want to know how this may affect your site and what you can expect? Read on.
Reading on only confused the hell out of me. Are they going to remove the Classic Editor on June 1st?!
One of the subsequent comments / replies finally clarified what they mean ..
Comment – As long as I can still fire up and use the Classic Editor, I’m fine . . .
. . . but this post is a bit confusing in that regard.
You open with saying you’ll be retiring the old editor on June 1st.
You then make the exaggerated claim we’ll love the block editor (I don’t know any blogger that loves it; I certainly don’t). The most asked question I get is how to fire up the Classic Editor.
You close the post with saying we can still use the classic editor.
What am I missing? What are you retiring on June 1st? Bottom line: are you keeping the classic editor or are you about to make many users unhappy?
Yes, yes, I’m not supposed to ask questions here . . . but then, why post at all?
Reply – Thanks for asking! Sorry for the confusion. To clarify, there are currently three editors available on WP.com. The older editor that we’re retiring looks like this: https://a.cl.ly/L1u7ldwB The two editors that will remain are the block editor which looks like this: https://a.cl.ly/BluZe4w5 and the classic editor, which looks like this: https://a.cl.ly/L1u7ldNK
To explain in words that I can understand .. at the time of writing, in addition to the new Block Editor, WordPress.com has two different front-ends which relate to pre-block editor times: the original vanilla-flavoured version where the dashboard has white text on a black background; and an “improved” version called Calypso (although that name is seldom used in any of their material) that was introduced in 2015. This newsletter includes images of both front-ends.
In essence, new WordPress.com users from around 2016 were presented with the Calypso interface, while older users usually had a choice of either.
This was all before the introduction of the new Block Editor in late 2018. The dashboard for the Block Editor is based on Calypso.
Their blog is effectively saying that it is Calypso which is being retired. This will leave the original front-end, now known as the Classic Editor, and the Block Editor.
The question is .. what will Calypso users see on June 1st, 2020? My money is on the Block Editor in an attempt to get them to transfer to it. If this happens then click on the three dots icon (near the top-right-hand corner), scroll down to the bottom of the menu and click on “Switch to Classic Editor” if you do not wish to use the Block Editor.
I will check to see what actually happens on June 1st, and make any necessary modifications to this post.
Just for information. There were two maintenance releases back in December 2019, 5.3.1 and 5.3.2, which comprised a small number of security and bug fixes.
Several recent changes have been made to WordPress.com which are not part of the Gutenberg project.
My Home is displayed on the Calypso interface after you have clicked on My Site(s) as part of the login process. It contains a number of quick links which allow faster access to various parts of the system.
Page Layouts. When you add a new page you will now be presented with a screen which allows you to pick a layout for it. I would personally call it a template, but WordPress uses that term in a different context. There is quite a wide range of layouts. If you are not interested in any of them then simply select the blank layout. This blog describes the feature in more detail.
WordPress.com Block Editor UI Redesign
This appeared in my WordPress.com account last Thursday (March 26th, 2020). The general layout looks more professional. It includes redesigned icons, better spacing, text colour options and a range of initial block patterns that can be incorporated into posts / pages. See the relevant blog for more information.
I must admit that I am confused with the timing of this introduction. The features recently appeared in Gutenberg 7.7 which, when you read the section below on the WordPress 5.4 release, you will see is post WordPress 5.4?!
WordPress 5.4 Release
The latest version of WordPress was released to WordPress.org users on March 31st, 2020. It will follow shortly on WordPress.com. It incorporates 10 Gutenberg development releases, from 6.6 to 7.5.
FYI – Gutenberg releases appear approximately once a fortnight. They are mainly for internal use by the WordPress developers although they are available as a plugin on WordPress.org for anybody who is brave enough to play with it (but this is absolutely not recommended for typical users or for use on production sites).
WordPress 5.4 could be best described as a release which concentrates on polishing the block editor. It includes:
A new Social Icons block which allows you to incorporate links to multiple social media sites by using their standard logos. This is the sort of thing that you see on many websites nowadays, viz. a row of social media icons
The revised Buttons block now allows you to set up multiple adjacent buttons
Various updates to the ongoing accessibility and privacy projects
Full screen mode in the block editor is now the default on a new WordPress installation or on a new device. This means that the sidebars to the left and right of the display of the post / page are not shown. If you do not like this setup (and I do not) then you can change it by clicking on the three dots menu item in the top right-hand corner and un-checking the full screen mode.
A quick reminder on the overall Gutenberg project. It is said that it will consist of four phases:
Introduction of the block editor in phase 1
Expansion of the block editor to encompass other parts of the system in phase 2, e.g. menus, widget areas and the Customiser
Collaboration and multi-user editing in phase 3
And multilingual support in phase 4.
We are currently in phase 2, and tentative dates for further releases in 2020 are August for WordPress 5.5 and December for WordPress 5.6. I consider that this phase will probably go into 2021. Obviously, any talk of dates is purely speculative at the moment, given the COVID-19 virus.
It might be useful to know that work on the various aspects of phase 2 goes on in parallel. Decisions on what will be incorporated in any given release depend on the stability of the relevant software at the time, and on whether it fits coherently into the overall design at the time. For example, the navigation block (the menu in old money) was considered to be ready to go into 5.4. However, it did not fit coherently into the current design, and so it has been put on one side for the moment.
Work on the full-site editing feature continues. A prototype was developed back in September 2019 if you want to take a look at how it might possibly appear. I suspect that it will be WordPress 5.6, probably later, before it is likely to be released.
The block directory, a home for third-party blocks, is currently planned for inclusion in WordPress 5.5. It will primarily be for use by WordPress.org users.
The ability for WordPress.org users to control the automatic updating of plugins and themes is also slated for WordPress 5.5.
Finally, XML Sitemaps can be used by search engines to discover the content on a website with less fuss. A WordPress prototype, implemented as a plugin, has recently been developed. Presumably, it will eventually appear in the core WordPress product at some point.
Here are some notes if you have an interest in this subject:
The majority of the current development work in this area tends to relate to the use of the WordPress software, not to the website that you create / update. In addition, any new features are likely to be limited to use with the new block editor, not with the classic editor
However, there is a WordPress project which has been set up to look at accessibility on websites. Their Accessibility Handbook may provide some useful information
There is a theme review team which checks new themes for various things, including accessibility. If a theme passes the checks in this area then it is deemed “accessibility ready”. This relates to the theme itself, not necessarily to the website that you design with it
WordPress Version 5.2 was launched back in May 2019. Three minor versions (5.2.1 through to 5.2.3) subsequently followed at intervals, consisting mainly of bug fixes with the occasional enhancement. 5.2.4, a security fix release, appeared a month ago.
The latest major version, 5.3, has just been made available to WordPress.org users on November 12th, 2019. It will follow shortly to WordPress.com users. The main focus of this release is to polish current interactions and to make the user interface more friendly. A new theme, Twenty Twenty, is included in the release.
Development continues with new versions appearing every
fortnight as Gutenberg plugins (Gutenberg being the project name). Gutenberg versions
5.4 through to 6.5 have been incorporated into WordPress 5.3, along with bug
fixes and performance enhancements in 6.6 and 6.7 Changes include:
Improved handling of large images which have been uploaded via a camera. WordPress will now reduce the size of big images to a default of 2560 pixels.
The cover block now supports a greater range of nested blocks. It also has a resizing option and the ability to have a solid colour background, as an alternative to an image.
The group block supports the concept of nested blocks. A group can be saved as a reusable block.
The columns block includes various improvements: up to 7 columns in a block; the ability to size individual columns; and support for colour.
Typewriter experience keeps the user’s place on the screen by automatically scrolling down appropriately as he types, thus avoiding the problem of typing right at the bottom of the screen, or even worse beyond the bottom when you cannot see what you are typing.
A Social Links block has been introduced
Widgets. There are now 9 widget blocks which can be incorporated into the main content area of a page or post: calendar, latest posts, categories, search, shortcode, archives, latest comments, RSS and tag cloud. The idea of legacy widgets in blocks which was being mooted appears to have been dropped.
Site admin email verification. This new screen will
be displayed once every 6 months. It has been introduced because of problems
where sites do not keep this email address up to date, resulting in important
emails not being delivered to the current site admin.
Page templates. I have recently discovered on my WordPress.com account which runs the block editor that “add new page” now produces a display of various possible page templates that can be used. As I am not interested in any of them, I simply select the blank template.
Discouraging search engines. The method employed to keep a site secret, where this was required by the site owner, was only moderately successful. A change has been made to make it more likely that search engines will not display such sites.
Improved date / time component handling.
Site Health Check (WordPress.org users). Further
features have been added.
(WordPress.org users). PHP 7.4,
which is due out shortly, will be supported.
version 5.3 includes a lot of bug fixes and minor changes, generally making the
product more reliable, while ironing out some of the idiosyncrasies.
Accessibility improvements for WordPress users. There are 50 updates in this area, including improved media controls, darker field borders and improved button styles.
My experiences with
the block editor
I have been using the new block editor on my own website (bkthisandthat.org.uk) and on several other sites since January 2019. I have discovered a couple of minor bugs which I have reported, but I have generally found it to be stable.
My only concern at the present time is with tables. Before the block editor the user had to handcraft HTML tables. There is now a table block. However, HTML tables with empty cells or images will not convert correctly to a table block. The table block itself is somewhat rudimentary. In particular, it does not allow column widths to be specified, nor does it allow an image in a table cell.
I have dabbled with the media and text block and with the columns block. Neither is perfect at the current time. The media and text block does not appear to adhere to the margins that are used in the theme, at least not in my theme. The columns block is just about usable.
What will be next?
Gutenberg development has four phases:
the block editor
collaboration, allowing multiple users to co-edit content in real time
Phase two (customisation) is currently in progress which includes headers, footers, menus and sidebars. A proposed design under the umbrella title of “full site editing” was put forward in September where these various elements, as well as the main content section, are each called block areas. The block editor would be able to display all block areas, just as a post or page might appear on the screen, and to work on any of them. Alternatively, a specified block area could be displayed on its own and worked on. At a very rough guess, it is likely to be mid-2020 before such a major change appears, always assuming that the idea is carried forward.
Auto-updating old versions (WordPress.org users). WordPress supplies security fixes back as far back as version 3.7, which was launched in October 2013. However, the effort required to support these old versions is an ever-growing problem. It is now proposed that, unless they deliberately opt out, old WordPress.org sites will be automatically updated (one version at a time) until they are on version 4.7. There has been much animated debate on this subject. It remains to be seen if the proposal will be adopted.
WordPress Version 5.2, was made available on May 7, 2019. In summary, the functional enhancements in this release are mainly aimed at WordPress.org users although work has also gone into improving the general block editor experience. The changes will be incorporated into WordPress.com shortly, where appropriate.
The Block Editor (aka
Another wodge of widgets now have block versions.They are: RSS, Amazon Kindle embed, search, calendar and tag cloud
In addition, a legacy widget block has been introduced. This will allow you to incorporate widgets that were developed for old WordPress (pre-version 5) into blocks. However, I note that it is described as “experimental” at the moment
The cover page block now acts as a container which can contain multiple blocks. For example, it may have three blocks: a title, a paragraph of text, and a button, as well as the cover image itself
Disabling / enabling blocks. This is called block management. It is probably aimed at WordPress.org users who have incorporated collection(s) of third-party blocks into their system. For example, they may have installed a collection of blocks that includes a gallery feature. They only want the gallery feature and are not interested in the other blocks. They can disable those unwanted blocks to reduce the memory requirement
Performance improvements, particularly reducing the time taken to load large posts / pages.
Site Health Project (WordPress.org
This is an ongoing project, principally for WordPress.org
users. WordPress version 5.2 includes Improved Fatal Error Protection which
aims to catch serious errors before they produce the “white screen of death”,
allowing a login to admin to potentially resolve the problem.
In addition, there are two new pages in the admin interface (under
tools) that allow you to check out the health of your site via a number of
This subject seems to trundle on and on! 5.6 is now the
minimum version of PHP that can run WordPress. However, as I have mentioned
before, the PHP people only support version 7.0 and above. Unless there are
mitigating circumstances WordPress.org users should be on version 7.0 or above.
WordPress 5.2 will not now be installed on your site if you
are not on PHP 5.6 or greater. This minimum version requirement is likely to go
up to 7.0 before the end of the year .. famous last words!
Similarly, WordPress will now check that any installed
plugin is compatible with the version of PHP that you have installed. If it is
not then the plugin will not be activated.
WordPress version 5.2 includes a lot of bug fixes and minor
changes, generally making the product more reliable, while ironing out some of
Other Recent Changes
The following items are not related to the version 5.2
release, per se.
If you use the
Calypso interface, you may have noticed that they have just changed the
layout of the menu system
form. I said some months back that there was no facility within
Wordpress.com to add a contact form in the new block editor. A form block has
now been added (not sure precisely when it appeared)
dashboard colour schemes are available .. if you are in to that sort of
Fyi – it
is no longer possible to purchase a
custom domain if you are only using the free plan. Individuals who
previously did so are not affected by this change.
My experiences with
the block editor
I have been using the new block editor on my own website
(bkthisandthat.org.uk) and on the Ascot Volunteer Bureau website since January
2019. I have found it to be stable. The current issues for me are:
Slideshows are not currently supported in blocks
The table block is not particularly satisfactory
at the moment (although there are workarounds)
The converter (from classic editor format to blocks)
annoyingly decouples an image and the adjacent text (where they are side by
side), although they can easily be re-coupled.
There is no pressure at this time for users to convert to
the block editor. As I said last time, it has been stated that the Classic
Editor will be supported until December 2021. Perhaps the end of this year may
be a useful time to assess the current state of play and possibly consider converting.
What is coming up?
Sidebars and footers.
It is important to realise that the implementation of widget blocks thus far
has been limited to their use in the main body of the screen. What has not been
mentioned is the use of widgets in sidebars and footers where we have
historically used them. WordPress has now issued a Blocks in Widget Areas RFC
(Request for Comments). This means that they have a draft design for handling
widgets in sidebars and footers, and they are asking for some feedback before
continuing. It may be late summer or autumn before any agreed design is
Navigation Menu. Work
continues on the Implementation of the navigation menu as a block, but it is
unclear to me where they are with this. They were struggling to agree on a
design when last I heard.
Block directory. As
mentioned earlier, third-party blocks are currently installed as plugins,
usually in collections that consist of multiple blocks. I get the impression
that this is seen as a short-term solution. There are design discussions on
implementing a separate block directory whereby they can be incorporated
individually into your site. This facility will be principally aimed at
There is a proposal to revamp it, using blocks. It remains to be seen if this
gets off the ground, and if so when. WordPress.com users who use the Calypso
interface will not be affected by this possible change. See
this post if you are unclear about the different WordPress.com dashboards.
Finally, a few words on this subject which deals with improving the experience of individuals with disabilities. Please be aware, if you are not already, that WCAG 2.1 (Web Content Accessibility Guidelines) was issued in June 2018. Public Sector bodies, including central and local government, plus some charities and some non-government organisations (not sure precisely what “some” means at the moment), must comply with these guidelines by September 2020. There are two strands that concern us:
Using WordPress itself. An accessibility audit on the new block editor has just been carried out. It was commissioned by a 3rd party outfit called WPCampus. The report finds various problems although it has to be said that the study was based on WordPress 5.0.3, and that work has been carried out in the area of accessibility since that release. I expect that further work will be undertaken in the coming months. I will monitor what happens here and report back
The website that you create. It is your responsibility to address WCAG 2.1 compliance if it applies to your organisation. I will relay any useful information that I hear. Obviously, I would appreciate any information that you may discover on the subject.
It is interesting that Automattic (the WordPress.com people)
have hardly mentioned Gutenberg, the new block editor. There has been no big
announcement for what is possibly the most far-reaching change yet made to WordPress.
To my cynical mind, this says that any big push to get users to adopt it will
not happen until they are confident that: it is stable enough; it contains all
of the functionality that is in WordPress 4; and their support mechanisms are
geared up to cope with a potentially increased workload, as people do migrate.
So, perhaps a useful strategy for WordPress.com users is to
wait until they do make a song and dance about it, before considering any
switch to the new block editor. You can stay where you are, simply by not clicking
on any invitation to switch to (or try out) the new block editor.
WordPress.org users who wish to play safe at this point in
time can either (a) not upgrade to WordPress 5 or (b) upgrade to WordPress 5
but install the Classic Editor plugin so that you do not have to use the new
A brief word on my own experiences. My main website lives on WordPress.com. I decided to adopt Gutenberg, the new block editor, in early January. There are a couple of bugs which affect me but I can work round them. I have not experienced any significant problems so far. I also look after a small, straightforward website for Ascot Volunteer Bureau. I converted it to the new block editor a month ago without problem.
My WordPress 5 FAQ Article
In lieu of any useful, concise material thus far on migrating to WordPress 5 (or not), I have penned this article to describe what options are available to users. It is in the form of FAQs. I will maintain and update it, as necessary, until such time as something better appears. Any questions or feedback on its content is welcome.
Latest WordPress 5 Releases
I had previously mentioned the 5.0.1 and 5.0.2 bug fix
releases which came out before Christmas. The focus in 5.0.1 was on security
fixes, while 5.0.2 included a range of performance fixes. 5.0.3
followed in early January, comprising 37 bug fixes and 7 performance updates.
WordPress 5.1 was released to WordPress.org users on February 21st, 2019, and will follow to WordPress.com users shortly. It is difficult to discern any particular focus other than attempts to polish the new block editor, and to make the software more error-free and robust. In addition to some performance improvements, the other item worthy of note is a site health check feature. This an ongoing project whose objective is to improve the stability and performance of WordPress. It is aimed at WordPress.org users. The first version was initially implemented as a plugin which has now been put into the core WordPress software. Further enhancements in this area will follow later this year.
WordPress.com users will probably have noticed a recent cosmetic
change which allows you to alter some colours on your dashboard. It seems to be
mainly for Calypso users, as far as I can see. Further
Finally, I note that a facility to copy a post or page has
appeared in the editor that is invoked via the wp-admin dashboard .. not before
time .. and it has reappeared (having disappeared for a while) in the editor
that is invoked via the Calypso dashboard.
Recent Queries on WordPress
This section contains topics that have been brought up
recently by individuals who receive these newsletters.
Shortcodes (I would call them macros, but I am an old geezer)
have been used to implement various features in WordPress. Examples include
contact forms, galleries and displaying recent posts. A full list of shortcodes
in WordPress.com can be viewed here.
A couple of people have experienced problems when trying to
edit or delete content that is implemented using shortcodes.
You need to switch from the visual view of the relevant post
or page to the text / HTML view. Shortcodes are encapsulated within
parentheses: consisting of the shortcode name along with a list of associated
parameters, e.g. email address and text boxes on a contact form. If you wish to
remove the entire shortcode then simply delete everything from [ to ],
including the parentheses.
The ease with which a shortcode can be edited varies.
Contact forms and displaying recent posts are relatively straightforward,
whereas galleries should be deleted and recreated from scratch.
Re the new block editor, each shortcode appears in a
separate block. Just remove the entire block if you wish to delete it. I get
the impression that shortcodes will eventually be replaced by specific blocks
that provide the same functionality, but who knows how long that may take.
Portfolios (of pictures)
This topic is relevant to individuals who have lots of
photos on a single post or page. I have spoken to a number of users who manage
(somehow) to squeeze lots of photos into a single post or page using the Twenty
Ten theme. Twenty Ten can still be used although it is no longer a supported
theme. At some point these users will have to change their theme. Hence these
WordPress.org users can find lots of plugins that provide
sophisticated gallery facilities.
WordPress.com users can use the portfolio option to display multiple photos. When it is active you have posts, pages and portfolio pages. There are various themes which make explicit use of portfolio pages. However, it is in fact possible to use the portfolio option with any theme although I would guess that the effectiveness (how good it looks) will vary from theme to theme. Read this WordPress.com support item for further information on portfolios and the themes which explicitly use them.
Notes on Changing Theme
Writing the above section has reminded me that I keep
meaning to pen some thoughts on the general topic of changing theme.
Beware that some or all of your current theme customisations
may be lost when you switch to a new theme:
Image. The main issue here is that the current image size may not be
compatible with the size that the new theme would prefer
areas. Obviously, if a widget area (say the left-hand sidebar) exists in
your current theme, but it does not exist in the new theme, then you may well
lose the widgets within it. Less obviously, a single widget area (say the
right-hand sidebar) may be lost even though the new theme also has a right-hand
sidebar – it depends on how aware the new theme is when it is activated
While your menu settings will almost certainly be retained, the new theme may
start off by using a default (perhaps empty) menu. You may have to tell it to
use your menu. The other possibility is that you may have to reconstruct your
menu(s). For example, the new theme may not have as much space as the current
theme (across the screen) to hold all the top level menu items. In which case
you may have to redesign your menus to fit in with the new theme, e.g. by using
where used, are theme specific. Any existing modifications will disappear in
the new theme.
It is good practice to make a note of your various
customisations before you change a theme. You can then re-apply them (except
for CSS), where necessary, in your new theme.
It is possible to make an image clickable. Two reasons to do
so spring readily to mind:
To link to another page, either on your site or
anywhere else on the Internet
To display a larger version of the image in
order to make parts of the image more distinct, or to make any text readable.
Note that the image displayed will be the size of the original version.
In edit image mode you will find a link option. To link to
another page or post, select Custom URL and enter the URL of the page. To
display a larger image, select Media (assuming that the original is in your
media library) and enter the URL of the image if it is not already displayed.
This applies only to WordPress.org users. In April 2019 the
minimum version of PHP that WordPress will run on will be PHP 5.6. However, as
I have mentioned before, version 5.6 is no longer supported by the PHP people.
Unless there are mitigating circumstances, you should be on PHP 7.0 or greater,
as they are the only versions that are currently supported by the PHP people.
The development of widget blocks appears to be proceeding
rapidly. However, the use of blocks for menus is not proving to be
straightforward, and no agreement has yet been reached on how it will be
There is currently no set date for WordPress 5.2, but it
seems likely that it will appear around the end of April. Similarly, there is
no agreed scope for it at the moment. Jungle drums indicate that it may
include: the first appearance of core widgets in blocks; further work on
polishing the new block editor; and improvements to the Site Health Check.
I refer to WordPress.com’s front-end dashboards at different times. This short item is simply to explain that WordPress.com has two different front-ends.
The original front-end to WordPress is invoked through the wp-admin dashboard. This is still the case for WordPress.org users and for older WordPress. com users. Here is an example ..
In 2015 Automattic, the owners of WordPress.com, introduced an alternative front-end, called Calypso. They will try to persuade you to use it rather than the wp-admin dashboard. They say that it is faster. I must admit that I have not found it so, and it is also missing some of the features that can be found on the wp-admin dashboard. Anyway, it is there and some of you may be using it. Here is an example of the Calypso dashboard ..
Some users may find that there is an option on the Calypso dashboard (probably at the bottom) to switch to the wp-admin dashboard if you should wish to do this. An alternative method, if this option is not shown, is to change the url by typing wp-admin after the domain name.
This set of FAQs is aimed at individuals who might describe themselves as modest WordPress users who may not have not been keeping up with the development of Gutenberg. It is not aimed at expert users.
I have penned it because I have not found a succinct summary of the options that are available to existing WordPress users of the TinyMCE editor (which has been at the heart of WordPress for many years) now that WordPress 5 and the Gutenberg editor (aka the new block editor) have been released.
I will maintain the information in this post until such time as somebody writes a better summary. Feedback on errors, omissions et cetera is welcome.
Prior to WordPress 5, the TinyMCE software was used as the editor. With the advent of WordPress 5 it is now generally referred to as the Classic Editor. I will use the Classic Editor term from now on in these FAQs.
What is Gutenberg?
Gutenberg is the name of the project which developed the new block editor in WordPress. In essence, all content is split into blocks; there are text blocks, image blocks, embedded blocks .. everything is a block. The first test version (0.1) of Gutenberg appeared in June 2017, and at the time of writing we are on version 5.3. The software was initially implemented as a plugin which WordPress.org users could incorporate into their sites to try out.
What is in WordPress 5.0?
In late 2018 Gutenberg was incorporated into the core WordPress software. This was a Major Major Major Major change (apologies for the frivolity – people of a certain age may know who he is!? .. no looking it up in a search engine!). Version 5.0 was released to WordPress.org users on 6 December, 2018, and WordPress.com users started to see it two weeks later.
Why does WordPress.com not mention WordPress 5.0?
Automattic, the owners of WordPress.com, tend not to mention versions of WordPress. They also tend to use the term “new block editor” rather than Gutenberg.
What if I do not want to install WordPress 5?
There is no reason why you have to install it. There may be valid reasons not to, e.g. you want to wait until you are confident that it is stable; or you may be using plugins that are not yet compatible with WordPress 5. Whatever the reason, there is no pressure at this time to move from WordPress 4 to 5.
Can I stay on WordPress 4 and just use the Gutenberg plugin?
This is not recommended. The plugin will continue to exist but it will be used in the development of Gutenberg V2 when widgets and navigation menus will be turned into blocks. So, it will not be stable, apart from possibly introducing unwanted effects.
What preparation do I need to do prior to installing WordPress 5?
The minimum preparation should be to check that your theme and plugins are compatible with WordPress 5.
What if I am happy to install WordPress 5 but I do not want to use the Gutenberg editor?
There is a Classic Editor plugin. If you install it, this will ensure that you continue to use the Classic Editor which will be supported until at least December 2021. At the time of writing, more than 4 million users have installed this plugin.
Do I have to convert all my content to Gutenberg?
This assumes that you intend to embrace Gutenberg and its features. It is important to realise that all existing content will be correctly rendered on your website without you doing anything. For example, there is no need to do anything with old posts that are never going to be altered. So, the answer is no.
How do I convert a post or page to Gutenberg?
When you open a post or page for the first time in the Gutenberg editor the content will be contained within a single block, called a Classic Block. This acts just like the Classic Editor with one or two exceptions. If you wish, you can keep it as a single Classic Block within Gutenberg. Alternatively, you can convert it into multiple native Gutenberg blocks. To do this, click on the three dots icon that is on the toolbar which is related to the Classic Block and select the “Convert to Blocks” option.
What if I want to mix and match the Gutenberg and Classic Editorson a per individual post or page basis?
This is not possible. Gutenberg will act as the editor unless you have installed the Classic Editor plugin. The only option within Gutenberg is to keep the post or page as a Classic Block, thus allowing you to edit it using the features of the Classic Editor.
What if I do not wish to install WordPress 5?
WordPress.com is a hosted service and you have no control over which version of WordPress that you use. You will be using WordPress 5, whether you know it or not.
What if I do not wish to use Gutenberg?
So long as you do not click on anything that encourages you to switch to the new block editor (or to try it out) then you will continue with the Classic Editor. It has been stated that the Classic Editor will be supported until at least December 2021.
Can I control which will be the default editor?
If you are a new user (post 19 December 2018?) then Gutenberg will probably be your default editor. If you are an existing user then the Classic Editor will be your default editor unless you switch to Gutenberg. At the time of writing this switch can be done in two places: in the panel at the top of the editor screen which is invoked via the wp-admin dashboard; or in the three dots settings options (top right-hand corner of the editor screen) if you are using Calypso.
Can I switch back to the Classic Editor?
Yes. However, beware that there are no guarantees that any block editor features that you may have used (and saved) will work with the Classic Editor.
The switch option can be found in the Gutenberg editor screen by clicking on the three dots icon (near the top right corner of the WordPress window). The “Switch to Classic Editor” option is at the bottom of the list. Beware that this option may be hidden (off the bottom of the screen) if the window size is too small or the font size in use is too large to display all the options in the list. If it is hidden you can now (from WordPress 5.3) scroll down the list. This was previously a bug which I had reported.
Can I mix and match the Gutenberg and Classic Editors on a per individual post or page basis?
Yes if Gutenberg is the default editor and you use the wp-admin dashboard. It is not currently possible if you use Calypso. In the wp-admin dashboard:
creating a new post with the Classic Editor. Do not click on add post in the wp-admin dashboard, as that will bring up the Gutenberg editor. Click All posts instead, and select Classic Editor from the Add New dropdown box at the top left of the screen (as shown on the left).
If you are editing an existing post and Gutenberg is the default editor then clicking on the name will bring up the Gutenberg editor. However, hovering on the line below the name will display various options, including the Classic Editor, if you want to use it rather than Gutenberg. See the screenshot below.
Do I have to convert all my content to Gutenberg?
This assumes that you intend to embrace Gutenberg. It is important to realise that all existing content will be correctly rendered on your website without you doing anything. For example, there is no need to do anything with old posts that are never going to be altered. So, the answer is no.
How do I convert a post or page to Gutenberg?
The process is slightly different, depending on whether you are using the wp-admin dashboard or Calypso.
Wp-admin dashboard. When you open a post or page for the first time in Gutenberg the content will be contained within a single block, called a Classic Block. This acts just like the Classic Editor with one or two exceptions, e.g. there is no insert contact form option. If you wish, you can keep it as a single Classic Block within Gutenberg. Alternatively, you can convert it into multiple native Gutenberg blocks. To do this, click on the three dots icon that is on the toolbar which is related to the Classic Block and select the “Convert to Blocks” option.
Calypso. When you open a post or page for the first time in Gutenberg you will get a message asking you if you want to convert the content to blocks or not. If you answer in the affirmative then the conversion will be done. If you click on cancel the content will be displayed as a single Classic Block, and you will have the features of the Classic Editor. You can convert it into multiple native Gutenberg blocks at some later date if you wish. To do this, click on the three dots icon that is on the toolbar which is related to the Classic Block and select the “Convert to Blocks” option.
Do I need to check the results after I have converted a post or page into blocks?
Yes. It may be necessary to do some manual changes. What follows is a list of issues that I have discovered with the converter. It is obviously not meant to be a comprehensive list, and some of them may disappear as (and when) changes are made to the converter:
images will probably need to be resized
slideshows on WordPress.com did not get converted in 5.0. I do not know if this is still true. If it is then you will need to recreate your gallery. Note that there is now a slideshow block which you will find in the Jetpack list of blocks.
any handcrafted HTML tables are converted to table blocks. However, beware the following
images in table cells are not supported
each column is the same width which may not be appropriate
empty cells are not converted, and can screw up (technical term) the appearance of the table.
if you have an image alongside text you will probably find that they have been decoupled, i.e. the text appears underneath the image. To couple them, align the image to the left or right depending on which side you want the image to reside.
Please contact me if you have any queries. I would also appreciate it if you could let me know if you discover any information which is now out of date.
Sorry to write another newsletter so soon but there is a lot
going on. Version 5 has been available for WordPress.org users for two weeks,
and there have been two bug-fix releases so far. WordPress.com users appear to
be just catching sight of it now.
There have been two bug-fix releases of WordPress V5 so far:
5.0.1 (released on 13 December, 2018) focused on
security fixes. They have also been applied to previous versions of WordPress, back
as far as 3.7
5.0.2 (released on 19 December 2018) focused on
performance improvements. There were 73 bug fixes.
5.0.3 has a target date of 9 January, 2019. Note that if you
have installed V5 and have the auto update facility enabled then these bug fix
releases will be installed automatically.
The plugin directory now contains a section at the beginning
for block-enabled plugins. There is talk of putting them in a totally separate
It looks as if WordPress V5 has just started to reach WordPress.com. If I sound not altogether confident, that is because Automattic never mentions versions of WordPress, nor do they mention Gutenberg (it is simply called the new block editor). The reasons for my claim are:
The appearance of new invitations to switch to the new block editor. The old invitation to try out Gutenberg which appeared on the main dashboard has now disappeared. If you use the dashboard to invoke the editor then this new invitation appears across the top of the screen when you go into edit post or page. If you use Calypso it appears in the right-hand sidebar within the editor. Beware that if you do make the new block editor your default editor there is no way to switch back at this moment
Twenty Nineteen, the new default theme which uses Gutenberg, has now been made available to all WordPress.com users.
I said in the last newsletter that there appeared to be no
way in Calypso to invoke the classic editor for a specific post / page if you had
set Gutenberg to be your default editor. I now see that the more settings
button within the Gutenberg editor (3 dots icon top right) has a feature which
allows you to switch to the classic editor for the currently opened post /
The bottom line for WordPress.com users is .. if you want to continue with the classic editor, as least for the moment, do not accept any invitation to try or switch to the new block editor.
There is talk of version 5.1 in late February although it is
not clear to me precisely what the scope of this release will be, other than
more bug fixes and a PHP upgrade notice for WordPress.org users.
Gutenberg V2. General design ideas are being kicked around for the implementation of widgets and menus as blocks, which will happen later in 2019. The Gutenberg plugin will remain in existence for WordPress.org users to test these changes.
This newsletter focuses on the options that will be available to WordPress users when version 5.0 is launched. As some of the options are not yet set in stone for WordPress.com users, I will, if necessary, re-issue this newsletter when they eventually become crystal clear. These items are in red in this issue.
There have been five beta versions so far, and we are currently, at the time of writing, on release candidate 3. The general opinion is that it is not ready for release. In the November 2018 newsletter I said that the target launch date was November 27th, 2018, and that if it was not met then it would be put back to January 22nd, 2019.
Well, we have passed the first target date, but all the signs are that Mr. WordPress is intent on reneging on the backup date, and is pressing ahead to release it as soon as possible despite the clamour to delay it. Hence, I am writing this newsletter now rather than waiting for some unknown surprise date. In fact, I have just found out this morning that December 6th, 2018 is the new target date.
Some reported bugs are already being put on one side for resolution in 5.0.1 or later. These are the bug-fixing releases which may appear fortnightly.
I will cover the options for WordPress.org users and WordPress.com users separately. In each case I will mention the following topics: the installation of version 5.0; the default editor; and the choice of editor for individual posts / pages. Note – I will simply use the term post from now on rather than say post / page each time. Suffice it to say that where post is mentioned it also applies to page.
Options for WordPress.org users
As version 5.0 is a major release, you can decide whether to install it or not. You may sensibly decide to delay it until you are ready and you are confident that it is reliable. If you do propose to install it please ensure that any plugins that you use will work with version 5.0. As an aside, if you want better control of WordPress updates there is a popular plugin called Easy Updates Manager (over 200K activations) which you might check out.
You can disable the new Gutenberg editor in version 5.0 by using the Classic Editor plugin (or optionally the Classic Editor Addon plugin). This will allow you to continue to use the existing editor which will be supported until at the least the end of 2021.
If version 5.0 is installed and the Gutenberg editor is enabled you can still use the old editor for individual posts:
creating a new post with the Classic Editor. Do not click on add new post in the wp-admin dashboard, as that will bring up the Gutenberg editor. Click All posts instead, and select the appropriate editor from the dropdown box at the top left of the screen.
If you are editing an existing post and Gutenberg is enabled then clicking on the name will bring up the Gutenberg editor. However, hovering on the line below the name, as shown underneath, will display various options, including the Classic Editor, if you want to use it rather than Gutenberg.
Options for WordPress.com users
WordPress 5.0 will be installed. Unlike WordPress.org users, you have no say in the matter. There is a question mark, as to when this will happen. A sensible approach would be for them to launch it gradually to groups of users .. but who knows!
Enabling / disabling Gutenberg. At the time of writing, the majority of WordPress.com users can choose to try out Gutenberg or not on 4.9.8 (the current version of WordPress). However, There is no information on whether a similar option will be made available in 5.0, e.g. enable Gutenberg (or not).
Choice of editor for an individual post. There are two ways to use WordPress, via the original wp-admin dashboard or via the more recent Calypso front-end.
If the Gutenberg editor is enabled you can still use the Classic Editor for individual posts:
creating a new post with the classic editor. Do not click on add new post in the wp-admin dashboard, as that will bring up the Gutenberg editor. Click All posts instead, and select the appropriate editor from the dropdown box at the top left of the screen.
If you are editing an existing post and Gutenberg is enabled then clicking on the name will bring up the Gutenberg editor. However, hovering on the line below the name will display various options, including Classic Editor, if you want to use it rather than Gutenberg.
This alternative front-end was introduced in 2015. WordPress.com will try to persuade you to use it rather than the wp-admin dashboard. They say that it is faster. I must admit that I have not found it so, and it is also missing some of the features on the dashboard. Anyway, it is there and some of you may be using it. The accompanying image shows the top level menu for Calypso.
At the time of writing, there is no ability to choose the editor for a post. If Gutenberg is enabled you get the Gutenberg editor. If it is not enabled you get the Classic Editor. I guess that this may change in WordPress 5.0. We will have to wait and see.
The classic block. When you edit a post or page with Gutenberg for the first time the content will appear as a single classic block. You can retain this format if you wish. The formatting icons will effectively give you the same facilities as can be found in the Classic Editor. However, if you are happy to fully embrace Gutenberg then you can convert the content into multiple native Gutenberg blocks.
Switching Editors. If you go into the Gutenberg editor by mistake then simply exit it. If you have saved a post or page in the Gutenberg editor, and then you subsequently decide that you wish to revert to the Classic Editor, a message will inform you that some formatting may be lost in the process. So, beware.
If you do not want to read the detail that follows then the
latest information can be briefly summarised as follows:
The major news is that the launch of WordPress 5.0 (the Gutenberg release) is currently set for November 27th, 2018
If this date is not met (and my money is on it not being met) then the launch will be put back to January 22nd, 2019
There is talk of subsequent minor releases every fortnight initially to fix bugs .. 5.0.1, 5.0.2 et cetera
My confidence in the reliability of WordPress 5.0 when it is eventually released has taken a nosedive in recent weeks. I plan to continue to use the current editor until such time as I consider that the dust has settled
It has been announced that the Classic Editor (i.e. the current editor) will be officially supported until at least the end of December 2021
WordPress.org users should be using version 7 of PHP from January 2019, as version 5.6 will no longer be supported after December. Version 7.3 is due to be released shortly but it should not be used until WordPress announces that it supports it. 7.0, 7.1 and 7.2 are ok.
The WordPress Rollercoaster
I previously said that version 4.9.9 would be launched in
early November, and that it would focus on preparing the way for 5.0 (the
Gutenberg version). This sensible approach (to my mind) was abandoned. The
pressure to get Gutenberg out as soon as possible resulted in a change of plan.
Work on version 4.9.9 was halted almost before it got started and all the focus
was switched to version 5.0.
The WordPress version 5.0 project is being led by MattWullenweg (Mr. WordPress himself), a sure indication that he is determined to launch it ASAP. Quite a few people were convinced that he wanted to make the big announcement of its arrival at Wordcamp US, a conference which takes place in early December. You can read his “plan” here. The initial target date for the release was November 19th, 2018.
Beta versions of 5.0 have been around since October 24th (beta 4 is due out today). However, significant bugs have been found, leading to general cries for a delay. Another factor has been a big hoo-ha on the subject of accessibility in Gutenberg, i.e. the ease of use for individuals who require assistive technology. The target date has now been put back to November 27th. If that date is not met the launch will be delayed until January 22nd, 2019.
Latest Gutenberg Information
Gutenberg 4.3 is the latest release. In theory, the development of new features in Gutenberg was halted around early July. In practice, new items continue to be added. I will mention just a few of them.
There has been much criticism that the Gutenberg user interface “gets in the way” of free-flowing writing. A number of features have been introduced to placate these critics:
The positioning of the toolbar which relates to the
current block just above the block was one particular dislike. A unified toolbar option now allows
you, if you wish, to position the toolbar at the top of the screen instead.
mode is another new option. When set, it greys out all blocks except the
one that you are currently working on.
Thirdly, there is a full screen mode. This removes the dashboard items on the left of
the screen. So, not actually full screen but simply a larger area.
I feel sure that further changes are likely in this area,
and indeed to the general user interface which has come in for some stick.
Classic block – insert media button
I had previously mentioned that there was no insert media
button in this block. This has now been rectified. However, there is still no
insert contact form option. If you need to insert a contact form you will have
to use a shortcode to do so. See the contact form
support item for further details. Note that existing contact forms
will continue to work OK.
Multiple reusable blocks
The reusable block which was introduced some time back was somewhat
limited in its usefulness. It has now been extended. Multiple blocks can now be
exported and subsequently imported elsewhere.
Media and Text Split Block
As the name implies, it allows you to have text alongside an
image. I do not like the initial implementation: there are no facilities to
vertically align the image within the block; and the text does not wrap round
underneath the image. I will monitor it to see if any changes are made to the
My Experiences with Gutenberg on
As a WordPress.com user, I decided to act as a guinea pig in
late September and try out Gutenberg on my bkthisandthat.org.uk website.
My main objective was to ensure that my existing content would work with
Gutenberg. I currently use the Independent Publisher 2 theme which is aimed at
people who want a simple theme where the word is king. Here
is the link to my feedback in early October if you have not seen it.
It was moderately upbeat in tone. However, I had another
play with Gutenberg recently and immediately hit a problem which was not there
before. Converting a post / page to Gutenberg resulted in all images being
duplicated! The problem has not been resolved at the time of writing. Hence, my
current mood is somewhat downbeat, given that this is such a basic item of
On the plus side, the problem with pasting content from Word into Gutenberg seems to have been resolved.
How to control which editor you use
I do not know! There is still no news on this front. It is said that Gutenberg will be the default editor. Question – will we be able to specify the Classic Editor as the default? There is talk of making a link to the Classic Editor plugin available on the WP Admin dashboard. However, it is not clear if it would only apply to WordPress.org users. The phrase “we are considering” keeps appearing on this general subject. It seems obvious to me that they want people to use Gutenberg, and will only allow them to specify the Classic Editor as the default if they absolutely have to .. and that they will not make a decision until the last possible moment.
The current set up in WordPress 4.9.8 is that if Gutenberg
is activated then it is treated as the default editor when posts / pages are
accessed via the WP-Admin dashboard. However, there is an option on the second
line (underneath the name of the document on the all posts/pages directory
listing) to select the Classic Editor instead.
This item is only relevant to WordPress.org users. WordPress server-side code is written in the PHP scripting language, of which there are various versions. Although WordPress will work with PHP 5.2, that version has not been supported for some time. The minimum version which is currently supported is 5.6 but support will also cease for that at the end of December.
Version 6 of PHP never officially appeared, so that means
that you should really be on version 7 in January 2019. There are currently
three versions: 7.0, 7.1 and 7.2. In addition, version 7.3 is due to be
available in mid-December although it should not be used until WordPress
announces that it supports it.
You should check with your ISP or support person as to what
version of PHP you are currently using, and then arrange to be on some variant
of version 7 if you are not already using one of them.
New default theme.
If you have used WordPress for two or more years then you will know that
Automattic was in the habit of producing a new default theme annually, usually
around December time. There was no new theme last year, presumably because the
emphasis was on Gutenberg’s development. However, it has been announced that
there will be a new theme to accompany WordPress 5.0, unsurprisingly called Twenty
Nineteen. Also unsurprisingly, it will be a Gutenberg theme!
Support for the
Classic Editor. There has been a fair amount of clamour for information on
just how long the Classic Editor will be supported after Gutenberg has been
launched. It has recently been announced that the Classic Editor will be
officially supported until at least the end of December, 2021.
plugins. I have been asked to explain the difference between the Classic
Editor and the Classic Editor Addon plugins for WordPress.org users. The
Classic Editor plugin currently has over 500,000 activations, so obviously
quite a few people want to stick with the current editor, at least for now. However,
it is still possible to inadvertently activate Gutenberg. This is a potential
problem for any site where more than one user has administration rights. The
Classic Editor Addon plugin installs the Classic Editor plugin and then removes
all mention of Gutenberg from it. The bottom line is that they are both effectively
doing the same thing; it is just that the Classic Editor Addon adopts a safety-first
approach to avoid any accidental activation of Gutenberg.
Activity is a new feature on WordPress.com. It logs details of changes on your site which you can browse. It sounds as if people on the free plan will be able to see the last 20 items, while those on paid plans will see items from the last 30 days. There are various plugins on WordPress.org which can provide logging information for those users, the most popular being Activity Log.
Beyond WordPress 5.0
Plans are already taking shape for subsequent versions.
As mentioned, there will obviously be room for bug-fixing
releases in the early days .. 5.0.1, 5.0.2 et cetera.
The next stage of Gutenberg development will minimally
include the following: widgets will become blocks; there will be menu
navigation blocks; and nested blocks will be supported. Quite what else may
appear in block form in the short to medium term is not yet clear, at least not
Also, expect changes / new functionality in the areas of
privacy and accessibility.