| 开发者 |
DropTheme
Dropndot |
|---|---|
| 更新时间 | 2026年11月20日 18:20 |
| PHP版本: | 7.2 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
/preview/post-slug/ or /api/preview) for draft and preview links, with the preview query string preserved.news/technology), so hierarchical frontend routes are preserved. Existing single-level mappings keep working unchanged./my-post/ instead of /products/my-post/).http://localhost:3000 are supported for link rewriting and redirects.Frontend View For Headless CMS and press Enter.frontend-view-for-headless-cms folder to /wp-content/plugins/.Yes. It only rewrites admin links to URLs you configure. Your frontend can be built with Next.js, Nuxt, Gatsby, Astro, React, Vue, or any other stack.
After activation, open Frontend View Settings. On the General tab, enter your frontend site URL. Optionally enable frontend redirects, a custom preview path, and secure authenticated preview. On the Slug Mapping tab, set the author slug and map taxonomy or CPT path segments to match your frontend routing.
Yes. Enable Redirect frontend requests to headless frontend on the General tab. Public page requests are redirected with a 301 to the matching URL on your frontend. Admin, REST API, GraphQL, feeds, sitemaps, previews, login, and similar backend endpoints are never redirected. The option is off by default.
Yes. Public custom post types shown in the admin UI appear under Post type / CPT slug overrides on the Slug Mapping tab, where you can set a custom segment or enable Empty slug to drop the CPT base from links.
Yes. Slug fields accept nested paths such as news/technology or blog/category/updates. Each path segment is sanitized individually, so the / separators are preserved while the value stays slug-safe. Existing single-level mappings continue to work unchanged.
Yes. Local URLs such as http://localhost:3000 or http://127.0.0.1:3000 are accepted for link rewriting and redirects. The plugin only builds links and browser redirects to the URL; it does not make server-side requests to it.
By default, your settings are preserved when the plugin is deleted, so removing and reinstalling keeps your configuration. If you want deletion to also remove the saved settings, enable Delete all plugin settings when the plugin is deleted on the General tab before deleting.
Enable secure authenticated preview on the General tab. When an authorized editor previews unpublished content, the plugin verifies their capability in wp-admin and issues a short-lived (120-second), single-use, HMAC-signed token in the preview URL. Your Next.js frontend's /api/preview route exchanges that token (server-to-server) for an opaque preview session stored in an httpOnly cookie, then fetches the draft from a token-gated WordPress endpoint. Sessions use a 20-minute sliding and 30-minute absolute expiry and can be revoked. Previewable statuses are draft, pending, private, and scheduled; published content is served normally. No permanent secret ever appears in a URL, the signing secret can be rotated, and the public REST API is not changed. The feature is off by default and requires the matching Next.js integration (documented in full on the Next.js Preview tab).
On the Diagnostics tab, click Run Diagnostics. It makes a single request to your saved frontend URL and reports whether it is reachable, the HTTP status, the response time, and whether TLS/SSL verified. For security it only tests the configured URL (never an arbitrary one), verifies the certificate, blocks requests to private, loopback, link-local, reserved, or cloud-metadata addresses (IPv4 and IPv6), and validates each redirect hop. Local and private-network frontend URLs (for example http://localhost:3000) are skipped with a note rather than probed, and runs are rate-limited.
Yes. On the Tools tab, use Export Settings to download your configuration as a versioned JSON file, then use Preview Import on the other site to upload it. You will see a preview of exactly what would change and must click Confirm Import before anything is applied. If the file is invalid, from a newer plugin version, or contains no recognized settings, the import is rejected and your existing settings are preserved. Secret values are never included in an export and can never be set through an import.
When you configure slug mappings, the plugin analyzes them and shows advisory warnings for configurations that may not behave the way you expect. These warnings never change your settings and never block saving. Detected issues include:
news/technology is overridden by the mapping on its first segment (news), so its intended destination is never produced. Consistent nested mappings (for example news → articles together with news/technology → articles/technology) are not flagged.wp-admin, wp-json, feed, or sitemap.When enabled for a taxonomy or post type, the plugin removes that base path segment from generated URLs. For example, /products/my-item/ can become /my-item/ on your frontend if your routes are flat.
Yes, the plugin is compatible with multisite installations. Configure the frontend URL per site as needed.
Yes, both HTTP and HTTPS frontend URLs are supported.
fvhc/v1/preview/*; the public REST API and existing permissions are unchanged.manage_options, nonce) with per-user rate limiting. Results never expose resolved IPs, headers, response bodies, server paths, or raw transport errors.fvhc-settings, version 1) and import it on another site.fvhc_get_managed_option_names(), now reused by export, import, and uninstall cleanup.news → articles with news/technology → articles/technology) are recognized as valid and are not flagged, matching the engine's first-path-segment rewriting behavior.?p=123), and old-slug redirects resolve first, avoiding non-canonical redirect chains.http://localhost:3000) now work for the 301 redirect, consistent with link rewriting, without weakening wp_safe_redirect() host validation.news/technology are preserved instead of being flattened. Existing single-level mappings are unchanged.http://localhost:3000) for link rewriting and redirects./preview/ slug will be used for preview posts, pages etc.