Comments and Moderation in PolyCMS for RISE CRM
PolyCMS for RISE CRM includes a native commenting and moderation system that lets visitors discuss published articles through multi-level threaded replies while keeping staff in full control. You configure global discussion settings under PolyCMS > Settings > General, review incoming submissions at PolyCMS > Comments, and rely on built-in IP rate limiting stored in writable/polycms/rate_limit/ to block spam floods.
Enabling and Controlling Comments
Discussion visibility can be managed globally across the site or overridden on individual blog posts.
Global Setting
Navigate to PolyCMS > Settings > General (/polycms/settings#tab-general) to turn comments on or off site-wide across your CMS frontend.
Per-Post Override
When creating or editing an article under PolyCMS > Posts, toggle the Allow Comments option in the post settings panel. This per-post control lets you disable discussions on legal notices or press announcements while keeping comments active on tutorials and guides.
Comment Moderation Workflow
All visitor comments are stored in {db_prefix}blog_comments (default rise_blog_comments) and managed from PolyCMS > Comments (/polycms/comments). The moderation list supports status filtering, keyword search, and column sorting (such as sorting by date or status) for rapid review.
Comment Statuses
| Status | Description |
|---|---|
| Pending | Newly submitted comment waiting in the queue for staff approval |
| Approved | Published comment visible to all frontend visitors |
| Spam | Flagged as spam and hidden from public display |
| Trash | Soft-removed comment queued for permanent deletion |
Single-Item and Bulk Moderation Actions
Depending on assigned RISE CRM role permissions (polycms_edit and polycms_delete under Settings > Access Permission > Roles), moderators can perform the following actions individually or via Bulk Actions across multiple selected comments:
- Approve - Publish the comment immediately on the frontend article page.
- Spam / Unspam - Mark unwanted submissions as spam to hide them, or restore false positives out of the spam queue.
- Reply - Post an official staff response nested directly beneath the reader's comment.
- Edit - Adjust comment wording when minor moderation is needed while preserving a constructive contribution.
- Trash - Move comments out of active queues into the Trash filter.
- Delete - Permanently erase a comment record from
{db_prefix}blog_comments(requirespolycms_deletepermission).
Multi-Level Threaded Replies
PolyCMS supports nested conversation threads. Whenever a visitor or staff member replies to an existing comment, the response is linked via its parent comment ID and rendered indented beneath the parent entry, making multi-participant discussions easy to follow.
IP-Based Rate Limiting
Public comment submission endpoints (/{blog_prefix}/comment/submit), alongside public frontend search endpoints, are guarded by an automated IP-based rate limiter. Rate-limit tracking data is stored privately inside:
{rise_crm_root}/writable/polycms/rate_limit/
When an IP address exceeds the submission frequency threshold, rapid automated bot requests are throttled automatically before flooding your moderation queue. Make sure the writable/polycms/ directory remains writable by your PHP web server user.
Recorded Comment Data
Each comment entry stored in {db_prefix}blog_comments records:
- Author display name and email address
- Sanitized comment body content
- Creation timestamp
- Submitter IP address (for moderation and abuse review)
- Parent comment ID (for threaded hierarchy)
- Linked post ID and moderation status
Related Documentation
- Managing Posts in PolyCMS for RISE CRM - Enable or disable comments per article.
- PolyCMS Troubleshooting and Common Issues for RISE CRM - Resolve directory permission issues affecting
writable/polycms/rate_limit/and comment forms.