Config module.

/config Allows a full website administrators to manage the CMS instance and the configuration settings.

Settings are stored in configuration files on the webserver. These files use a 'file definition' entry in the config module to determine which file (and optional which part of the file) to edit, and which language to use.

Features include:

List defined files that configure CMS
Add new configuration file definition
Use Edit_Area to edit a configuration file
edit a file definition
delete configuration file history
delete configuration file history and definition
list edit histories

/config illustrates the existing file definitions

click on a filename to edit the file.

choose link 'add definition' to add another file definition.

/config?action=addfile adds a new file definition.

A file definition tells the /config module where the file physically exists on the webserver, what file type (language) to draw the file as, and optionally which section to present. Optional notes for file description, and file test procedure can be made.

If you're only editing a section of the file, fill in the section name start and end fields. The start and end tags will be a unique line in the config file, often as a 'comment'. This 'comment' should not be preceded by tabs, spaces, or other characters.

For example, in an example.css file you may use /* Section 1 */ as the start and end tags. The example.css file may physically be something like:

... .popupdiv a:link, img{border-width:0;} /* End AD Popup*/ /* Section 1 */ .ajaxtickerclass { //class to apply to your scroller(s) if desired
} /* Section 1 */ /* rest of the body statement in uccstyle.css - separated for xStandard editor */ ...

and by specifying the /* Section 1 */ as the start and end tags - only this would show up in the editor.

.ajaxtickerclass { //class to apply to your scroller(s) if desired
}

Sample comments that could be used for start and end tags:

CSS - /* Section 1 */
VB/ASP - ' Section 1 '
HTML - 
JavaScript - // Section 1 //
SQL - -- Section 1 --
XML/XHTML

to edit CMS configuration, visit /config and choose a configuration file you wish to edit.

IF what is displayed does not match the contents of your physical file, create a new .txt file, copy the contents of your existing file into that on the server. Some text files are stored differently then others - and the filereader needs the most basic. This error usually applears when your files were authored externally, like the xStandard vendor.

[Save] the file when you have made your changes and they will be updated into the existing file on the server, and a copy will be made into the history.

Choose the history from the dropdown list at the bottom to review old changes (and optionally save them to reinstate them) You may also delete history if after loading it you decide you do not need it.

Choose File Definition link to update the file definition.

To update the file definition of an existing file visit /config , choose the filename you wish to update, choose the File Definition link.

You may also remove individual histories of the config file, or remove the definition and all of the histories. If you remove the definition and all of the histories, the physical file on the server is unaltered and remains in service.