Linux 软件免费装
Banner图

Wolvy Video

开发者 wolvy
更新时间 2026年9月1日 04:03
PHP版本: 7.4 及以上
WordPress版本: 7.1
版权: GPLv2 or later
版权网址: 版权信息

标签

player video streaming watermark drm

下载

1.0.0

详情介绍:

Wolvy hosts, encodes and DRM-protects your video. This plugin puts it on your WordPress site. Once you have added your signing secret, every player it renders for a signed-in viewer carries a signed viewer token: an identifier for the person watching, signed with your Wolvy account's secret so the viewer cannot edit it and watch as somebody else. Wolvy records that verified identifier against each playback session, which is what lets a copy found elsewhere be traced back to the account it came from. You need a Wolvy account to use this plugin. It is a client for that service, not a standalone video host. What it does Who can watch Anyone, by default. A signed-in visitor is identified by a signed token — once a signing secret is configured — so the on-screen watermark and your Wolvy session records name them; a visitor who is not signed in gets an unsigned embed, which Wolvy plays unless your account has watermark enforcement switched on. If you want playback restricted, turn on Require visitors to sign in under Wolvy → Settings, and choose what everyone else sees. Developers can decide per video with the 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.

安装:

  1. Upload the wolvy-video folder to /wp-content/plugins/, or install the zip from Plugins → Add New → Upload.
  2. Activate it.
  3. Go to Wolvy → Settings, paste your API key, and press Verify API key — this discovers your account number automatically.
  4. Paste your viewer signing secret from the Wolvy dashboard and press Verify signing secret.
  5. Check Wolvy → Health before you publish anything.
For the strongest setup, keep the secrets out of the database by defining them in wp-config.php: define( 'WOLVY_API_KEY', 'wv_live_…' ); define( 'WOLVY_VIEWER_SIGN_SECRET', '…' );

屏幕截图:

  • Choosing a video from the block picker.
  • Analytics — daily views and watch time, countries, and recent viewers.
  • The health screen, naming what would break playback.
  • Settings, including verification of the signing secret.

升级注意事项:

1.0.0 First release.

常见问题:

Do I need a Wolvy account?

Yes. This plugin is a client for the Wolvy video platform. Without an account there is nothing for it to display.

The player is blank, or redirects to an error page.

Almost always one of three things, all of which Wolvy → Health checks:

  1. Your site's domain is not on your Wolvy account's allowed-domains list.
  2. Your site sends Referrer-Policy: no-referrer. Wolvy refuses embeds that arrive without a referrer.
  3. The signing secret here no longer matches your account's, because it was rotated in the Wolvy dashboard.

Can I autoplay, hide controls, or change the player's colours?

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.

Does this work with a caching plugin?

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.

Can I upload to Wolvy from WordPress?

Not in this version. Upload in the Wolvy dashboard; the library here picks it up.

Where does the plugin store my API key?

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.

What data does it store about my visitors?

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.

更新日志:

1.0.0