Kommentti connects your WordPress publication to the Kommentti comment and community service.<\/p>\n\n
Test your theme and full-page\/CDN cache before deploying to a busy publication. The plugin does not promise search indexing, ranking or citation in AI answers.<\/p>\n\n
A Kommentti account and a verified public HTTPS website are required. Free service includes one website and 500 new comments per month. The plugin is free; paid service features and limits are enforced by Kommentti.<\/p>\n\n
The plugin contacts https:\/\/api.kommentti.com only after the administrator configures and permits the service connection. Connection checks send the site ID, site origin and language. Server display sends the site ID, discussion ID, language, page and a private read-only credential in the Authorization header. The credential is never placed in a browser URL or public HTML.<\/p>\n\n
On-site moderation is an optional administrator\/editor workflow. Each WordPress user with moderate_comments permission saves their own personal Kommentti moderation key. It is stored encrypted per user and site. An authenticated, nonce-protected WordPress request sends a short-lived challenge, the configured site origin and this key to the Kommentti grant service. A dedicated iframe receives a one-use grant and displays pending comments only after Kommentti verifies site ownership or assigned moderator rights and the eligible service plan. Keys are not exposed to the browser. Removing a local saved key does not revoke it remotely; revoke it in Kommentti when no longer needed.<\/p>\n\n
The public comment widget loads the documented Kommentti service script and iframe. Visitors connect directly to Kommentti, which receives connection information such as IP address and browser information, and processes account details and submitted comments. Published comments expose the author's display name, text and dates. This plugin does not send analytics or telemetry.<\/p>\n\n
Signed notifications from Kommentti are received at the WordPress REST URL shown in Settings \u2192 Kommentti. These contain event metadata and site\/discussion identifiers, not private account details or comment bodies.<\/p>\n\n
Service: https:\/\/kommentti.com\nTerms of use: https:\/\/kommentti.com\/terms\nPrivacy: https:\/\/kommentti.com\/privacy\nSupport and installation: https:\/\/kommentti.com\/developers\nProvider: Cen Medya Limited \u015eirketi, info@kommentti.com<\/p>\n\n\n
Create a read-only API key under your site's API settings in Kommentti, then save it in the plugin. A Publisher or Media Network service plan is required for this API. Secrets may instead be configured with KOMMENTTI_API_KEY and KOMMENTTI_WEBHOOK_SECRET constants in wp-config.php, optionally populated from environment variables. Do not commit secrets to source control.<\/p>\n\n
Copy the webhook receiver URL from the plugin into Kommentti API settings. Save the signing secret generated there in the plugin, and send a test notification. Saving a webhook in Kommentti rotates its secret; update WordPress with the new value.<\/p>\n\n
The plugin uses WordPress HTTP requests, TLS verification, no redirects, a two-second timeout and bounded response sizes. Valid snapshots are cached for at most 60 seconds. Expired comments are never served during an API outage; the standard Kommentti widget is used instead. API quotas and comment quotas are separate.<\/p>\n\n
Automatic placement replaces the classic comment template or the core Comments block. In custom layouts, select manual placement and insert the Kommentti comments block or [kommentti_comments]. Use one article discussion per page; duplicate rendering is suppressed. For manual layouts remove the theme's native Comments block if you want to show only the Kommentti discussion.<\/p>\n\n
The default discussion ID is the WordPress post ID, matching Kommentti's WordPress WXR import. An administrator may enter an existing discussion ID in the post editor's Kommentti discussion box. Keep the same ID when switching display modes, renaming posts or changing permalinks. Moving posts to another WordPress installation may change post IDs; preserve discussion mappings during migration.<\/p>\n\n
To migrate existing WordPress comments, use Tools \u2192 Export, then preview and approve the WXR file in Kommentti. Imports require Starter or above. Existing WordPress comments are not automatically uploaded or deleted. On-site moderation is available through Comments \u2192 Kommentti with a personal connection on Starter and higher plans. This plugin does not provide server-side comment writing, WordPress visitor-account SSO or automatic two-way comment synchronization.<\/p>\n\n
Password-protected, draft and excluded post types do not load the widget. The WordPress closed-comments setting hides posting in this integration while preserving the hosted discussion. To enforce a lock for all clients, also lock the discussion in Kommentti.<\/p>\n\n
A valid webhook invalidates the matching article's comment snapshot and requests article purges from WP Rocket, WP Super Cache, W3 Total Cache and LiteSpeed when their purge APIs are present. Site-wide events request a site-wide purge. Custom cache integrations can use the kommentti_purge_post and kommentti_purge_site actions.<\/p>\n\n
Cloudflare and other external CDN caches need their own purge or expiry policy. A long-lived HTML cache can keep a removed comment visible even after the plugin cache was invalidated. Test your actual cache stack. WP-Cron is not required for incoming webhook invalidation.<\/p>\n\n
Configuration is per WordPress site. A staging copy with a different host pauses the integration until the administrator reconnects it. Do not share one site's API key across unrelated WordPress sites. Subdirectory publications sharing one hostname require separate planning because domain changes cannot distinguish those copies.<\/p>\n\n
Deactivate the plugin to restore the theme's native comment handling. WordPress comments and hosted Kommentti comments are preserved. Uninstall removes plugin settings, encrypted credentials and cache metadata; existing discussion mappings remain for future reinstallation. Revoke unused server API keys in Kommentti. Rotating WordPress authentication salts makes stored credentials unreadable; re-enter them afterwards.<\/p>\n\n\n
Yes. A Kommentti account is required. Standard embedding works with all service plans, including Free. The read API used for server display requires Publisher or Media Network.<\/p><\/dd>\n
Server mode puts approved comments into the initial page HTML. Reading and pagination work without JavaScript. Account actions, posting, replies and reports require JavaScript. Standard iframe mode requires the service widget.<\/p><\/dd>\n
No. Hosted comments stay in Kommentti. Existing native comments are preserved. Use the service's supported export\/import tools when planning a migration.<\/p><\/dd>\n
No. Readers use their Kommentti account in the inline widget. WordPress user accounts and permissions are not shared with the service.<\/p><\/dd>\n\n<\/dl>\n\n\n