-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Search & Replace in Gutenberg #21886
Comments
I really like the idea of a solid search and replace. I do think to start this would be best explored in a plugin, I say that as then it could be iterated. As the project moves into collaborative editing, I think having a strong search and replace makes solid sense, which even more bolsters the need to explore this. Let me put up some feedback labels though to get other's input. |
This issue was discussed today during the Design team's triage meeting in Slack (registration required). We agreed this could be a handy feature to have, and think it would be great to see explored first as a plugin. |
I like this idea too. how to contribute for this idea? |
Today is the 2nd anniversary of this feature request! 🥳 I still think, this is could be an important feature for the block editor. |
+1 |
Please implement a “Search & Replace” feature in Gutenberg.
I often need this feature for post/page templates with placeholders, which I replace with the correct text. Also I often revisit older articles and have to search & replace wordings.
I know, that I can do some “dirty” tricks to do the Search & Replace in Gutenberg manually on a PC (copy HTML/Gutenberg markup to text editor and replace the text there), but this is problematic, because it could break the HTML/Gutenberg markup, …. and it’s 100% not working on mobile.
In the classic editor, it was easy to add the Search & Replace feature via “TinyMCE Advanced” plugin.
Implementation ideas:
– Implement a Search & Replace functionality in Gutenberg like the one available in TinyMCE.
– WP-CLI support for Gutenberg Search & Replace
The text was updated successfully, but these errors were encountered: