New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| ↑ | AJAX comments with layered spam protection and no CAPTCHA. Threaded replies, load more, and 5 editable notification emails. Free, no pro version. | You have to log in to add a translation. | Details |
Original untranslated
AJAX comments with layered spam protection and no CAPTCHA. Threaded replies, load more, and 5 editable notification emails. Free, no pro version.
You have to log in to edit this translation. |
|||
| ↑ | FluentComments - AJAX Comments, Anti-Spam & Comment Email Notifications | You have to log in to add a translation. | Details |
Original untranslated
FluentComments - AJAX Comments, Anti-Spam & Comment Email Notifications
CommentPlugin name. You have to log in to edit this translation. |
|||
| Only do that when your origin server cannot be reached directly, bypassing the proxy. This setting trusts the header rather than verifying the proxy sent it, so on a directly reachable origin a visitor could set the header themselves and sidestep the per IP limit. It is also worth narrowing <code>fluent_comments/proxy_ip_headers</code> to the one header your proxy actually sets. | You have to log in to add a translation. | Details | |
Original untranslated
Only do that when your origin server cannot be reached directly, bypassing the proxy. This setting trusts the header rather than verifying the proxy sent it, so on a directly reachable origin a visitor could set the header themselves and sidestep the per IP limit. It is also worth narrowing <code>fluent_comments/proxy_ip_headers</code> to the one header your proxy actually sets.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| If yours does not, every visitor looks like the same address. The limit that matters follows a per visitor cookie rather than the IP, so nobody gets locked out, but the loose per IP ceiling then applies to the whole site at once. You can opt into reading proxy headers: | You have to log in to add a translation. | Details | |
Original untranslated
If yours does not, every visitor looks like the same address. The limit that matters follows a per visitor cookie rather than the IP, so nobody gets locked out, but the loose per IP ceiling then applies to the whole site at once. You can opt into reading proxy headers:
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Usually not. Most managed hosts, and the Cloudflare plugin, put the visitor's real address into <code>REMOTE_ADDR</code> for you, and FluentComments reads it from there. | You have to log in to add a translation. | Details | |
Original untranslated
Usually not. Most managed hosts, and the Cloudflare plugin, put the visitor's real address into <code>REMOTE_ADDR</code> for you, and FluentComments reads it from there.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Yes, unless they are logged in. FluentComments always asks a logged out commenter for both, and it does not follow the WordPress "Comment author must fill out name and email" setting, which is why that option is not on our settings screen. The reason is the notification emails: every one of them is addressed by the commenter's email, so an anonymous comment quietly opts its author out of the reply notifications everybody else in the thread receives, and leaves you nothing to moderate on. Logged in commenters are never asked, because WordPress already has both from their account. The WordPress setting itself is untouched and still applies to any post type FluentComments is not handling. | You have to log in to add a translation. | Details | |
Original untranslated
Yes, unless they are logged in. FluentComments always asks a logged out commenter for both, and it does not follow the WordPress "Comment author must fill out name and email" setting, which is why that option is not on our settings screen. The reason is the notification emails: every one of them is addressed by the commenter's email, so an anonymous comment quietly opts its author out of the reply notifications everybody else in the thread receives, and leaves you nothing to moderate on. Logged in commenters are never asked, because WordPress already has both from their account. The WordPress setting itself is untouched and still applies to any post type FluentComments is not handling.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Yes. Use the <code>fluent_comments/form_fields</code> action to render them and <code>fluent_comments/validate_submission</code> to check them. They work identically on the block, the shortcode and the classic template. Because fields ship with the per request session payload rather than the cached page, anything time sensitive in them stays fresh. | You have to log in to add a translation. | Details | |
Original untranslated
Yes. Use the <code>fluent_comments/form_fields</code> action to render them and <code>fluent_comments/validate_submission</code> to check them. They work identically on the block, the shortcode and the classic template. Because fields ship with the per request session payload rather than the cached page, anything time sensitive in them stays fresh.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Yes, all five of them. Rewrite the subject and body of any email, use smartcodes like <code>{{comment.author}}</code> and <code>{{post.title}}</code>, preview it against a real comment from your site, and set a shared logo, color scheme, footer and From/Reply-To address for all of them. WordPress's own two notices are left untouched unless you explicitly choose to replace them. | You have to log in to add a translation. | Details | |
Original untranslated
Yes, all five of them. Rewrite the subject and body of any email, use smartcodes like <code>{{comment.author}}</code> and <code>{{post.title}}</code>, preview it against a real comment from your site, and set a shared logo, color scheme, footer and From/Reply-To address for all of them. WordPress's own two notices are left untouched unless you explicitly choose to replace them.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| The exception is "Comment author must fill out name and email", which FluentComments always applies to its own form whatever that box is set to. See the question below for why. | You have to log in to add a translation. | Details | |
Original untranslated
The exception is "Comment author must fill out name and email", which FluentComments always applies to its own form whatever that box is set to. See the question below for why.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Yes, with one exception. Threading depth, moderation keywords, disallowed keywords, the link limit, "comment author must have a previously approved comment", "users must be registered and logged in": all of them are real WordPress options that FluentComments reads and writes in place. The most useful ones are surfaced on the FluentComments screen so you do not have to go hunting for them. | You have to log in to add a translation. | Details | |
Original untranslated
Yes, with one exception. Threading depth, moderation keywords, disallowed keywords, the link limit, "comment author must have a previously approved comment", "users must be registered and logged in": all of them are real WordPress options that FluentComments reads and writes in place. The most useful ones are surfaced on the FluentComments screen so you do not have to go hunting for them.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Yes. Every color, spacing value and radius is a CSS custom property, so a handful of <code>--fcom-*</code> overrides in your theme will restyle the whole thing. The block also exposes its title, avatars, colors and border radius in the editor sidebar. | You have to log in to add a translation. | Details | |
Original untranslated
Yes. Every color, spacing value and radius is a CSS custom property, so a handful of <code>--fcom-*</code> overrides in your theme will restyle the whole thing. The block also exposes its title, avatars, colors and border radius in the editor sidebar.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Yes. FluentComments uses the normal WordPress comments table and the normal WordPress comment functions. Nothing is migrated, copied or moved. These are your existing comments, displayed and protected better. Deactivate the plugin and your comments are still exactly where they were. | You have to log in to add a translation. | Details | |
Original untranslated
Yes. FluentComments uses the normal WordPress comments table and the normal WordPress comment functions. Nothing is migrated, copied or moved. These are your existing comments, displayed and protected better. Deactivate the plugin and your comments are still exactly where they were.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| No. The first page of comments is rendered into the page itself, so a visitor who only reads never triggers an extra request. There is no webfont, no external service and no third party script. Comments load in pages rather than all at once. | You have to log in to add a translation. | Details | |
Original untranslated
No. The first page of comments is rendered into the page itself, so a visitor who only reads never triggers an extra request. There is no webfont, no external service and no third party script. Comments load in pages rather than all at once.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Yes, and it is designed for it. Nothing visitor specific is printed into the page, so a cached comment form is still a valid one. There is no security nonce anywhere in the plugin, which means a form served from cache can never fail with the "your session has expired" error that nonce based forms hit. Everything per visitor is fetched on demand, only when someone actually goes to comment. | You have to log in to add a translation. | Details | |
Original untranslated
Yes, and it is designed for it. Nothing visitor specific is printed into the page, so a cached comment form is still a valid one. There is no security nonce anywhere in the plugin, which means a form served from cache can never fail with the "your session has expired" error that nonce based forms hit. Everything per visitor is fetched on demand, only when someone actually goes to comment.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Yes. Drop the <code>[fluent_comments]</code> shortcode into any builder's shortcode or text widget and the full comment list and form render there. | You have to log in to add a translation. | Details | |
Original untranslated
Yes. Drop the <code>[fluent_comments]</code> shortcode into any builder's shortcode or text widget and the full comment list and form render there.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
Export as
Comment
Short description.