WordPress v6.2.1 Breaks the Shortcode Block in Templates

I can confirm that this is happening. I have a template that includes a GravityForms block, which generates a shortcode for insertion.

It works on normal pages, and even works on the admin for the template, but for the public render of the page, it just shows the shortcode.

This update completely bricked one of our sites that relies heavily on this block!

So this was in fact removed by design ??

There is an open ticket – https://core.trac.www.ads-software.com/ticket/58333 – and I have linked to this thread in there.

If you can provide details, like why you were using shortcodes in templates, it will help properly identify the severity. (this is not to say your uses are wrong or right, just trying to make sure the ticket priority can be properly evaluated)

I rolled back the site in question to 6.2 without any issues.

I’m having the same problem. Seeing shortcodes for two plugins, WPForms and Metaslider.

Can anyone help with a rollback?

I tried installing the Core Rollback plugin, and rolled back to 6.1.2, the next version available according to the plugin (though apparently prior to the one I was using before the update).

The problem is unfortunately still there. I’m still seeing shortcodes in the frontend, though I see the proper plugin in the backend.

Any help very much appreciated. I just launched the site today ??

@alpineer you can try this workaround: https://core.trac.www.ads-software.com/ticket/58333#comment:7

@ipstenu it’s absolutely insane to me that shortcodes have been removed by design!! Every single one of our agency’s FSE sites uses the shortcode block in templates for everything: filters, search, ACF & plugin integrations. This is chaos!! ??

The workaround doesn’t seem to work for me. Going to revert to a previous version and hope there is a fix.

I’ve got the same problem on over 600 pages which use five or six different templates with shortcodes in each template on one site and similar things on several others.

I’m looking forward to editing each of those pages to get the shortcode back in place. Or backtracking to 6.2 and turning off updates.

It reminds me of this:

“There’s no point in acting surprised about it. All the planning charts and demolition orders have been on display at your local planning department in Alpha Centauri for 50 of your Earth years, so you’ve had plenty of time to lodge any formal complaint and it’s far too late to start making a fuss about it now. …

What do you mean you’ve never been to Alpha Centauri? Oh, for heaven’s sake, mankind, it’s only four light years away, you know. I’m sorry, but if you can’t be bothered to take an interest in local affairs, that’s your own lookout. Energize the demolition beams.”

Douglas Adams, The Hitchhiker’s Guide to the Galaxy

• This reply was modified 1 year, 5 months ago by asjl.

Thanks, @andergmartins. I’m not clear on exactly what I should do.

“Add the following code as a plugin in a PHP file in the plugins folder:”

I’m in the plugins folder, but where exactly do I put this code? Does it go in one of the PHP files for the plugin I’m having problems with?

Or does it go in a PHP file by itself? And in the folder for the plugin I’m having problems with? And what should be the file name, does it matter?

Thanks for any help on this.

I worked out a not-great hacky workaround; cos you can still have shortcodes in post content still, I made a new static MyHome template – with all the query loops etc – adding a post content block, then made a page and put the shortcode slider (Smart Slider 3, broken by this update) in content, and set that page as a template of the MyHome and voila. I am not happy about this, tbh and it remains to be seen if this impacts SEO or other stuff…cos of course gonna have two home page URLs now – /home-page as well?

Now…is it possible to make the Search results template do something similar? Attach it to a page with the shortcode content in?

I am expecting not because Search results is a dynamic thing; but if this is going to be fritzed around with by whoever breaking stuff, I’d rather have my Search form PHP shortcodes in content where they might render….

Apparently this is not Automattic’s doing, but whoever it is, taking major functionality out like that overnight is not a good look, zero day or not. Tell and warn people? Maybe?

• This reply was modified 1 year, 5 months ago by timbearcub.
• This reply was modified 1 year, 5 months ago by timbearcub.
• This reply was modified 1 year, 5 months ago by timbearcub.

Hello there

Got the same issue this morning after updates ; ouch didn’t help my Coffee addiction ‘^^

I tried the solution to make the short code blocs as block template part as explained petitphp in https://core.trac.www.ads-software.com/ticket/58333#comment:12
and it happily solved the problem.

Séverine

• This reply was modified 1 year, 5 months ago by rubin-sev.

Thanks @rubin-sev and @timbearcub.

i’m glad you were able to find a solution.

Unfortunately I am not able to follow how you did this.

Would either of you be able to explain in semi lay person terms how to implement your workaround?

Thanks!

Sadly I cannot add a screenshot image but I will try to describe as well as I can
Go where you added your short code block select it , click and you will have the menu options ( copy duplicate insert lock etc… ) you will find create Template part
you will be asked the name of your templePart. Then it will include the short code block into the template part block ( wich will be in purple color ).

It worked for me ?? perhaps you will have to purge your wordpress and brower caches

Hope it will be useful for you ??

Séverine

• This reply was modified 1 year, 5 months ago by rubin-sev.

Amazing @rubin-sev! I was able to follow your clear instructions. Thank you so much for taking the time to explain.

Is this a sort of bug in the update that did not take into account shortcodes in template parts? Or does including the shortcode in the template part resolve the security issue?

If it is the former/first, I’m guessing someone will realize it sooner or later and the next update will break the shortcodes again. Is this a fair observation?

Anyway, thanks to you and good luck to all.