Thanks for responding. That’s frustrating, but important to figure out, so I think we need to bring this to the developers. Would you be able to open an issue in the Gutenberg repository about this? The more details, steps to reproduce, information about the site, perhaps even URL, plugins installed, theme, WordPress and plugin versions, the better. If not, let me know and I’ll see if I can open an issue on your behalf.
I’m keen on getting to the bottom of this, would you be able to share a full set of steps so I can try to reproduce? I’d like to know if which theme you’re using, whether you’re editing a post or a page, and whether you have the Preview (desktop icon) > Show template option enabled or not.
For what it’s worth, the notes icon should appear if a post or page already has a note, and not otherwise. So if you select a block, click the ellipsis in the toolbar, and choose the option “Add note”, and type in your comment, the note should appear:
Hey there, I just tested locally and the site title block when inserted should link to the homepage by default. If it does not, you can indeed check the inspector toggle to say “Make title link to home”.
One thing that is possible, is for a plugin to provide a category of its own, for its blocks, including an icon. That’s up to each plugin to do, for example, here’s an example.
Hey there, sorry to hear you having trouble. Whether it’s an issue in the Gutenberg plugin, or the theme, or a plugin, is hard to discern at a glance, but based on the fact that it is an energetic core block that fails to render, it seems it’s either an issue with that block, or a bug in the editor that affects that particular block. It seems like your best bet would be to contact the plugin author for support. Alternately, do you see any errors in your browser console? You should be able to see the console by pressing Ctrl Shift I (Windows/Linux) or ⌘ Option I (Mac).
I just wanted to connect you with this potentially related issue for the font library, and also validate that this is a feature I’d like to see as well. For now, that issue could be one to subscribe to, for updates.
That’s the one. It should be safe to both activate (to get the latest features) and even deactivate. Though the fix I mentioned isn’t released to that plugin yet, it will be in version 16.5, the next version. So whether 6.3.1 or 16.5 lands first, that isn’t clear to me. It shouldn’t be too long though, days.
Thanks for all the context. I wanted to point to this bug in WordPress 6.3 which is possibly related to the crashes you are seeing. The fix has been merged and is expected to go out in 6.3.1, and in case it’s the same issue, can hopefully fix what you’re seeing.
Can you share a bit more context on what you’re seeing in your application profiling? In my tests that page is consistently getting between 180-200ms lcp.
