[WordPress] 外掛分享: Flx Headless

首頁外掛目錄 › Flx Headless
全新外掛
安裝啟用
尚無評分
14 天前
最後更新
問題解決
WordPress 6.0+ PHP 7.4+ v1.1.0 上架:2026-08-31

內容簡介

Flx Headless 是一款專為 WordPress 設計的外掛,透過外部 Flx Render 服務渲染頁面,提升網站的靈活性與效能。即使外部服務無法連接,仍可回退至 WordPress 原生渲染,確保訪客始終能看到內容。

【主要功能】
• 支援渲染頁面、文章及分類檔案
• 提供 REST 健康檢查端點
• 自訂 Render URL 設定
• 自動回退至 WordPress 原生渲染
• 顯示全站樣式的公共 REST 端點

外掛標籤

開發者團隊

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

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

原文外掛簡介

Flx Headless renders published WordPress Pages, single Posts, the blog index, category
archives, tag archives, search results, and the 404 page through an external
Flx Render service instead of WordPress’s native template output. If the
Render service is unreachable, returns an error, or a required field is
missing from the payload, Flx Headless falls back to normal WordPress rendering, so
visitors always see a page.
Each route rendered through Flx Headless includes a page title, meta description,
canonical URL, and robots directive where applicable.
Flx Headless also provides:

An admin Flx Headless screen showing the plugin version, configured Render URL,
REST namespace, health endpoint, global styles endpoint, and a Render URL setting.
A public REST health endpoint at /wp-json/flx-headless/v1/health.
A public REST endpoint at /wp-json/flx-headless/v1/global-styles serving
WordPress’s current computed Global Styles CSS.

Menus, comments, and full-site rendering are not covered.
External Services
Flx Headless renders Pages, Posts, the blog index, category and tag archives, search
results, and the 404 page by sending page data to an external Flx Render
service over HTTPS and displaying the HTML it returns. This is required for
Flx Headless to function as a headless rendering integration.
No data is sent anywhere until an administrator configures a Render URL —
either by entering one on the Flx Headless screen and saving it, or with
one click via the dismissible setup notice shown in wp-admin after
activation. Before a Render URL is configured, Flx Headless performs no external
requests and falls back to normal WordPress rendering.
The Render URL is entirely administrator-controlled. It may point to any
service that implements the Flx Render API, including a self-hosted instance;
Flx Headless does not require use of any specific provider.
For each request that Flx Headless renders through the configured service, the
following data is sent, depending on the content being rendered:

Post or page content, title, excerpt, slug, permalink, and featured image
URL.
Post or page ID, publish date, last modified date, and author display
name.
Site name and home URL.
The search query text, for search result pages.
Category or tag title and description, and paginated lists of the post
fields above, for archive and search pages.

No WordPress user account data, credentials, email addresses, or license
keys are transmitted to the Render service.

延伸相關外掛

文章
Filter
Mastodon