by uukidev
0 (0 reviews)
YUI Preview Token
Issue time-limited preview tokens for headless WordPress setups. Open drafts directly in your frontend URL without long-lived credentials.
Compatible with WP 7.0.2
v1.1.2
Current Version v1.1.2
Updated 1 month ago
Last Update on 15 Jun, 2026
Refreshed 13 hours ago
Last Refreshed on
Rank
#51,404
—
No change
Active Installs
0+
—
No change
KW Avg Position
152
—
No change
Downloads
73
—
Total downloads
Support Resolved
0%
—
No change
Rating
0%
Review 0 out of 5
0
(0 reviews)
Next Milestone 10
0+
10+
30,832
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 8 more installs to reach 10+
Rank Changes
Current
#51,404
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
0.0
0 reviews
Overall
0%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Tracked Keywords
Showing 2 of 2Unlock Keyword Analytics
Track keyword rankings, search positions, and discover new ranking opportunities with a Pro subscription.
- Full keyword position tracking
- Historical ranking data
- Competitor keyword analysis
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.1.2
- Last Updated
- Jun 15, 2026
- Requires WP
- 5.9+
- Tested Up To
- 7.0.2
- PHP Version
- 7.4 or higher
- Author
- uukidev
Support & Rating
- Rating
- ☆ ☆ ☆ ☆ ☆ 0
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade Now
Frequently Asked Questions
Common questions about YUI Preview Token
No. Any HTTP client that can call the WordPress REST API works. The plugin returns standard WordPress REST API post objects.
Only draft, pending, and future posts. Published posts are intentionally excluded — they are already publicly accessible.
Yes. Tokens are designed for repeated use within their validity window (e.g. reloading the preview, checking on different screen sizes). Issuing a new token invalidates the previous URL.
The token is rejected with a 401 response. The expired token is automatically deleted by the daily WP Cron job. In the editor UI, the panel shows a fresh "Generate token" view without exposing the expiry state.
By default, yes. The preview endpoint returns a 403 for HTTP requests to protect the token from being intercepted in transit. For local development, add define('PVT_SKIP_HTTPS_CHECK', true); to wp-config.php.
In Settings → YUI Preview Token → Minimum Capability, choose the minimum WordPress role (Subscriber, Contributor, Author, Editor, or Administrator). Users below that role will receive a 403 when attempting to generate tokens.
Yes. You can enter patterns like https://*.example.com to allow all subdomains of a domain. The bare wildcard * is supported but triggers a security warning — prefer specific patterns when possible.
By default, log entries are written via PHP's error_log(), which follows the WP_DEBUG_LOG setting. To write to a dedicated file, add define('PVT_LOG_FILE', '/absolute/path/to/pvt.log'); to wp-config.php.
Yes. When the Classic Editor plugin is active, the token panel appears as a meta box in the post editor sidebar.
Pass the token query parameter directly to the preview endpoint — no authentication headers required: ` GET /wp-json/yui-preview-token/v1/preview?token= ` The token is bound to a specific post at issuance time (stored as a SHA-256 hash in wp_options). The server resolves which post to return from the token alone; the client cannot redirect it to a different post. The response follows the standard WordPress REST API post format (/wp/v2/posts/{id}). The preview URL also includes p=<post_id>, pt=<post_type>, and preview=true parameters so the frontend can determine routing and template selection before making the API call. `javascript const params = new URLSearchParams(location.search) const token = params.get('token') const postType = params.get('pt') // 'post', 'page', or a custom post type slug const res = await fetch(https://wp.example.com/wp-json/yui-preview-token/v1/preview?token=${token}) const post = await res.json() `