• This is a great leap forward in themes, and if everything worked as intended, it would be just about the best. Right now there are too many frustrating bugs to give it the very top rating—some in the theme itself, some in the Site Editor. Twenty Twenty-Two depends on the Site Editor to get anything done, but the Site Editor is still marked “beta,” and for good reason.

    Nevertheless, I’ve gone mad with the power of full-site editing. Maybe it was a mistake to make random bugs the default WordPress experience. But the bugs will be squashed, and I’ll remember this as the theme that put the power of Web design in the hands of writers and designers instead of coders.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Hi @cbaile19

    Are you able to give in-depth information about the bugs you encountered?

    You could also take a screenshot of what you are seeing, upload it to a site like https://snipboard.io/ and then add the link to your response.

    Thread Starter cbaile19

    (@cbaile19)

    Happy to help, but I was hurriedly adjusting live sites, so I didn’t keep a scientific record. I have Twenty Twenty-Two on three sites hosted by DreamHost right now. Here are some things I remember:

    1. Images in “classic” block don’t respond to maximum width. If I “convert to blocks,” they do, but on a site that has content going back to 2007 that isn’t practical. Workaround: activate the Customizer (I use the Toolbelt plugin, which has an “Enable the Customizer” feature) and add

    img {height: auto;
          max-width: 100%;}

    in Additional CSS.

    2. Blockquotes in “classic” block are formatted identically to regular paragraphs. “Convert to blocks,” and they convert to properly styled blockquotes.

    3. Trying to edit the footer always produces a “saving failed” message.

    4. “Saving failed” frequently happens in the Site Editor when I try other things, but I haven’t experimented scientifically enough to notice the other patterns.

    5. Sometimes when I get a “saving failed” message, the saving seems not to have failed.

    6. Typography is different on Windows from other platforms. Font weights are wrong on Windows. Italics (with inline <i> tags) do not render in post titles on Windows, but do on other platforms. When I tweaked the typography on one site to use a serif font for paragraph blocks, <i>all</i> inline markup stopped rendering on Windows: the editor showed the “i” button darkened for text marked with <em>, but the text did not appear in italics in the editor or on the front end. These typography problems do not seem to affect Macintosh or Android.

    I hope my scatterbrained notes help a little. I’ve been a WordPress user since 2006, but I’m a writer who never developed much patience for code. It seems to me that block themes and the Site Editor are turning WordPress into what I always wanted it to be. We’re not there yet, but I can see the destination on the horizon.

    Moderator Kathryn Presner

    (@zoonini)

    Hi there @cbaile19,

    Thanks so much for compiling this list of feedback, it’s most appreciated!

    1. Images in “classic” block don’t respond to maximum width. If I “convert to blocks,” they do, but on a site that has content going back to 2007 that isn’t practical. Workaround: activate the Customizer (I use the Toolbelt plugin, which has an “Enable the Customizer” feature) and add

    I haven’t yet been able to replicate this yet on my test site running Twenty Twenty-Two, via these steps:

    – added a Classic block to a page
    – inserted a large image within the Classic block
    – clicked the pencil icon on the image and selected “Full size” for the image

    The image isn’t overflowing the column on my end.

    If you’d like to troubleshoot this more, would you be able to provide a link to a page or post where you had to add custom CSS to fix an image overflow issue, so I can take a look directly?

    2. Blockquotes in “classic” block are formatted identically to regular paragraphs. “Convert to blocks,” and they convert to properly styled blockquotes.

    I was able to replicate this one, and it seems to be occurring because a blockquote element within a Classic block does not have the wp-block-quote class that a Quote block has, which is where the styling is coming from.

    I’m not actually sure whether this would actually be considered a bug. Twenty Twenty-Two comes with very minimal CSS, and instead was designed to inherit most of its styling from the Gutenberg block editor styles. So if an element added to the Classic block is missing block-editor styles (as in the situation here) it’s kind of to be expected that the associated styling would be missing, and a CSS workaround seems like an appropriate trade-off here. Adding something like this to your custom CSS should do the trick:

    blockquote {
      border-left: 1px solid;
      margin: 0 0 0 1.75em;
      padding-left: 1em;
      box-sizing: border-box;
      overflow-wrap: break-word;
    }

    3. Trying to edit the footer always produces a “saving failed” message.

    4. “Saving failed” frequently happens in the Site Editor when I try other things, but I haven’t experimented scientifically enough to notice the other patterns.

    5. Sometimes when I get a “saving failed” message, the saving seems not to have failed.

    This sounds like a block editor or Gutenberg-related problem rather than something specific to the Twenty Twenty-Two theme. Would you like to troubleshoot further here, or better yet, would you be willing to make a separate post in the Gutenberg forum so we can go through troubleshooting steps in detail?

    https://www.ads-software.com/support/plugin/gutenberg/

    6. Typography is different on Windows from other platforms.

    I noticed there is a support post on this topic. I’ll try to either have a look myself or get some other eyes on this one.

    It seems to me that block themes and the Site Editor are turning WordPress into what I always wanted it to be. We’re not there yet, but I can see the destination on the horizon.

    That’s great to hear. ?? I’m glad you see the potential, and I hope you’ll enjoy the improvements to Full Site Editing that are coming up this year!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Liberating but buggy’ is closed to new replies.