Configure comments
Site administrators can configure three independent controls under Settings → POM Tweaks → Content → Comments. Enable the control you need, configure its fields, and select Save. Administrator access to the site's settings is required.
Disable comments by post type
- Enable Disable comments by post type.
- Under Disable comments for these post types, select the content types that should not accept discussion. The labels include their identifiers, such as post, attachment, or product.
- Select Save and reopen an editor and a public page for each affected type.
- Check an unselected type as well: its existing comment behavior should remain available.
Selected types stop accepting comments, pingbacks, and trackbacks. Their native comment lists and counts are hidden on content pages, and their discussion, comments, and trackback editing panels and comment columns are removed. Existing comment records and stored post settings are preserved. An empty selection has no effect unless Disable for all current and future post types is selected.
When every registered type that supports comments or trackbacks is disabled, the control automatically closes discussion globally through WordPress filters. It also removes the Comments menu, Settings → Discussion, the toolbar comments link, and native comment metaboxes. Direct access to the native comment administration screens returns to the Dashboard. The Dashboard's Activity widget retains its post activity but omits recent comments. Standard recent-comment widgets and comment blocks are suppressed, and comment feeds return 404 responses.
Attachment comments use this same control: select Media (attachment) under Disable comments for these post types. There is no separate attachment-comments switch under Media. Attachments count toward the global decision just like other comment-capable types. WooCommerce product reviews count as comments; internal order notes do not. Disabling public comments does not delete or block internal order notes.
For a permanent site-wide policy, select Disable for all current and future post types. Otherwise, a newly registered type with comment support can make global comment administration available again until you select that type. Saved selections for temporarily unavailable content types are retained.
Change notification recipients
- Enable Comment notification recipient.
- Enter one valid email address in Comment notification recipient.
- Select Save.
- On a staging site with mail capture, check both a new-comment notification and a moderation notification.
Both recipient lists use this address. Empty or invalid values leave the existing recipients unchanged. This control does not enable notifications that WordPress or another integration has disabled, change the sender identity, or affect unrelated emails.
Remove the website field
Enable Remove the website field and select Save. View a comment form while logged out on content that still accepts comments. The website input disappears; name, email, comment text, consent controls, and other fields remain under their existing rules.
The control handles both WordPress's default fields and the final native form fields. A third-party form that does not use WordPress's comment-form filters needs its own configuration.
Verify and reverse
- With only one type selected, confirm that its editor panels and public comment form disappear while another type remains unaffected.
- With all comment-capable types disabled, reload administration and confirm both comment menu entries disappear. Selecting all current types is enough; the all-current-and-future option is optional.
- To restore a type, clear its selection and the all-current-and-future option, then save. Disable the entire control to restore the site's underlying discussion behavior. WordPress's original per-post status and other plugins can still keep comments closed.
- If comment menus remain, inspect unselected custom types and attachments. Product reviews also require a decision.
- If a theme or plugin displays a separate comment interface, configure that interface too. Existing records remain available to integrations that query them directly; this control is not a data deletion or access-control tool.
- Refresh page caches when verifying public templates. Browser or proxy caches can retain earlier output.