外掛說明
Convert to Blocks 是能將傳統編輯器內容即時轉換為區塊的 WordPress 外掛。安裝 Gutenberg 外掛或升級至 WordPress 5.0 或更新版本後，網站內容會顯示為 [傳統編輯器] 區塊。這些區塊能具備完整功能，也能在網站前端正確顯示內容，但是會使得內容作者無法充分發揮區塊編輯功能；為了充分發揮區塊編輯功能，傳統編輯器產出的內容必須轉換為區塊內容。這個外掛能完成即時轉換，當區塊編輯器編輯傳統編輯器產出的內容時，相關內容會剖析為區塊內容。只要在區塊編輯器中儲存內容，內容的新結構便會儲存至資料庫中。這個方式可以降低風險，因為僅需變更內容的資料庫值。
請注意，內部區塊轉換支援必須安裝 Gutenberg 10.9.0 或 WordPress 5.9 的更新版本。
螢幕擷圖
使用 WP-CLI 命令 wp convert-to-blocks start便能在瀏覽器中重複轉換文章進行批次移轉，而不需手動輸入
安裝方式
手動安裝
- 將外掛安裝套件解壓縮所得的
convert-to-blocks資料夾上傳至網站的/wp-content/plugins/目錄。 - 在 WordPress 管理後台的 [外掛] 選單中啟用 Convert to Blocks。
常見問題集
-
如何知道外掛是否已執行？
-
在內容中找到傳統編輯器，然後試著離開該頁面，便會顯示「系統可能不會儲存變更」的提示訊息，這是因為 Convert to Blocks 會即時將網站內容轉換為區塊，且這些變更會在更新內容後才儲存。
-
Convert to Blocks 是否能處理自訂區塊？
-
預設無法處理。
-
Convert to Blocks 是否能處理巢狀區塊？
-
如果 WordPress 核心程式版本低於 5.7.2 (含)，這個外掛所需的巢狀/內部區塊支援，無法正確執行於這些版本所整合的 Gutenberg 功能。這項功能所需的 Gutenberg 外掛版本需要高於 10.9.0 (含)，即 WordPress 5.9 或更新版本。
使用者評論
2025 年 5 月 14 日
1 則留言
You might wonder why you need this plugin when the “Convert to blocks” button is right there at the top of every Classic block. Well, click that and it will eff up any images you had using the <figure class=”alignleft”> (or alignright) code. The default WP “convert to blocks” strips out the figure code entirely and POOF your alignment class is gone and your caption is off god knows where. But not this plugin! Add this and when you open your classic page in the block editor, it preserves the figure tag and alignment class. Saved me having to redo image settings on 600 post. Thank you 10up.
2025 年 3 月 12 日
1 則留言
All this does is convert posts into HTML blocks, same as happens if you manually tell WordPress to convert a classic HTML post to blocks. Ok, it saves a single mouse click… why install a plugin to save one mouse click?
2024 年 5 月 20 日
1 則留言
When you run a command and open a URL, the browser opens articles one after another and converts them into blocks. It magically automatically converts blocks quickly and accurately.
2024 年 4 月 9 日
1 則留言
Saves me a lot of time. Used it two times on large projects.
I did not try the bulk option, but I just read that it can have bugs or crashes. Probably due to server load or unusual post content?
What I did instead was create a button that that when pressed automatically opens in a new tab the 20 posts from the Posts Table view.
I then waited for them to load.
After they were all loaded I went to each page and updated the page.
I then waited a while for all of them to be saved and double checked in the Posts Table if all the posts were converted to the Block editor. The little icon showing if the post is Classic or Block comes very handy!
Once I confirmed that all 20 posts from the Posts Table view were converted I moved to the next page and repeated the process.
This semi-automated process helps prevent “bugs” or perhaps random server spikes.
I was running this on my own private cloud server with little resources. Surprisingly saving 20 posts at once was possible without any crashes.
I did not have any bugs or issues.
Thank you for creating this plugin!
2024 年 4 月 2 日
2 則留言
I have a load of old posts and pages done in the original WP editor which desperately needed converting to blocks in order to play nicely with a child theme I was working on. We know the block editor has the facility to go through posts/pages one-by-one and convert to blocks – but this is painful….
This plugin seems to do that job for you, but silently in the background.
Once I’d activated it and saved the settings, nothing happened….at least, not visually. It was only when I started to look at the entries made in the legacy editor that I could see they had been converted to block format – silently!
The only improvement I can suggest is a message on the plug-in interface page which says something like, “when you have ticked the checkboxes, press the save button and your conversion will commence as a background task.”
I don’t know if that would make sense in keeping with the way the plug-in works. I only have a couple of hundred posts so it did the job quickly. I don’t know how it would perform on a site with thousands of old posts in legacy editor format. Either way, thanks to the author for saving me the time.
2023 年 11 月 6 日
2 則留言
Very good plugin, which helps to migrate a lot of posts.
We have a project with ~8000 posts, which needs to be converted. Only standard text and images…
Unfortunatly WordPress itself is pushing Gutenberg, but not providing tools for this task.
This plugin is helping a lot. Basically it opens the browser, clicks the button, saves the post, opens the next post …
A quite clever solution, which unfortunately is slow and sometimes breaks.. Means you have to monitor the task and reload the tab from time to time…
參與者及開發者
變更記錄
1.3.4 – 2025-07-15
- Fixed: Ensure no PHP error is thrown on the plugin list screen when running PHP 8.0 (props @dinhac, @dkotter, @faisal-alvi via #210).
1.3.3 – 2025-07-14
- Added: Link to settings page from the plugin list page (props @badasswp, @dkotter via #195).
- Changed: Bump WordPress “tested up to” version 6.8 (props @jeffpaul via #199, #200).
- Changed: Bump WordPress minimum supported version to 6.6 (props @jeffpaul via #199, #200).
- Fixed: Fix PHP warning due to undefined array key (props @sksaju, @dkotter via #202).
- Fixed: i18n functions being called too early, causing PHP Notices (props @stormrockwell, @dkotter, @dsawardekar via #203).
- Security: Bump
cookiefrom 0.4.2 to 0.7.1,expressfrom 4.21.0 to 4.21.2,@wordpress/e2e-test-utils-playwrightfrom 1.7.0 to 1.18.0,serialize-javascriptfrom 6.0.0 to 6.0.2 andmochafrom 10.4.0 to 11.1.0 (props @dependabot, @Sidsector9 via #194). - Security: Bump
axiosfrom 1.7.4 to 1.8.3 (props @dependabot, @iamdharmesh via #196). - Security: Bump
http-proxy-middlewarefrom 2.0.6 to 2.0.9 andtar-fsfrom 3.0.8 to 3.1.0 (props @dependabot, @dkotter via #206).
1.3.2 – 2025-02-03
- Changed: Bump WordPress “tested up to” version 6.7 (props @colinswinney, @jeffpaul via #188, #190).
- Security: Bump
axiosfrom 1.6.8 to 1.7.4 (props @dependabot, @dkotter via #180). - Security: Bump
webpackfrom 5.91.0 to 5.94.0 (props @dependabot, @faisal-alvi via #181). - Security: Bump
wsfrom 7.5.10 to 8.18.0 and@wordpress/scriptsfrom 27.8.0 to 30.4.0 (props @dependabot, @faisal-alvi via #182, #189). - Security: Bump
expressfrom 4.19.2 to 4.21.0 (props @dependabot, @iamdharmesh via #185).
1.3.1 – 2024-08-20
- Changed: Bump WordPress “tested up to” version 6.6 (props @sudip-md, @jeffpaul, @Sidsector9, @ankitguptaindia via #174).
- Changed: Bump WordPress minimum from 6.3 to 6.4 (props @sudip-md, @jeffpaul, @Sidsector9, @ankitguptaindia via #174).
- Fixed: Issue with saving a post before the convert to blocks transform was completed (props @mdesplenter, @Sidsector9, @dsawardekar via #173).
- Security: Bump
bracesfrom 3.0.2 to 3.0.3 (props @dependabot, @Sidsector9 via #168). - Security: Bump
wsfrom 7.5.9 to 7.5.10 (props @dependabot, @Sidsector9 via #169).
1.3.0 – 2024-05-14
- Added: Block Catalog integration, and pagination support (props @dsawardekar, @iamdharmesh via #164).
- Changed: Adjust
enable_block_editormethod only to alter posts that support the gutenbridge (props @stormrockwell, @Sidsector9, @jeffpaul, @dsawardekar via #136). - Changed: Bump WordPress “tested up to” version 6.5 (props @QAharshalkadu, @jeffpaul, @Sidsector9, @sudip-md, @dkotter via #146, #161).
- Changed: Replaced lee-dohm/no-response with actions/stale to help with closing no-response/stale issues (props @jeffpaul via #159).
- Changed: Bump Node version from 16 to 20 (props @aaronjorbin, @Sidsector9, @dkotter via #160).
- Changed: Bump
actions/upload-artifactfrom v3 to v4 (props @iamdharmesh via #162). - Security: Bump
follow-redirectsfrom 1.15.2 to 1.15.4 (props @dependabot, @dkotter via #153). - Security: Bump
browserify-signfrom 4.0.4 to 4.2.2 (props @dependabot, @dkotter via #145). - Security: Bump
@babel/traversefrom 7.11.5 to 7.23.7 (props @dependabot, @dkotter via #155). - Security: Remove old dependencies in favor of using
@wordpress/scriptsin our build workflow (props @Sidsector9, @dkotter via #167).