| 开发者 | ivanchibo |
|---|---|
| 更新时间 | 2026年11月2日 00:34 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
New accounts use their Public Frica ID, such as FID-7K9MX4QP2N8C. A local collision adds a suffix such as -2; usernames never determine account linking. Missing or invalid Public IDs use a private generated fallback. On single sites, legacy frica_ usernames followed by 24 hexadecimal characters switch on the next verified Frica sign-in. Custom usernames and shared Multisite usernames stay unchanged. Migration preserves account data and author URLs, invalidates old sessions and creates a fresh session for that sign-in.
The login page shows a specific safe error and a support reference. Administrators can open Settings > Frica ID > Last sign-in diagnostic to match that reference to the last failure stage, code and fixed reason category. Only the latest record is kept, for 24 hours, without tokens, authorization codes, passwords, emails or provider response bodies. Clock differences up to 30 seconds are tolerated during verification; expired tokens remain rejected. Larger differences require fixing server time synchronization.
Yes. Sign into WordPress with your existing method, open your own Profile, and choose Connect Frica ID. Connecting preserves existing permissions. Connection requires the same WordPress browser session throughout the flow.
An email match alone is not proof of ownership of a local WordPress account. Sign into that WordPress account normally first, then connect Frica ID from Profile. The plugin never silently merges accounts.
Yes. It is disabled by default in the plugin. Existing connected members can continue signing in. Enabling it also requires WordPress's Anyone can register setting. WordPress Multisite does not allow account creation through this plugin.
Activate and configure the plugin separately for each site. Network-wide activation is intentionally blocked. Existing network users must already belong to the selected site, sign into that site, and explicitly connect their account there. Each site's application and redirect URI must be configured separately.
Frica ID authenticates the user; WordPress creates the local session. The plugin runs wp_authenticate_user and wp_login hooks, but password-specific challenges and custom login workflows may need integration. Test your installed security and membership plugins before rollout. Configure your required identity assurance and two-factor controls in Frica ID. The plugin does not disable WordPress password login.
No. WordPress logout ends the local WordPress session. Frica ID's browser session remains independent; this plugin does not implement global logout.
Disconnect removes the local connection without deleting the WordPress user. Confirm your WordPress password or email recovery works first. Deactivation keeps settings and connections; deleting the plugin removes its own settings, temporary transactions and connections. WordPress user accounts and content remain.
State must be used once, within ten minutes, in the same browser. Secure cookies must be allowed. Retry from the login page, check HTTPS/reverse-proxy configuration, and verify callback routes are not cached.