Modus Internet : Located in Vancouver and Burnaby British Columbia we do website design, database integration, custom programming, search engine optimization (SEO) or consultation.
Current Location: Home / Products / Custodian CMS / Flowchart



This page has been written to help explain the process Custodian CMS goes through when parsing a URI request. The Custodian CMS flowchart is available for download in two formats.

Custodian CMS Flowchart PNG Custodian CMS Flowchart PDF

More Detailed Breakdown

Custodian CMS Flowchart Breakdown 1
  1. A user clicks on or types in a link directed at any page located in a Custodian CMS maintained website.
    2. ( Would result in the /ccmstpl/error404.php page being called. )
    8. ( Would probably result in the /ccmstpl/error.php page being called. )
Custodian CMS Flowchart Breakdown Part 2
  1. As of 2013-05-21 there are approximately 140 lines of configuration and security code found in the .htaccess template. If a user request makes it through them all the incoming URI will be converted from something more SEO friendly to a proper php call and the /index.php template will be called.
  2. If the user request fails your webserver will determine the type of error generated and direct the user to the appropriate error template which may contain links to CSS, JavaScript or image resources.
Custodian CMS Flowchart Breakdown Part 3
  1. The /index.php template will load the /ccmspre/config.php, the /ccmspre/user_whiteList.php and the /ccmspre/index.php templates into memory.
  2. It will then connection to the website database in order to establish a persistent connection which will save server resources and load time when calling the database at any point in the future.
Custodian CMS Flowchart Breakdown Part 4
  1. The /ccmspre/index.php template loads the language function, sets the preferred language variable and saves it into a cookie named ccms_vlng.
  2. A ccms_vid cookie is searched for, but not required, cleaned, timestamp corrected, resubmitted to the user and checked against the database where it is timestamp corrected again. The ccms_vid cookie is typically not required but does contain an md5 code which can be used to help secure forms from XSS or to move between secure and non secure versions of the same website.
  3. The Content-Type header is written and immediately returned.
  4. The template requested in the URI is searched for on the server. ( File Pars )
    • If the file is not found the /ccmstpl/error.php template is called which may contain links to CSS, JavaScript or image resources.
    • If the file is found it is parsed for CCMS tags which indicate areas of data replacement.
  5. CCMS_DB tags search the database for content associated with the tag in the appropriate language as set in the ccms_vlng cookie.
    • {CCMS_DB:common,content_area_1}
    • {CCMS_DB:index,form_submit_button}
    • {CCMS_DB:forms,request_more_info_text1}
  6. CCMS_LIB tags search for a template named in the tag, stored in the /ccms_lib folder. If the template is loaded then it will try to call the funtion specified in the tag. ( This is done to help keep large amount of programming code out of HTML code. )
    • {CCMS_LIB:_default.php;FUNC:ccms_cfgDomain}
    • {CCMS_LIB:cms/_123.php;FUNC:XyZZy123_}
    • {CCMS_LIB:test/dir/indeX_Asdf-123.php;FUNC:cfgindeX_Asdf123("arg1", "arg2")}
  7. CCMS_TPL tags typically inject repetitive HTML snippets like headers and footers but they may contain anything, including PHP code or other tags and may be located anywhere withing the /ccms_tpl dir.
    • {CCMS_TPL:header.tpl}
    • {CCMS_TPL:somedir/footer.php}
    • {CCMS_TPL:products/list.html}
Custodian CMS Flowchart Breakdown Part 5
  1. If all goes well and no errors are encountered the HTML is sent to the user and their browser makes the final calls to CSS, JavaScript and image resources.

Contact Us

778 786 2423

1310 Fraser Ave
Port Coquitlam, BC, Canada
V3B 1M4
(10 minutes from Vancouver)

Copyright © 2017 Modus Internet. All rights reserved.