| 开发者 | pidgechat |
|---|---|
| 更新时间 | 2026年10月27日 19:12 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
pidge-live-chat folder to /wp-content/plugins/.Yes. The plugin only adds the widget; the chats are handled by Pidge. Signing up is free, no card needed, and the first 14 days have everything unlocked: app.pidge.chat/#/signup.
Your account stays on the free plan and the chat keeps working: one website, two people replying, live chat, the inbox and webhooks. If your Pidge account has several websites, the oldest one keeps its chat on the free plan and the others pause until you pay. Nothing is deleted. Paying ($10 a month or $100 a year per website) turns everything back on. Nothing in WordPress needs changing either way.
In the Pidge inbox at app.pidge.chat. It works in any browser and can be installed on your phone for notifications. There is no inbox inside wp-admin.
Deactivate your Crisp plugin, install this one and paste your Pidge website ID. If your theme or other plugins call $crisp.push(...), those calls keep working: Pidge accepts the same commands, such as user:email, user:nickname, session:data, chat:open and $crisp.is(...). An identity secret from Pidge works the same way as Crisp's identity verification (HMAC-SHA256 of the email). Past Crisp conversations aren't imported.
Yes. Under Settings → Pidge Live Chat → "Advanced: self-hosted Pidge server", enter its address, for example https://chat.example.com. Developers can set it with the pidge_server_url filter instead.
The settings page can hide it from administrators and on single pages of chosen post types. For anything else, use the pidge_load_widget filter: return false where it shouldn't load.
Most caching plugins don't cache pages for logged-in users, which is what this needs. If yours does, a cached page could carry another user's name and email. Turn off caching for logged-in users, or leave the option off.
That a website ID is saved and the settings page says "Connected"; that you aren't hiding it from administrators while logged in as one; and that your Pidge plan for the site is active. Script optimisers that combine or delay scripts can also stop it loading: exclude client/l.js from them.