| 开发者 | arijit1992 |
|---|---|
| 更新时间 | 2026年7月17日 00:25 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
[capsquery_facial_authentication] shortcode for front-end pages.
How it works
assets/vendor/. Its pretrained model weights are required for the plugin to function and are bundled under assets/models/. Since the raw weight files have no meaningful file extension, each one is stored base64-encoded inside a small .json wrapper file and decoded on request by a plugin REST endpoint — no external network calls or third-party servers are involved.
Requirements
/wp-content/plugins/capsquery-facial-authentication/ or install via Plugins → Add New.On a single site, this is typically users with the any role.
No. The plugin stores an encrypted mathematical face descriptor (128 numbers), not an image.
No. A successful face match must be followed by the correct PIN.
No. Modern browsers block camera access except on HTTPS or localhost.
Use the shortcode: [capsquery_facial_authentication] or [capsquery_facial_authentication redirect="/my-account"]
They are the pretrained face-api.js (MIT-licensed) neural network weights needed for on-device face detection and recognition. The library's raw weight files have no standard file extension, so each one is base64-encoded and wrapped in a .json file; the plugin decodes and streams it back out through its own REST endpoint when the browser loads the model. They are required — the plugin cannot detect or recognize faces without them.