Timeline for How to update a Gutenberg block without manually recovering it?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 26, 2020 at 23:07 | answer | added | Welcher | timeline score: 2 | |
| May 26, 2020 at 23:02 | comment | added | Welcher | Block deprecation works to address the rendering issues in the block editor but all of the blocks will still need to be manually updated as the markup is still saved in the database. | |
| May 25, 2020 at 14:51 | comment | added | Siddharth Thevaril | Thanks a lot, this is just what I needed! Can you add this as an answer so that I can accept it? | |
| May 25, 2020 at 13:40 | comment | added | Jacob Peattie | When updating a block that has been used, you need to "deprecate" the block, which allows it to be migrated to the new version. The process for that is documented here: developer.wordpress.org/block-editor/developers/block-api/… | |
| May 25, 2020 at 13:15 | history | asked | Siddharth Thevaril | CC BY-SA 4.0 |