1. Carolina
    · Reply

    My gut says this should have been solved and considered when the Customizer menu item was removed. -And not postponed to a moment when the contributors have four weeks to merge the site editor, build the theme and EE -Everything Else. It is going to be a very hectic time.

    I believe the way forward is to use the editor components to create a new settings page, but I don’t know if the components or the developers are ready for that.


    • Gabriele Grüner
      · Reply

      It is going to be a very hectic time.

      Yes, clients who simply wanted a website a while ago will start to ask why even stay with WordPress at this point, when there suddenly are bills for things which they never ordered.


  2. Drivingralle
    · Reply

    For years the it was advised to add visual settings to the customizer. And it was the right thing in my opinion.

    Now that there is something new in development. That is not even fully worked out and stable for a few month/versions so that developers could have time to adjust there (free/open) products to it. Suddenly the core is so arrogant to break all other developers stuff with full intention.

    WordPress celebrates itself for being backward compatible. This does not mean just the source code.
    From the Philosophies “Design for the Majority” also means to have a majority of developers in mind that have build on top of WP. Not all developers have the time to adjust there plugins and themes everyday to the latest Gutenberg changes.

    Because the core team is to lazy or ignorant to build a off ramp from customizer to FSE the solution is to offload the work to hundreds of support staff? Creating thousands of (unpaid) hours of work/communication. Something that could be prevented by putting in a few hours of development work.

    In stead the settings inside the customizer that have moved to FSE could show a notice and a link to the new place. Something well build software does like WooCommrece with there change of coupon menu location.

    Have we not learned anything from 5.0?
    Do we need another “Classic *” Plugin to fix the narrow view of the core development team?


  3. Steve Grant
    · Reply

    I know this is slight tangential but I really wish there was a different approach to the redevelopment. I wish they’d finish one part off before starting another massive upheaval.

    Currently we are in a transition toward FSE and new kind of template system, which will be great when it’s finished but lets be honest no developer with a big client site going Live in the next month has built it with a FSE theme. It’s not “there” yet.

    So – We create a site in August 2021 and deliver the site 1st November 2021. It uses PHP templates, because FSE and Gutenberg menus are in flux.

    We educate our clients to use Gutenberg to lay out their posts (rather than pasting tables in from Word Docs!) and we show them the Group and Column features and we say “please use this to put your picture in a block with text”. And the client tries it, and they ask questions like ” how di I increase the gaps between columns, I can see padding but not MARGIN”

    So we developers to try to explain:
    “well, that requires the new theme WP system to activate both margin and padding in Gutenberg – and theme.JSON is needed to activate the option, and we tried incorporating theme.JSON but it is not compatible with your theme because theme.JSON takes precedence over the … well, let’s just say it broke everything, it’s all in flux right now but WP team are apparently going to nail it by November this year at which point we can start to fix your new site….”

    And the client says “why doesn’t wordpress ever work simply, can’t we use something else?”.

    And we developers say “Oh it will work eventually, it will be AMAZING one day. And some good news – before they get the editor issues resolved they have already started changing how you will update menus, and styles, and layouts too”

    And the client says “That sounds like more confusion and problems!! So when will that happen, surely that’s years away … will it work OK on our site?”

    and we say “In November 2021 everything I did in September 2021 will become incompatible, or legacy, and there will be more forks and bug chasing – and no it will not work”

    And the client says “but why didn’t you build the site in FSE / Theme.JSON in September” and we say “because as I looked at the development state of FSE I began contemplating a new life as a wood carver, deep in the forest. A good honest reliable job, something with material continuity, reliability, stability “


    • Matthias Baier
      · Reply

      My thoughts too…
      I’m constantly busy with fixing stuff, I coded before and now there’s a Gutenberg-button for what I had coded and it either overrides my stuff or the button doesn’t work. Both is distracting for my clients.
      I tried out FSE for a small project but ultimately abandoned the block-theme-approach, because the warning banner was more confusing than did help.
      I wish they would give it more time. But it happened with Gutenberg and it will happen with FSE. Merry Christmas! :-) At least, I know, sites will not break with 5.9.


  4. Jonas
    · Reply

    As a normal user, I am relaxed about the matter. Either I use an “old” theme. Then nothing seems to change. Or I’ll start over with a block theme, then I won’t miss the customizer. I have not installed a plugin on eight websites that is hooked into the customizer.
    But I also understand the concerns of theme and plugin developers.


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: