Back to Main Site

PolyCMS Permalink and URL Settings for RISE CRM

Last updated on Nov 22, 2026 7:37 AM 7:37 AM 1,988.22 ms

PolyCMS for RISE CRM provides flexible, SEO-friendly URL routing managed from PolyCMS > Permalinks (/polycms/permalink-settings) and stored in {db_prefix}blog_permalink_settings (default rise_blog_permalink_settings). Powered by CodeIgniter 4 dynamic routes, a compiled prefix cache at files/polycms/.blog_prefix_cache.php, and a safe set404Override() handler, PolyCMS lets you customize blog prefixes, post structures, taxonomy bases, and automatic 301 redirects while keeping core RISE CRM routes like /dashboard and /signin completely protected.

Blog Prefix and Root CMS Mode

The Blog Prefix defines the base URL segment under which your blog posts, archives, and search pages live:

Prefix Value Example Post URL Use Case
blog (default) yourdomain.com/blog/sample-post/ Standard company blog alongside RISE CRM
news yourdomain.com/news/sample-post/ Corporate press room or announcements portal
articles yourdomain.com/articles/sample-post/ Public knowledge base and editorial hub
"" (Empty / Root Mode) yourdomain.com/sample-post/ Full Root CMS mode with clean top-level slugs

To prevent collisions with RISE CRM and CodeIgniter 4 internals, PolyCMS automatically blocks reserved prefixes: admin, api, assets, uploads, system, and application.

Protecting RISE CRM /dashboard and /signin

On RISE CRM, the Homepage Redirect setting (polycms_enable_homepage_redirect under PolyCMS > Settings > General) defaults to OFF (0). This deliberate safeguard ensures activating PolyCMS never overrides or blocks your staff login (/signin) or /dashboard workflow by accident.

  • Leave Homepage Redirect turned OFF if your domain root should continue serving the standard RISE CRM entry screen while your CMS lives at /blog or /home.
  • Turn Homepage Redirect ON intentionally only when you want your public CMS homepage (configured under PolyCMS > Settings > Reading) to serve as the primary front door at yourdomain.com/. Even when enabled, direct RISE CRM URLs such as /signin and /dashboard continue to function normally.

Permalink Structures

At PolyCMS > Permalinks, select one of five preset URL patterns or compose a custom structure:

Preset Pattern Example URL
Post Name (Default) %postname% yourdomain.com/blog/sample-post/
Month and Name %year%/%monthnum%/%postname% yourdomain.com/blog/2026/05/sample-post/
Day and Name %year%/%monthnum%/%day%/%postname% yourdomain.com/blog/2026/05/15/sample-post/
Numeric archives/%post_id% yourdomain.com/blog/archives/123/
Plain "" (query string) yourdomain.com/blog?p=123

When crafting custom URL structures, you can combine any of the 10 supported structure tags: %year%, %monthnum%, %day%, %hour%, %minute%, %second%, %post_id%, %postname%, %category%, and %author%. You can also toggle Use Trailing Slash to standardize whether generated links end with /.

Category Base and Tag Base

Customize the URL segments used for taxonomy archives (single path segments without / characters):

  • Category Base - Defaults to category -> yourdomain.com/blog/category/tutorials. Customizing to topics produces yourdomain.com/blog/topics/tutorials.
  • Tag Base - Defaults to tag -> yourdomain.com/blog/tag/rise-crm. Customizing to label produces yourdomain.com/blog/label/rise-crm.

CodeIgniter 4 Routing and Prefix Caching

Unlike static rewrite setups that require editing Apache .htaccess or Nginx rules after every change, PolyCMS resolves routes dynamically at runtime inside plugins/polycms/config/Routes.php:

  1. Prefix Cache File - Whenever you save PolyCMS > Permalinks, PolyCMS writes your active prefix, previous old_prefix, and redirect status code into files/polycms/.blog_prefix_cache.php and automatically clears the frontend HTML page cache in writable/polycms/cache/.
  2. Dynamic Prefix Routes - Routes.php loads .blog_prefix_cache.php on every request with zero database overhead to register /search, /comment/submit, /author/{id}, pagination, taxonomy archives, and post routes under your chosen prefix.
  3. Safe set404Override() Fallback - For root-level CMS pages (such as /about-us) and empty-prefix ("") Root CMS mode, PolyCMS registers a CodeIgniter 4 set404Override() callback that delegates unmatched paths to Frontend::catch_all(). Core RISE CRM routes always resolve first; if a path matches a published CMS page or root-mode post, PolyCMS returns HTTP 200 and renders it; otherwise, it restores a clean HTTP 404 response.

If you ever encounter unexpected 404 errors on frontend pages after migrating servers or editing directories manually, visit PolyCMS > Permalinks and click Save Settings to regenerate files/polycms/.blog_prefix_cache.php.

Automatic Redirect Engine (301 / 302 / 307 / 308)

Changing a blog prefix or updating permalink settings does not have to break indexed links. PolyCMS stores the previous prefix in .blog_prefix_cache.php and routes legacy requests through Frontend::redirect_old_prefix using your selected HTTP status code from PolyCMS > Permalinks:

  • 301 (Moved Permanently) - Recommended default for preserving SEO rankings and passing link equity to new URLs.
  • 302 (Found) - Temporary redirect during short tests.
  • 307 (Temporary Redirect) - Temporary redirect preserving HTTP request method.
  • 308 (Permanent Redirect) - Permanent redirect preserving HTTP request method.

Permalink Best Practices

  • Choose your blog prefix and permalink structure before launching publicly and avoid changing them once search engines index your URLs.
  • Use %postname% (Post Name) for clean, readable, keyword-rich URLs.
  • Keep files/polycms/ writable so .blog_prefix_cache.php updates cleanly whenever you save permalink changes.
  • Verify frontend articles, categories, and RISE CRM /dashboard navigation immediately after switching between prefixed mode and Root CMS mode.

Related Documentation