27 Comments

  1. Fas

    Interesting evolution that is having WordPress, little by little.

    Report

  2. Andre

    This is what drives me nuts…designing themes for both the Classic editor and the block editor, only to later find out things were completely changed.

    Then there is the issue of trying to get the front-end styles into the block editor is an absolute nightmare (I often invent new swear words). For example, try changing the main content font size when the block editor is loading its own CSS in the footer area; overriding what you try to do.

    Styling for the classic editor is a breeze! If the dev team can find a way to make it as easy as the classic editor, I would be happy as can be!

    The dev team makes these changes that will affect millions of users who have themes (and plugins) which need updating constantly is taxing. I feel sorry for the theme authors/shops that have a LARGE portfolio of themes and plugins that were updated for GB compatibility. Luckily, I’m keeping mine limited…less overhead when it comes to constantly changing and updating themes.

    Report

  3. Matt

    Thanks for this heads up…For sites running the default WP 2020 theme, I assume these are all tested. Any thoughts on this?

    Report

    • Andre

      I’m working on a theme using TwentyTwenty as the foundation and have been doing it on WP 5.4 beta3 (now RC1). So far, I haven’t encountered anything of an issue; the exception was that they had the HTML tag as fixed on mobile view (not sure why) in beta2, but I posted it on GitHub (fixed now). Had to make an adjustment to the calendar widget though.

      Report

  4. Leonardo Losoviz

    A tip concerning the new @wordpress/block package: it supports hot reloading! With it, whenever making a change in the block’s javascript file, the page is automatically refreshed, which greatly speeds up development.

    It doesn’t mention how to enable it in the package’s documentation, so here it goes: Add a script with src http://localhost:35729/livereload.js, like this:

    if (defined('ENABLE_HOT_RELOADING_FOR_DEV') && ENABLE_HOT_RELOADING_FOR_DEV) {
      wp_register_script('livereload', 'http://localhost:35729/livereload.js');
      wp_enqueue_script('livereload');
    }

    And add define('ENABLE_HOT_RELOADING_FOR_DEV', true); to wp-config.php

    Report

  5. Bikram

    What about the Classic editor theme development. Is it still a thing or dead? Last year I had built 2 themes for my site but never released them. Block editor held me back.

    Report

    • Justin Tadlock

      The only thing related to themes that don’t add block styles is the calendar widget.

      As for whether such development is dead, it is not completely. It really depends on whether you still want to add a custom stylesheet for the classic editor, and nothing has changed in that regard. At this point, you really should be creating styles for the block editor with themes for public release, even if still supporting classic.

      Report

  6. trapti agrawal

    Could someone please confirm that the image file upload issue which was occuring post 5.3 update is fixed or not.

    Report

  7. Francisco Rojas

    What’s about to make changes to improvements the mobil and desktop upload to avoid slow pages, sites and landing pages…?

    Report

    • Justin Tadlock

      The loading speed on the front end depends on a number of factors. The first and most important is the theme that you use. The second most important factor is what plugins you are using. Many will load additional scripts and styles on the front end.

      This is a much larger topic, which is also specific to individual sites, than what we can realistically dive into here in the comments. There are many friendly volunteers who can help over at WordPress support.

      Report

  8. Anh Tran

    Great improvements for the block editor. But I think the breaking changes are bad. Imagine a lot of themes will need to update because of the CSS change.

    Report

  9. Claas Meyer

    What about releasing Gutenberg after it has been finished?

    These ongoing rolling updates in millions of live websites with breaking changes cause millions of hours mostly unpaid work for small agencies and help-a-friend webmasters. These guys will find out about these changes only after the websites is broken because probably very few of them read any announcements or development blogs or notes or issues or release candidate notes.

    Report

    • Derin Tolu

      Just to play devils advocate…when was the last time anyone finished creating software? I don’t believe anyone develops like that anymore do they??

      Report

  10. Nick

    I think social icon block is really helpful for developers and we can simply add icons without the need for any additional plugin. But, Can someone confirm if we can add them to widgets or not? Or they can only be added to posts and pages?

    Report

    • Justin Tadlock

      Widget support for blocks, such as social icons, is currently experimental. If you install and activate the Gutenberg plugin, it has an “Experiments” settings page that allows you to enable widget support. Eventually, it will be possible to add blocks pretty much anywhere, but core WordPress isn’t there yet.

      Report

  11. Guido

    Thanks for this. The core tickets can be difficult to understand for people that are not full stack developer, such as myself. So your post is very helpful to me.

    Report

  12. Sebo

    actually I feel apply_shortcode not semantically correct either. If I “apply” something to an object I would rather consider it a state change but not necessarily expect something to be returned. Hope this makes sense.

    Report

  13. Shari L Smith

    I am so disappointed in WP for all this mess in something that used to follow clean efficient code practice. The entire reason I chose WP originally. Content is NOT style. Style is NOT content.

    Report

  14. Benjamin Intal

    …[authors] who have directly targeted specific editor classes, will need to check their block editor styles.
    [developers] can easily feel like they are fighting a losing battle.

    👆This.

    Report

  15. Jim S Smith

    And THIS is only one of many reasons why I hate having to update to the next major versions or sub-versions repeatedly. Nothing more unnerving than having to go back through tons of code and scripting, all to find out what was broken and when.

    I fondly remember the days when WordPress used to be much lighter weight, and loaded webpages very quickly. Now, it seems we get a lot of “gotchas” when it comes to more of these major changes. I sometimes wonder if some of the members of the development team really think about the effects of some of those changes sprung on the community?

    Report

  16. prjmarket

    You dropped one big change in WordPress 5.4. WordPress announced that WordPress 5.4 may feature image lazy-loading by default. This feature will enable the “loading” HTML attribute on all IMG elements. WordPress publishers will no longer need to use JavaScript or third party plugins for lazy-loading their images.

    Report

  17. Emily Anniston

    Thanks for sharing this. I still wonder is there any updates for mobile upload and display? Plus, I hope the update for extra theme features won’t mess up with all the saved ones.

    Report

  18. Federica Sibella

    Hi there,
    I wonder if the bug related to PDF preview was eventually solved in 5.4 (https://core.trac.wordpress.org/ticket/48853). It is quite a big issue for developers! Thanks.

    Report

  19. Jesse K

    When will the team fix the burning dumpster fire that is WP_User_Query ? Wish Guttenberg wasn’t eating up all the dev oxygen right now.

    Report

Comments are closed.

%d bloggers like this: