For a very long time that has been a check box available in the editor that allows the email notification from Subscribe2 HTML to be suppressed on a per post level. WordPress calls this box a `meta box`.
tl:dr; – The Override checkbox needs updating for the new `Gutenberg` editor – where should it go?
With the new editor (code named Gutenberg), these meta boxes are supported but conversion to new code is highly recommended (although not well documented!).
So, I’ve been looking at how to migrate to new code, particularly because if the current checkbox is ticked and the post then immediately published, the email goes out due to the order in which processes are triggered in WordPress and Subscribe2 HTML (a work around for now is to ensure you save the post before clicking the Publish button).
The possible locations for the checkbox are a `Block` or a `Sidebar menu`, and there are drawbacks to both over the current position.
With a Block you have to manually add it to a post and then check the box. Also, blocks are intended more to reflect the content of a post, but it does work this way. It would look like this:
The other option is a sidebar menu, this seems a more sensible place to put the checkbox. The drawback is that design decisions in Gutenberg mean that the sidebar can be ‘unpinned’ which remove the email icon from the top row. You then have to know to restore it using the sidebar more menu. This is how it would look:
And the Plugins section in this menu would be unticked and need clicking to restore the item after being unpinned.
So, the main reasons for this post, were do you think the override should go in the next release of Subscribe2 HTML? And thanks for reading this far 🙂
I’m sure you’ve all noticed in your WordPress admin areas that WordPress 5.0 has been released. As far as I can tell the current version (11.3) of Subscribe2 HTML works just fine in the new version.
You may have also noticed that WordPress 5.0 seems to be one of the most controversial and divisive versions of WordPress in many years, the new Editor seems to be loved or hated with few taking the middle ground. As such a Classic Editor plugin has been made available with WordPress 5.0 to restore the old editor look. Again, Subscribe2 HTML works just fine with this too.
Finally, some are very upset with the direction of WordPress 5.0 and they have forked the code and created ClassicPress. While this code is still reported as being in beta testing it seems to be a clone of WordPress 4.9.8. And yes, you’ve already guessed, Subscribe2 HTML works just fine here as well.
Subscribe2 HTML remains fully supported on WordPress and I’ll aim to keep it working in ClassicPress now too. 👍
The next version of Subscribe2 HTML is coming with a ‘block’ that will work with the Gutenberg editor project. There may be some useful information below for other plugin developers too.
Back in 2017 the team behind WordPress decided to spend some time developing the editor, noting that it had remained pretty much unchanged for several years while other areas of WordPress developed at a pace, it was deemed in need of some tender loving care. The project was dubbed Gutenberg.
I have been spending some time testing Gutenberg to ensure that Subscribe2 HTML will continue to function when the planned release of WordPress 5.0 (no date for the yet) lands in your update page. The good news is, to date I have not noticed any differences in the way WordPress and Subscribe2 HTML work together despite the massive code differences in the editor background and the significant visual changes you’ll see in the editor.
In the next version of Subscribe2 HTML you will get a Gutenberg ‘block’. The ‘block’ is fundamental to the design and functionality of the Gutenberg editor. And Subscribe2 HTML now has a block to insert the Subscribe2 HTML shortcode and configure parameters from in the editor.
You can call the script from the command line: php -f ./pot-helper.php textdomain output-file.php input-file1.js input-file2.js
Or call it using grunt by including grunt-shell in your package.json file and adding the necessary configuration in your Gruntfile.js.