Back to Main Site

PolyCMS Troubleshooting & Common Issues for RISE CRM

Last updated on Nov 22, 2026 11:46 AM 11:46 AM 1,919.67 ms

This troubleshooting guide helps RISE CRM administrators diagnose and resolve the most frequent PolyCMS issues, including frontend 404 routing errors, role permission blocks, media upload failures, sub-plugin conflicts, theme or cache mismatches, and post-migration database errors. Follow the targeted checklist below to restore full CMS functionality safely without losing content.

404 Errors on Frontend Pages

Symptom: Public blog posts, category archives, or static CMS pages return a 404 Page Not Found response.

Resolution:

  1. Navigate to PolyCMS > Permalinks (/polycms/permalink-settings).
  2. Click Save Settings even if you did not change any field. This regenerates the routing cache file at files/polycms/.blog_prefix_cache.php.
  3. Verify that files/polycms/ is writable by the web server user so .blog_prefix_cache.php can be written.
  4. Confirm your web server rewrite rules are active: mod_rewrite with AllowOverride All on Apache, or a proper try_files $uri $uri/ /index.php?$query_string; rule on Nginx.
  5. Clear your browser cache and reload the frontend URL.

Permission Denied or Missing PolyCMS Sidebar Menu

Symptom: A staff member cannot see the PolyCMS or Appearance menus, or sees an access-denied message when opening a CMS screen.

Resolution:

  1. Log in as a RISE CRM Administrator and navigate to Settings > Access Permission > Roles.
  2. Open the role assigned to the affected staff member and scroll to the PolyCMS permissions section.
  3. Enable the required granular capabilities:
    • polycms_view (PolyCMS: View) - Browse dashboard, posts, pages, categories, tags, comments, and media.
    • polycms_create (PolyCMS: Create) - Create new posts, pages, and taxonomy terms.
    • polycms_edit (PolyCMS: Edit) - Edit content, publish or unpublish items, and moderate comments.
    • polycms_delete (PolyCMS: Delete) - Permanently delete CMS content and media.
    • polycms_settings (PolyCMS: Settings) - Manage PolyCMS Settings, Permalinks, Plugins, Themes, and Tools.
  4. Click Save and ask the staff member to refresh RISE CRM.

RISE Administrators and roles with can_manage_all_kinds_of_settings automatically have full PolyCMS access without manual role toggles.

Media Upload Failures and Cache Write Errors

Symptom: Uploading images in PolyCMS > Media fails, or HTML caching, SQL backups, and HTMLPurifier report write errors.

Common Causes and Fixes:

Cause Fix
Directory not writable Ensure both files/polycms/ and writable/polycms/ (including cache/, rate_limit/, backups/, and htmlpurifier/) exist and have writable permissions (755 or 775, owned by your web server user).
File exceeds PHP limits Increase upload_max_filesize and post_max_size in php.ini and restart PHP-FPM or Apache.
Blocked file format PolyCMS restricts uploads to safe, allowed formats (jpg, jpeg, png, gif, webp, svg, pdf). Convert unsupported files before uploading.
Disabled PHP upload function Confirm move_uploaded_file and the PHP fileinfo extension are enabled in your server's PHP 8.1+ configuration.

Theme Not Rendering Correctly

Symptom: The public blog shows broken styling, unstyled HTML, or missing layout elements.

Resolution:

  1. Go to Appearance > Themes (/polycms/themes) and confirm an active theme (such as Head Random) is enabled.
  2. Verify that all theme files exist intact under plugins/polycms/themes/<theme-slug>/ and match the original package.
  3. Open PolyCMS > Settings > Performance (#tab-performance) and click Clear Cache to flush stale cached HTML in writable/polycms/cache/.
  4. Flush server-side PHP OPcache or reverse-proxy caches (Cloudflare, Nginx FastCGI cache, Varnish).
  5. Open your browser Developer Tools (Console and Network tabs) to check for 404 asset paths or mixed-content (http:// vs https://) blocks.

Sub-Plugin Conflicts or Fatal Errors

Symptom: Activating a custom or third-party sub-plugin triggers a PHP error or makes the admin screen unresponsive.

Resolution:

  1. If you can access the admin panel, go to PolyCMS > Plugins and click Deactivate on the problematic sub-plugin.
  2. If the admin UI is inaccessible, connect via FTP, SFTP, or SSH to {rise_crm_root}/plugins/polycms/plugins/ and temporarily rename the faulty sub-plugin folder (for example, rename my-plugin to my-plugin.disabled).
  3. Reload RISE CRM, inspect writable/logs/ for the exact CodeIgniter 4 stack trace, and resolve the conflict before re-enabling the sub-plugin.

Comments Not Appearing on Posts

Symptom: Visitors submit comments on the frontend, but the comments do not appear below the article.

Checklist:

  • Pending Moderation: Open PolyCMS > Comments and approve pending comments.
  • Disabled on the Specific Post: Edit the post in PolyCMS > Posts and confirm comments are enabled for that article.
  • Disabled Globally: Navigate to PolyCMS > Settings > General (#tab-general) and confirm global comments are turned on.
  • Cached HTML Page: Clear the frontend HTML cache in PolyCMS > Settings > Performance so newly approved comments render immediately.

Slow Frontend Page Loads

Symptom: Public pages or archive listings take noticeably long to load.

Optimization Steps:

  1. Enable built-in frontend HTML page caching in PolyCMS > Settings > Performance (writable/polycms/cache/) and set an appropriate cache duration.
  2. Enable PHP OPcache on your server so CodeIgniter 4 and PolyCMS PHP files are served from memory.
  3. Compress featured images and inline graphics before uploading (prefer WebP or optimized JPEG).
  4. Review active third-party sub-plugins or external embed scripts that may block frontend rendering.

Database Errors After Server Migration

Symptom: PolyCMS displays SQL table-not-found or connection errors after moving RISE CRM to a new server or changing database prefixes.

Resolution:

  1. Confirm that core RISE CRM screens (Dashboard, Clients, Invoices) load normally so you know the primary database connection in .env / app/Config/Database.php is healthy.
  2. Verify that all 19 PolyCMS tables ({prefix}blog_*) were imported with the exact table prefix configured for RISE CRM.
  3. Navigate to Settings > Plugins in RISE CRM, deactivate PolyCMS, and reactivate it. Reactivation runs polycms_install_schema() from plugins/polycms/index.php idempotently, recreating any missing tables or default seed records without overwriting existing posts.

Need Additional Help?

If your issue is not resolved by the steps above, gather the relevant error log from writable/logs/, your RISE CRM version, and your PHP version, then contact us via the PolyXGO CodeCanyon support page.

Related Documentation