WordPress has killed shortcodes used in block templates in 6.2.1

  • Resolved timbearcub

    (@timbearcub)


    1 year, 6 months ago

    Not totally your fault, but Automattic has decided to pull shortcodes from block templates. https://www.ads-software.com/support/topic/wordpress-v6-2-1-breaks-the-shortcode-block-in-templates/ claiming a ‘security issue’ but basically nuking two plugins I use, yours included.

    That means your plugin just shows [smartslider3 slider=”6″] when used in a FSE template. But it shows fine in the FSE editor!

    Just thought you might want to know, before the confused people that Automattic SHOULD have informed start blaming you. They shouldn’t just remove functionality like that – it’s like the bad old days all over again.

    I now have to also work out how to plug in some form/PHP code to put category lists into search boxes. Grr.

    Sorry like the Gutenberg issue you’re left holding the baby…

    • This topic was modified 1 year, 6 months ago by timbearcub.
Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support Gabor

    (@nextendweb_gabor)

    Hi @timbearcub!

    Thanks for the info! This issue seems to affect many people, we got about 10 similar tickets in our support system, so hopefully WordPress developers will realize how big of a mistake they made.

    I see, that you managed to create a workaround, but in case anyone else will have this issue (or you would prefer a different solution), with the suggested workaround:

    https://core.trac.www.ads-software.com/ticket/58333#comment:7

    I created an installer zip file:

    https://www.dropbox.com/s/560p3fzqkvbq62k/fix-shortcode.zip?dl=1

    This should be installed at Plugins -> Add new, and after activating this “Fix shortcode” plugin, shortcodes should work again.

    Meanwhile we are checking it within our code too, how could we create a solution for this issue, in case WordPress will stay this way.

    Hi

    Thanks @gabor !
    -> There is also a quick solution by integrating the block in a model part.
    it works for us !

    hi @harvestagency can you please explain how you fixed it? thank you

    Plugin Support Gabor

    (@nextendweb_gabor)

    We managed to create a fix from our end. Here is an installer:
    https://www.dropbox.com/s/1lvgfzct9xktxhw/smart-slider3-wordpress-free-bugfix-SSDEV-3871-wp-removed-shortcode-support.zip?dl=1

    If you go to your Plugins list -> delete your current Smart Slider 3 (don’t worry, your sliders will stay) and install this one by uploading it:
    https://smartslider.helpscoutdocs.com/article/1717-wordpress-installation#admin
    that should solve the issue.

    This fix will be included in the next Smart Slider versions as well!

    About this, and my previous answer what I can tell is, that the “Fix shortcode” plugin fixed all shortcodes, while within our code we are only fixing our own code. So if there was a security issue regarding shortcodes about why WordPress developers did the changes they did, the new version of our plugin won’t bring back those issues.

    Hi @mrglennjones

    Select your slider block and add it to a part model

    https://www.dropbox.com/s/zgi1bvmouidcsfi/Capture%20d%E2%80%99%C3%A9cran%202023-05-17%20%C3%A0%2016.39.53.png?dl=0

    Thread Starter timbearcub

    (@timbearcub)

    Thank you for such a great quick service!
    Yes a lot of people are affected by this – same thing has happened to Insert PHP Code plugin as well; which is annoying cos I suspect that won’t be fixed, and so I need to develop another solution for inserting that code into my site because I can’t solve it that way.

    The PHP code ‘fix\ will bring back the security issue, so I’d rather not do it…but I created a workaround by switching my site to a static page with a ‘front page’ template that mirrored my Home template, then putting Smart Slider 3 into the content on that page. The shortcode problem was only in templates, so Smart Slider works fine in the page content. Obviously you’ve fixed the issue now, but some people might need to do that for other plugins.

    The other option was stay at 6.2, but again, if there is a security issue, I’d rather be updated…

    But rather annoying to be doing that at 6am fixing a site when I’m sure a better solution could have been found than just breaking the functionality (or at least telling us users what is going on)!

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘WordPress has killed shortcodes used in block templates in 6.2.1’ is closed to new replies.