Hot Posts


The 6.2.1 update for WordPress has caused a disruption in shortcode support in block templates.

Many users are reporting issues with WordPress 6.2.1 update breaking shortcode support in block templates. It is recommended to check for any compatibility issues before updating to ensure smooth functioning of your website.

Yesterday saw the introduction of WordPress 6.2.1, which was made available to websites that allowed automatic background upgrades. There were five significant security updates in this version. Generally speaking, a maintenance and security release shouldn't break a website, however 6.2.1's removal of shortcode support from block templates is causing problems for a lot of users.

I'm excited to make the necessary changes to each of those pages in order to restore the shortcode. Alternatively going back to 6.2 and disabling updates.

Users were only informed of this by a brief and insufficient note regarding the vulnerability in the 6.2.1 release after Block themes processing shortcodes in user-generated data.

WordPress 6.2.1 co-release lead Jb Audras mentioned at today's core dev meeting that this issue might lead to a speedy 6.2.2 release, while specifics are still unknown.

I have only been willing to take into consideration WordPress and my security plug-in, Wordfence, for automated upgrades. In order to prevent issues, I will now turn them both off and schedule at least a 24-hour wait. In any case, I kind of like to plan updates because I'm a control freak.

With 6.2.1, my custom block theme website appears to function properly and makes use of several shortcodes. I kind of expected it to break, but I'm not sure why.

Although I doubt it, I don't believe I've used block templates. For the most part, I utilize the Gutenberg-based Kadence blocks and theme. For one site, I also utilize the Newspack blocks and the Automattic Newspack theme.

Lastly, how would a site go from 6.2.2 to 6.2.2 if it rolled back to 6.2?

All in all, I'm starting to dislike how much more work WordPress currently takes on when building a website using the block editor. My websites, which were created using the ancient editor decades ago, have never had problems updating WordPress core. Let down.

This! In my experience, I've found that very few core developers work with clients when perusing the Gutenberg repository and the trac. As a result, they are not conversant with common use cases for WordPress in professional settings such as the one you mentioned. And because they are ignoring a sizable section of the WordPress community, this presents a serious problem.

Not acquainted directly. Their deliberate neglect is evident from the backlog of Gutenberg issues, comments on Make posts, and the official yearly poll.

Your evaluations are accurate. During yesterday's core chat, there was a lengthy side discussion in which one core developer basically said, "You shouldn't be using shortcodes at all, and if you do, you're a bad developer." It's possible that you personally detest shortcodes for some other reason, but it's quite impolite to essentially look down on anyone who uses them.

I've been a contractor for eight years for one of the largest WordPress agencies in the world, where I oversee regular WordPress releases. For reasons like these, agencies typically wait one to two years before adopting new technologies like Gutenberg or FSE. Agency work is the lifeblood of and the center of the WordPress ecosystem. I would argue that the difficult thing to strike a balance is just the opposite, not falling behind since agency work requires stability: this is the reason Headless WordPress core is so far behind

For the time being, we are just going back to 6.1.1.

I always read the release notes before updating, and I never update automatically because of this. Furthermore, never make updates to your production system. Before deploying it, at the very least, test it in a staging environment.

This is regrettable, and some would argue typical of how some people in the tech business rush in with a messianic zeal and break everything. Even though it appears that there was a haste to address security flaws in this instance, a thorough explanation of the implications would have been appreciated. Beyond its blogging capabilities, WordPress may be difficult to work with to create websites with sophisticated use cases, and many of the innovative solutions are brittle. I'm wondering if a new platform is necessary for all these use cases that WordPress doesn't support.

Co-lead WordPress 6.2.1 Jb Audras stated that this problem might lead to a swift 6.2.2 release.

Our new website uses a block template, but thankfully everything is working well as of version 6.2.1.

In theory, WordPress 6.2.1 should work perfectly if your website isn't running a block template theme. None of my websites are impacted by the modification because none of them employ a block template with a modified theme.

If you're not familiar with block themes, WpEngine has a great post about them. Get block templates at

Paradoxically, and having nothing to do with 6.2.1 at all, I finally gave up yesterday and redesigned my theme to utilize PHP templates rather than just plain HTML block templates. I could finally get rid of all those silly workarounds. I'm even happier that I did now!

I utilize WordPress and premium themes built with the Genesis Framework. Every site is operational and undamaged. Updates via autopilot function flawlessly. As far as I'm aware, I don't use free or premium WordPress themes or shortcodes.

Yes, that took place at one of my clients' websites. Additionally, I utilize shortcodes to add normal traditional menus to my templates because, while I enjoy the Block Editor and the FSE approach, I find that the menu paradigm in both programs is completely unsatisfactory. To use the classic menus (just the way I want to use them), shortcodes are necessary. I deduced that it had to be an automatic update and resolved the issue by downgrading the WordPress version, but what a mess. Similar to others here, I'm learning from this problem: WordPress updates will no longer be done automatically.

The biggest irony in all of this is that while Gutenberg makes constructing extremely basic websites easier for non-techies, learning to code becomes far more difficult when the foundational knowledge isn't enough. I've worked as a professional web developer for 27 years, and I've been an expert with WordPress for ten of those years. However, the recent drastic changes to developer tools have left me feeling like a complete beginner. Even if you've bothered to understand React (which I haven't, and probably won't), things that were formerly an absolute no-brainer in PHP now require a considerably more involved procedure.

I understand how you feel. I am in a similar predicament. WordPress development was enjoyable before Gutenberg, but in recent years, it has become a laborious and time-consuming process that has negatively damaged my mental health. I'm still not sure what working with JavaScript and React is so amazing about.

I'm utilizing the block theme for WordPress 2022. I have a couple of quick code blocks, largely for form inserts. I updated to 6.2.1 on my development site, and now the short code blocks are functional. However, after reading this post, I'm a little anxious to make updates to my live sites. For what purpose would some shortcodes function while others are broken? Does this have to do with how I'm using the shortcodes? The shortcode block is being inserted into the FSE by me. Regards!

Acting startled about it is pointless. The demolition orders and planning charts have been visible for 50 Earth years at your local planning department in Alpha Centauri, so you've had plenty of time to file a formal protest. It's also much too late to start raising a fuss right now. How come you haven't visited Alpha Centauri? For heaven's sake, humanity, you know it's just four light years away. I apologize, but you are on your own watch if you can't be bothered to be involved in local matters.

Ticket 58366 at

-create a new template part in the site editor, select general for the part type, and give it a name. For example, I called mine small cart icon. -Insert your shortcode in the new template section and save. Select the template part you just created—in my instance, the small cart icon—in the header template where the shortcode is not rendered, remove the shortcode, and insert the template part element. Then, save. -result: The shortcode was appropriately rendered in the frontend.

There will be shortcodes for a very long time. It's your only choice as a WordPress developer who wants to create a feature that works with EVERY website. We have three options: shortcodes, blocks, and widgets. The only thing that functions with ALL page builders, block themes, and non-block themes is shortcodes.

Post a Comment