[WordPress] 外掛分享: WPShift Companion

首頁外掛目錄 › WPShift Companion
WordPress 外掛 WPShift Companion 的封面圖片
10+
安裝啟用
尚無評分
剛更新
最後更新
問題解決
WordPress 5.0+ PHP 7.4+ v1.1.1 上架:2026-01-15

內容簡介

WPShift Companion 是一款將 WordPress 網站連接至 WPShift 的外掛,提供簡易的網站遷移、魔法登入及管理 SMTP 功能,讓使用者能夠更有效率地管理其網站。

【主要功能】
• 連接網站至 WPShift 帳戶
• 一鍵遷移至 WPShift 伺服器
• 魔法登入,無需密碼
• 自動應用管理 SMTP 設定
• 性能優化與資料庫清理功能

外掛標籤

開發者團隊

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

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

原文外掛簡介

WPShift Companion connects a WordPress site to WPShift, a hosting and server management platform for WordPress. The plugin is the bridge between your site and your WPShift dashboard.
What the plugin does:

Connect your site — link this WordPress site to your WPShift account with a guided authorization flow. No passwords are exchanged; the connection uses a revocable token.
One-click migration — move this site onto a WPShift-managed server. The plugin builds a complete backup (files and database) in the background and hands it to WPShift, which restores it on your new server. Migration always requires an explicit confirmation from a site administrator before anything is transferred.
Magic login — open this site’s WordPress admin directly from your WPShift dashboard, without typing a password.
Managed SMTP — when your WPShift server provides outgoing email, the plugin applies that SMTP configuration to WordPress automatically, so site email is delivered reliably.
Performance optimizer — a set of opt-in tweaks: disable emojis, embeds and jQuery Migrate, control the Heartbeat API, clean up header output, lazy-load media, and harden common attack surfaces (XML-RPC, login hints, author archives).
Database cleanup — remove revisions, auto-drafts, trashed posts and comments, spam, expired transients, and orphaned metadata.

The optimizer and database cleanup work on their own; connecting to WPShift is only required for migration, magic login, and managed SMTP. A WPShift account is available at wpshift.io.
External services
This plugin connects to the WPShift platform at app.wpshift.io (operated by WPShift, https://wpshift.io). Without this connection the migration, magic login, and managed SMTP features cannot function. Data is only transmitted after you connect your site to a WPShift account, except where noted.
What is sent, and when:

Connecting your site — your site’s URL, site name, and the admin email address are sent to app.wpshift.io to establish the connection and identify the site in your dashboard.
While connected — the plugin periodically exchanges site status and site health information (WordPress version, plugin version, connection state, and WordPress Site Health results) with app.wpshift.io so your dashboard can show the state of the site. WPShift can request this information through a token-protected endpoint on your site.
Managed SMTP — the plugin fetches your server’s SMTP configuration (host, port, credentials) from app.wpshift.io and applies it to outgoing WordPress email. The credentials are cached briefly on your site; they are not sent anywhere else.
Magic login — when you use magic login from the WPShift dashboard, a one-time token is verified against app.wpshift.io before you are signed in.
Migration — when you explicitly start a migration, a full backup of your site (all files and the complete database) is transferred to the WPShift-managed server you are migrating to. This is the entire purpose of the migration feature and only happens after an administrator confirms it.

No data is sent to any service other than WPShift. See https://wpshift.io for WPShift’s terms and privacy information.
Third Party Libraries
This plugin includes the following third-party libraries:
Alpine.js

Version: 3.14.1
License: MIT
Source: https://github.com/alpinejs/alpine
Website: https://alpinejs.dev

Alpine.js is used for reactive UI components in the admin interface. The minified file assets/js/alpine.min.js is built from the official Alpine.js repository.
To build from source:
1. Clone https://github.com/alpinejs/alpine
2. Run npm install
3. Run npm run build
4. The built file will be in packages/alpinejs/dist/

延伸相關外掛

文章
Filter
Mastodon