-
Notifications
You must be signed in to change notification settings - Fork 805
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Subscriptions: Remove the shortcode #15227
Comments
Thanks for this! Leaving the shortcode in Simple payments block was one of my biggest regrests. 😅 It came from wish to not add yet another simple payments implementation (alongside widget, classic editor block, and shortcode) but it turned out to be short-sighted and caused more trouble than it was aiming to save time. |
Noting that, at present, shortcodes included in the block templates and block template parts of FSE themes are not rendered, and that probably won't change. It seems like that might make this issue a bit more urgent. |
Could you clarify a bit what you mean by that? Would 5.9 break rendering of shortcodes in some way? |
ah, I was able to reproduce. For some reason, the shortcode is rendered when used in a footer template, but not in a single post template. I added this issue to the primary issue for WP 5.9 compat. |
@jeherve is there a way to tell which other blocks output a shortcode? I'm thinking forms and simple payments from memory. Anything else? |
Maybe the contact form too? |
There are no other blocks that should be problematic in that regard as far as I know. |
This is fixed with #26947 |
The Subscriptions block outputs a shortcode.
Describe the solution you'd like
We should remove this, and output the markup we want for the block directly as suggested by @mtias
Describe alternatives you've considered
Keeping the shortcode means that people who use the shortcode continue to be able to benefit from the additional features we add, but this results in more complex development and doesn't encourage people to move to Gutenburg.
The text was updated successfully, but these errors were encountered: