Cy Think Survey

Cy Think Survey

Surveys, Polls, Questionaires, Quizzes & cetera

Home
Help Index
About Codes
About Maintenance
About Parms
About Users
Code Implementation
Code Maintenance
Control Heirarchy
Documentation Maintenance
Field Add
Function Maintenance
Menu Maintenance
Merge Core Procedure
Merge Client Procedure
Page Add
Page Change
Page Copy
Program Creation
Parameter Maintenance
Ring Maintenance
Site Appearance
Site Maintenance
Site Setup
Site Setup Prep
System Maintenance
Table Add
Table Copy
Text Maintenance
Admin

Programmer's Guide to CMS Programming (1)  

This is the first step in the process of implementing a change to the Cy Think Content Management System (CMS) program code. This step involves changing the JavaScript, PERL and PHP code in the program modules and updating the documentation of the system accordingly. This must be done on a single website for a single client where it can be tested.

Analyze the Change

  1. Determine if database changes are needed. If database and table changes are needed, these are always done first. See Add Table
  2. Consider what program modules need to be changed. Identify the module (or modules) that will need to be changed. Consider the impact if many modules are involved in the change.
  3. Determine and note on the Merge Changes / Log which website is to be the development and test site.

Implement Database Changes

Follow these steps if table changes are required.

  1. Record or indicate the affected table or tables in the Database Change Log.
  2. Make the change or changes. Update the 3-ring binder as needed.
  3. Copy the SQL code to D:/CyThink/coreCMS/sql. This will make things easier later.
  4. New database fields require JshPARM.pm to be changed.
  5. New database tables require JshGUI.pm to be changed.
  6. New table see pp to add a database table
  7. Req New Program See PP to create an App

Implement Program Changes

  1. Copy the module from D:/CyThink/coreCMS to the local site folder, e.g. D:/JSH/site.
  2. Print and use the list of core files from Files.xls as a record sheet.
  3. Record the module names on the Files.xls worksheet.
  4. Make the changes. Be sure to isolate code with the proper use of Parms.
  5. FTP the changes to the remote host and test them.

Promote and Distribute the Change

  1. Use ExamDiff to make sure no inadvertent detrimental changes creep into the code.
  2. Merge the change into the core CMS code. See this link.
    Programmer's Procedure to Update the Core CMS Code

This page describes and contains procedures that a programmer would use to extend the features of the Cy Think CMS. These procedures help maintain the power and flexibility of the CMS system.

Copyright © 2008 Cy Think, Inc.