[WordPress] 外掛分享: CraftRoq Relocate DB

首頁 › 外掛目錄 › CraftRoq Relocate DB
WordPress 外掛 CraftRoq Relocate DB 的封面圖片
全新外掛
安裝啟用
—
尚無評分
9 天前
最後更新
—
問題解決
WordPress 6.5+ PHP 8.1+ v1.1.0 上架:2026-10-06

內容簡介

CraftRoq Relocate DB 是一款專為網站資料庫變更設計的外掛,能夠安全地在不同環境間進行資料替換,如從測試環境轉移至正式環境、切換至 HTTPS 或更改網域名稱。它提供預覽功能,確保不會破壞現有網站。

【主要功能】
• 預覽替換結果,確保安全性
• 正確處理序列化資料和 JSON
• 支援大型資料庫的批次處理
• 每個替換批次為一個資料庫交易
• 提供搜尋和替換多達 20 對的功能
• 支援 WP-CLI 指令操作

外掛標籤

開發者團隊

⬇ 下載最新版 (v1.1.0) 或搜尋安裝

① 下載 ZIP → 後台「外掛 › 安裝外掛 › 上傳外掛」
② 後台搜尋「CraftRoq Relocate DB」→ 直接安裝(推薦)
📦 歷史版本下載

原文外掛簡介

CraftRoq Relocate DB changes text across your database: moving a site from staging to production, switching to HTTPS, changing a domain, or renaming something everywhere it appears.
It is built for doing that on real sites without breaking them.
Preview first, always
Every replacement starts as a dry run. It searches the tables you choose, changes nothing, and shows exactly what would change: rows and replacements per table and column, values it would leave alone and why, and before/after examples. Only a completed dry run can be applied, and applying it repeats exactly what was previewed.
Serialized data and JSON handled properly
Plugins and themes store settings as serialized PHP. A plain text replacement breaks those values whenever the length changes. Relocate rewrites serialized data token by token and recalculates every length, without unserializing it, so no plugin code runs and objects, private properties, references and numbers stay exactly as they were. URLs inside JSON (as page builders store them, with escaped slashes) are found and replaced too.
A value is left untouched, and reported, when changing it could corrupt it: serialized data that is already broken, a custom serialized format only its own class understands, or JSON that would become invalid.
Made for large databases
Tables are processed in small batches by primary key, a few seconds per request, so there are no timeouts or memory limits to hit however big the tables are. Progress is saved after every batch. If the page is closed or the connection drops, the job can be continued from the last completed batch.
Safety measures

Each batch of a replacement is one database transaction: it is saved completely or not at all, so an interruption never leaves a batch half applied or applies it twice. This needs InnoDB tables, which WordPress uses by default; the confirmation step warns about any that are not.
The original value of everything a replacement changes is saved to a downloadable file of SQL statements. Importing it puts those values back.
The site address (siteurl and home) is changed last, so you are not logged out part-way through.
Tables without a primary key or suitable unique key are skipped, because their rows cannot be updated one at a time safely.
Post GUIDs are left alone unless you ask for them to be changed.
Only administrators who can post unfiltered HTML can use it.

Also included

Up to 20 search and replace pairs in one job, applied together in a single pass.
Choose the tables to search, and leave out individual columns.
Case-insensitive and whole-word matching, and matching the http:// and protocol-relative versions of a URL.
A live progress view with the current table, rows scanned, changes found and time remaining.
A searchable, sortable history of every job, a log, and automatic clean-up. Old jobs can also be deleted by hand.
Import / Export: download the database as a .sql.gz file and import .sql or .sql.gz files, in resumable steps, with the site address changed on the way out or on the way in. Imported tables are built next to the ones in use and put in place together at the end, so the site keeps working during an import, and one that fails or is cancelled leaves them as they were.
Export and import the plugin’s settings as a JSON file.
WP-CLI commands: wp crq search-replace and wp crq resume.

延伸相關外掛

文章
Filter
Mastodon