| 开发者 | wolvy |
|---|---|
| 更新时间 | 2026年9月1日 04:03 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
wolvy_can_view filter.
Privacy
Playing a video loads a player from Wolvy's servers, so Wolvy receives your visitor's IP address and user agent. When the viewer is signed in and a signing secret is configured, this site also sends Wolvy an identifier for them — by default a random code only your site can link back to a person, though you may configure it to be a username or email address instead. Visitors who are not signed in are not identified.
The plugin adds suggested text to Settings → Privacy, and registers the stored identifier with WordPress's own personal-data export and erase tools.
wolvy-video folder to /wp-content/plugins/, or install the zip from Plugins → Add New → Upload.wp-config.php:
define( 'WOLVY_API_KEY', 'wv_live_…' );
define( 'WOLVY_VIEWER_SIGN_SECRET', '…' );Yes. This plugin is a client for the Wolvy video platform. Without an account there is nothing for it to display.
Almost always one of three things, all of which Wolvy → Health checks:
Referrer-Policy: no-referrer. Wolvy refuses embeds that arrive without a referrer.Those are account settings in the Wolvy dashboard, and they apply to every embed. The plugin tells you when you have used a shortcode attribute it cannot honour, rather than ignoring it.
Yes. A page rendered for a signed-in visitor carries a token belonging to that one viewer, so the plugin marks it uncacheable with DONOTCACHEPAGE. A page rendered for everyone else carries no token, is identical for every visitor, and caches normally. Every major caching plugin bypasses logged-in visitors by default; if you have deliberately enabled caching for logged-in users, exclude pages with videos.
Not in this version. Upload in the Wolvy dashboard; the library here picks it up.
In the options table, encrypted with a key derived from your site's wp-config.php salts. That protects it if your database alone is exposed. On the rare host with neither libsodium nor OpenSSL it is stored unencrypted, and Wolvy → Health says so. To keep it out of the database entirely, define WOLVY_API_KEY in wp-config.php instead — the constant always wins.
One identifier per signed-in user, in user meta, so a watermark seen on a leaked copy can be traced back to an account. It is registered with WordPress's personal-data export and erase tools.