I wish WordPress would wake up and get rid of Gutenberg.

  • I wish WordPress would wake up and get rid of Gutenberg.

    I don’t know who they think they are designing this block editor for. It’s one thing to make something optional. It’s another to muck up everything in WordPress by forcing it into the 2022 theme. If WordPress wants to get into the block editing business, then create it as a plugin and leave it at that. I had just installed a new site and used the 2022 WordPress theme (which was the default) and was like, what’s going on?? Where did everything go under the “Appearance” section?? I was really, really annoyed at how long it took me to figure out that the 2022 theme itself was causing the problem.

    IMPORTANT NOTE:
    Dear WordPress, make Gutenberg a plugin so those that want these features can have them, those that don’t can use a different builder (if desired), etc. And don’t create your “default themes” to mess up the standard WP functionality. I really wish you would take a survey before continuing down this path. I think you’d be surprised at the response you’ll get. And if I’m mistaken, then I’ll gladly shut up. But I think if you would survey all of your current users of www.ads-software.com, you’ll find that most people are not in favor of being coerced into using Gutenberg as the primary WP editing system. I realize this is just my opinion. But again, a survey would be a great way to ask for feedback and I’m sure we’d all love to see the survey results.

    — Gary

Viewing 3 replies - 1 through 3 (of 3 total)

  • Thank you for sharing your review @garymgordon.

    I am seeing that your comments sit somewhere in between Gutenberg, Full Site Editing and the TwentyTwentyTwo theme itself. It might be a good idea to move some of that feedback to the TwentyTwentyTwo review section but for the sake of simplicity, I will just reply here.

    It’s another to muck up everything in WordPress by forcing it into the 2022 theme.

    You probably know this already, but it is possible to opt-out of Gutenberg completely by installing the Classic Editor plugin.

    That being said, I would be curious to know more about your experience using Gutenberg purely as a post/page editor (as opposed to a the Global Site Editor). Do you see any advantages to using blocks? Do you feel there are any specific areas where it could be improved?

    Where did everything go under the “Appearance” section??

    Again, I feel that you probably figured this out by now but the way Full Site Editing works, once you activate a FSE theme such as TwentyTwentyTwo, all the options that used to be under Appearance > Customize are moved to the the Appearance > Editor. If you prefer the older workflow, you can switch back to a non-FSE theme.

    a survey would be a great way to ask for feedback and I’m sure we’d all love to see the survey results

    I totally get the reason why you propose a survey, but I am not sure this would be very practical in the context of Open Source communities. Instead, my suggestion would be to join the conversations in the Make WordPress Slack. You can see the current meeting times and channels here.

    Thanks again for your thoughts, Gary. I hope my reply helps and I look forward to continuing our conversation!

    Hi folks,

    I can sympathize with Gary Gordon’s problem with Gutenberg, and, yes, looking for solutions in the vastness of WP Support forums sometimes seems as vexing as the original issue.

    I have a problem with Gutenberg compatibility that I think and hope could add to discussion of general WP development strategy and responsibility structures for same.

    I recently posted a request for troubleshooting help here:

    https://www.ads-software.com/support/topic/problem-setting-parent-page-attribute-using-block-editor/#post-15729297

    The post relates to a specific problem I am having in converting over from the Classic Editor to Gutenberg.

    So far the only reply to my post, which you can read on the same page, is a suggestion that I engage with my Web host to install an alternative database for my WP installation.

    In the Web searches leading up to my posting I found that, probably, hundreds of other users have had problems similar mine.

    Instead of us each hunting down new databases, wouldn’t it have been advisable for Gutenberg developers to solve the compatibility problem?

    My understanding is that WP intend to discontinue the Classic Editor functionality this year (2022). Will Gutenberg compatibility issues be solved before Classic Editor users and their posts and pages are left to their own devices?

    Hey @robby-barnes, thank you for joining the conversation and sharing your experience.

    I replied to your original support thread.

    Since this is supposed to be a review, let’s please keep it lean here and continue the conversation regarding your own issue on the corresponding support thread instead. Thank you!

    • This reply was modified 2 years, 5 months ago by Alvaro Gómez.
Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘I wish WordPress would wake up and get rid of Gutenberg.’ is closed to new replies.