Skip to content
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

Introduce option to auto-convert freeform content upon opening the editor #44054

Open
mtias opened this issue Sep 11, 2022 · 2 comments
Open
Labels
[Block] Classic Affects the Classic Editor Block [Feature] Convert to Blocks Internally: "raw handler" [Type] Discussion For issues that are high-level and not yet ready to implement. [Type] Enhancement A suggestion for improvement.

Comments

@mtias
Copy link
Member

mtias commented Sep 11, 2022

It's about time we start looking into further smoothing out the transition points from classic content to blocks. We have some pending refinements to do on validation and generally being more permissive about attribute spread, but there are also some steps we can start formalizing before we consider ways to do bulk conversion of content in the future.

One of these steps would be to introduce a configuration setting to WordPress so that the editor attempts to auto-convert freeform content into blocks the moment you open the editor, instead of handing it over to the classic block and requiring clicking the "convert to blocks" button. This should be a reversible action, for the most part. I'd imagine a notice triggering "content was updated" with the option to undo. We could go further and use this same setting to stop loading the classic block (and all its dependencies) from the block library.

I imagine a few extra requirements and considerations:

  • Probably the best start is to make it a wp-config constant: AUTO_CONVERT_TO_BLOCKS, maybe supporting a definition that can include specific post types so you can restrict auto-conversion to pages but leave it off from posts, etc.
  • Obviously would be set to off by default and opt-in.
  • Maybe also don't allow the constant to trigger any behaviour if WP_POST_REVISIONS is also false, as we'd want to limit any operation that is not easily retrievable from prior state when something goes wrong.

Any other considerations I might be missing?

@mtias mtias added [Type] Enhancement A suggestion for improvement. [Feature] Block Transforms Block transforms from one block to another [Type] Discussion For issues that are high-level and not yet ready to implement. labels Sep 11, 2022
@github-actions
Copy link

Hi,
This issue has gone 30 days without any activity. This means it is time for a check-in to make sure it is still relevant. If you are still experiencing this issue with the latest versions, you can help the project by responding to confirm the problem and by providing any updated reproduction steps.
Thanks for helping out.

@github-actions
Copy link

This issue has gone 30 days without any activity.

@github-actions github-actions bot added the [Status] Stale Gives the original author opportunity to update before closing. Can be reopened as needed. label Oct 12, 2022
@glendaviesnz glendaviesnz removed the [Status] Stale Gives the original author opportunity to update before closing. Can be reopened as needed. label Oct 13, 2022
@ellatrix ellatrix added [Feature] Paste [Block] Classic Affects the Classic Editor Block labels Aug 18, 2023
@ellatrix ellatrix added [Feature] Convert to Blocks Internally: "raw handler" and removed [Feature] Block Transforms Block transforms from one block to another [Feature] Paste labels Jul 12, 2024
@mtias mtias mentioned this issue Sep 29, 2024
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Block] Classic Affects the Classic Editor Block [Feature] Convert to Blocks Internally: "raw handler" [Type] Discussion For issues that are high-level and not yet ready to implement. [Type] Enhancement A suggestion for improvement.
Projects
None yet
Development

No branches or pull requests

3 participants