32 Comments

  1. André Mácola
    · Reply

    Hated the new UI styles for borders. Need to be softer and smooth

    Report

  2. Irfan
    · Reply

    “..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

  3. Glenn Martin
    · Reply

    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

    • Lynn
      · Reply

      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

  4. Samuel Lavoie
    · Reply

    Seems like a solid 5.x release that should bring over people reluctant to the Gutenberg way of life (?). 😃

    Report

  5. Gary Taylor
    · Reply

    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

  6. Antony
    · Reply

    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

  7. Roger
    · Reply

    About time Rahsaan got some love!

    Say a little prayer
    https://www.youtube.com/watch?v=k_avUwlyW6I

    Volunteered Slavery
    https://www.youtube.com/watch?v=-6ryVryFnEY

    Hat-tip to Matt for the righteous dedication.

    Report

  8. Aleksandr Samokhin
    · Reply

    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

  9. Gustavo Rodrigues da Silva
    · Reply

    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

  10. Josef
    · Reply

    I just tried this version and really liked the New Default Theme it has to offer. Looking forward to more updates.

    Report

  11. Anmol osm
    · Reply

    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

  12. Immanuel
    · Reply

    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

  13. Marcus Tibesar
    · Reply

    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

  14. Francesco V.
    · Reply

    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

    • Milan Petrović
      · Reply

      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

    • Glenn Martin
      · Reply

      Yes, this is a known issue being addressed here: https://core.trac.wordpress.org/ticket/48623

      Report

    • Andrey Savchenko
      · Reply

      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

      • Isabella

        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

      • Andrey Savchenko

        It appears that lots of plugins and themes are using this code in one form or the other.

        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.

        Why is there no “deprecated” notice at least a few month before such a breaking change?

        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.

        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.

        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.

        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.

        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).

        Something went pretty wrong with this commit, sorry to say.

        Certainly did, I very much would have preferred that permalink breakage was caught before release.

        Report

  15. daninhbinh
    · Reply

    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

  16. Ben Bradley
    · Reply

    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

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: