內容簡介
總結文案：Post Forwarder 是一個強大的 WordPress 外掛，使用 REST API 可自動將文章轉發到多個 WordPress 站點，非常適合內容聯播、多站點網絡或在相關網站之間分發內容。
1. 這個 WordPress 外掛的主要功能是什麼？
- 可以自動將文章轉發到多個 WordPress 站點
- 適用於內容聯播、多站點網絡或分發內容給相關網站
2. 這個外掛的特點有哪些？
- 支持多個目的地 WordPress 網站的配置
- 自動映射自定義分類或回退到常規標籤
- 上傳並在目的地網站上設置精選圖片
- 支持任何公共文章類型
- 智能鎖定機制防止重複文章
- 傳輸 Advanced Custom Fields 數據
- 靈活的配置，可以使用易於使用的界面或高級的 JSON 配置
- 選擇性的推送，可以選擇將每篇文章推送到哪些網站
- 配置推送文章是作為草稿還是已發佈
3. 如何使用這個外掛？
- 配置目的地 WordPress 站點（入口網站）及其 REST API 憑證
- 編輯文章時，選擇要將文章推送到哪些入口網站
- 保存後，外掛將自動將文章及其所有內容、分類、元字段和精選圖片推送出去
- 智能的分類映射試圖保留自定義分類，如有必要則回退到常規標籤
4. 外掛最適合哪些用途？
- 擁有多個網站的新聞網絡
- 在相關網站之間進行內容聯播
- 多品牌公司分享內容
- 博客網絡和內容分發
- 開發 / 分析到生產流程
5. 這個外掛的技術需求是什麼？
- 目的地網站啟用了 WordPress REST API
- 配置應用程序密碼以訪問 API
- PHP 7.4或更高版本
以上是關於 WordPress 外掛「Post Forwarder」的介紹及相關問答。
外掛標籤
開發者團隊
原文外掛簡介
Post Forwarder lets you syndicate content from one WordPress site to any combination of destinations with a single click at publish time — or schedule it ahead with the built-in calendar. Configure as many portals as you need and choose per-post which ones receive each article.
Supported Destinations
WordPress sites — forwards via the REST API with taxonomy mapping, featured image upload, ACF field support, and duplicate prevention. One-click authorization using WordPress Application Passwords, or enter credentials manually.
LinkedIn — posts as a link-share article card with your excerpt, featured image thumbnail, and hashtags auto-generated from your WordPress post tags. Supports personal profiles and organisation pages. One-click connect — no configuration required.
X (Twitter) — posts the title and post URL as a tweet; the featured image attaches directly on paid API tiers or appears as a link preview card. Connect with your own free X developer app.
Plan ahead with the content calendar
Post Forwarder includes a built-in weekly calendar so you can do more than fire-and-forget on publish. Schedule posts to go out to your connected channels at the time that suits you, see everything that’s queued at a glance, and manage upcoming posts across all your WordPress sites, LinkedIn, and X from one screen. Great for keeping a steady publishing rhythm without babysitting the clock.
WordPress forwarding highlights
One-click “Save & Connect with WordPress” using the built-in Application Password flow.
Taxonomy mapping with automatic fallback to tags.
Featured image, ACF fields, and custom post types are carried across.
Duplicate prevention so the same post is never forwarded twice.
LinkedIn highlights
Zero-configuration connect — click “Connect with LinkedIn” and authorize in one step.
Featured image is uploaded directly to LinkedIn and shown as the article thumbnail.
WordPress post tags become LinkedIn hashtags automatically (the tag “my topic” becomes #MyTopic).
Supports personal profiles and organisation pages.
Token expiry is shown in settings, with a reconnect prompt before it lapses.
Compatibility
Tested with WordPress 7.0 and PHP 8.3.
Platform Requirements & Limitations
WordPress
The destination site must run WordPress 5.6+ with the REST API enabled (default).
The connecting user must have at least the Editor role on the destination site.
Use “Save & Connect with WordPress” for one-click Application Password authorization, or enter a username and Application Password manually.
No extra configuration required — one-click connect handles sign-in.
LinkedIn access tokens expire after 60 days. The plugin shows the expiry date and prompts you to reconnect.
For organisation page posts set the Author URN to urn:li:organization:YOUR_ORG_ID. You’ll also need the Community Management API product approved on the LinkedIn app (not needed for personal profile posts).
LinkedIn needs the post URL to be publicly reachable to show an article card. Posts from localhost or .local/.test domains fall back to image-only or text+URL mode.
X (Twitter)
You need a free X developer account to post tweets. X limits write access per developer app, so each plugin user connects their own app.
Step 1 — Create an X developer account (one-time)
Go to developer.x.com and sign in with your X account.
Click Sign up and agree to the terms — your developer account is created instantly.
Step 2 — Create an app and get credentials
In the Developer Portal go to Apps and click Create App.
Give it any name (e.g. “My Post Forwarder”).
Open the app, click Keys & Tokens then User authentication settings then Set up.
Set:
App permissions: Read and write
Type of App: Web App, Automated App or Bot
Callback URI: the callback URL shown in the plugin’s X portal settings
Website URL: your site URL
Click Save and copy the Client ID and Client Secret (the secret is shown only once).
Step 3 — Connect in the plugin
In Post Forwarder -> Settings -> Connection Configuration, add an X portal.
Enter the Client ID and Client Secret you copied.
Click Save Portals, then click Save & Connect with X.
Authorize the app on X and you are redirected back with a “Connected” badge.
Notes:
* The free tier allows 1,500 tweet writes per month. Each user’s app has its own separate quota.
* X access tokens are long-lived and refreshed automatically before expiry.
* Featured images on the free tier appear as link preview cards (public sites only), not as direct attachments. The X Basic plan enables direct image upload.
External Services
Post Forwarder only sends data when you choose to connect an account or forward a post — nothing is sent in the background.
To publish to LinkedIn or X (Twitter), the plugin uses a small open-source connection helper to handle the secure sign-in step, then sends the post you’re forwarding (such as its title, link, and image) to the network you connected. WordPress-to-WordPress forwarding talks only to the site you set up.
You stay in control: connect or disconnect any destination at any time, and advanced users can self-host the connection helper. Each network’s handling of the content you send is governed by its own terms:
LinkedIn — Terms · Privacy
X (Twitter) — Terms · Privacy
Technical Notes
Security:
* OAuth tokens are stored in the WordPress database. Enable at-rest encryption on your host for best protection.
* Sensitive fields (access tokens, client secrets, passwords) are never echoed back to the browser — submitting a blank field preserves the saved value.
* All form inputs are sanitized and validated; WordPress nonces protect all forms and OAuth callbacks.
Tested with:
* WordPress 7.0
* PHP 8.3
Minimum Requirements:
* WordPress 5.6+
* PHP 7.4+
