| 开发者 |
dvpatel
nakulchandra dallaswebagencyus |
|---|---|
| 更新时间 | 2026年8月14日 18:57 |
| 捐献地址: | 去捐款 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
noindex is sent in both the page markup and the HTTP response headers, so a preview cannot leak into search results.previewflow folder to /wp-content/plugins/.No. The link itself is the credential. Anyone holding it can view the content until it expires or you revoke it. No account is created, and nothing is left behind to clean up.
Practically, no. Each token is 43 random base62 characters — around 256 bits of entropy — generated from the platform's cryptographic random source. It is not derived from the post ID, the title or the date.
The visitor sees a message you can write yourself, rather than a 404. The response uses HTTP 410 Gone, which is the accurate status for something that existed and was deliberately withdrawn.
Yes, immediately. The next request is refused. Because PreviewFlow also stops preview pages ever being written to a page cache, there is no cached copy left behind to keep serving after you revoke.
No. PreviewFlow sends noindex, nofollow, noarchive, nosnippet in both the page markup and the X-Robots-Tag response header.
Yes. A preview is a normal front-end request for the post, so your theme, your builder and your block plugins render it exactly as they render anything else. Elementor, Bricks, Divi, Beaver Builder, Oxygen, Breakdance, Kadence, GenerateBlocks, Spectra and the block editor all work.
Product previews do — enable the product post type in settings and you can share an unpublished product like any other content. Previewing the shop, cart and checkout pages is not included in this version.
Yes. PreviewFlow tells the cache not to store preview responses in the first place, using the standard opt-out that WP Rocket, LiteSpeed Cache, W3 Total Cache, WP Super Cache, NitroPack, Cache Enabler, WP Fastest Cache and others all honour. It also sends Cache-Control: private, no-store so CDNs and shared caches do not hold a copy.
Yes, as many as you like. Give each one a label such as the client's name, its own expiry and its own password. Revoke one without affecting the others, and see the view count for each separately.
Yes, per link. Passwords are hashed with WordPress' own password hashing, and wrong guesses are rate limited per visitor — ten attempts by default, then a fifteen minute cool-down. You can require a password on every new link in settings.
The built-in preview only works for a logged-in user with permission to edit the post. PreviewFlow creates a link that works for anyone you send it to, with an expiry, an optional password and a revoke button.
A published password-protected page is still published: it can appear in feeds, sitemaps, search results and archives. A PreviewFlow link leaves the content unpublished and adds no public footprint at all.
Yes. The prefix is configurable in settings, so links can read /preview/…, /review/… or anything else you like. Changing it invalidates links you have already shared, and the settings screen says so.
Yes. If your site uses plain permalinks, links fall back to a query string form. They are just as secure, only less tidy — the status panel will point this out.
Yes. Drafts, pending review, scheduled and private content all work.
Always. Preview pages bypass every cache layer, so what your client sees is what you last saved.
Only if you leave view tracking on, and never with a raw IP address. Visitors are identified by a one-way salted hash of their IP and browser that cannot be reversed. You choose how long history is kept, and can delete all of it at any time. Switch the whole feature off in settings if you prefer.
No. There is no external service, no analytics, no licence check and no third-party requests. Fonts and assets are bundled with the plugin.
Anyone who can edit the piece of content. Editors and administrators see every link on the dashboard; authors and contributors see the ones they created.
Yes. PreviewFlow → Settings → Tools exports your configuration as JSON and imports it on another site. Preview links themselves are not exported.
Nothing is deleted unless you ask for it. Tick Delete all PreviewFlow data in the Advanced settings before removing the plugin if you want the links, view history and settings removed too.
Yes. Every string is translatable through the previewflow text domain.
noindex in both markup and response headers.