Entities

    CMS Entities Basics | Overview | Documentation (image)

    CMS entities are:

    • User. User can loggin into system using password and todo allowed actions. CMS access control uses user and assigned to user groups to performs authentification and authorization tasks. User data can be stored in MySQL server data base, SQLite data base file or XML files. User management can be done using CMS administration tool "Users" or XML file edit.
    • Group. Multiple groups can be asigned to users. Authentication and autorization can be performed by user and assigned to user groups. Group data can be stored in MySQL server data base, SQLite data base file or XML files. Group management can be done using CMS administration tool "Groups" or XML file edit.
    • File. HTML, Java Script, CSS, template and other files to be included into page. Usualy files are located in special CMS folders (by default in /cms/files and /cms/images) and can be accessed for editing using CMS "Files" admin pages, CMS "Edit" plugin, WebDav protocol or server operating system tools. Pictures are located in separated folder (by default /cms/images). Files can be uploaded with drag and drop using CMS "Files" admin pages from personal computer folder. Files access control can be controlled by users and groups. File management can be done using CMS administration tool "Files".
    • Template. CMS is using PHP Smarty template engine. Skin dependent page templates are located in skin templates folder. Templates located in files folder (by default /cms/files) can be used too. Different templates can be assigned for different pages. Templates can include other templates. Template main duty - to separate page representation level from programing level. Smarty and CMS variables and plugins can be used in templates. Template management can be done using CMS administration tool "Files", "Setup" and "Pages".
    • Page. Page contains all data to be used for URL representation: title, description, URL, optional metadata, include files, template and other information. Page data can be stored in MySQL server data base, SQLite data base file or XML files. Pages are source for menu tree. Pages access control can be controlled by users and groups. Pages can be published by date and time from and to. Page management can be done using CMS administration tool "Pages" or XML file edit.
    • Menu. Site menu tree. Menu items can be authorized for users and groups, can be hidden (to be shown only in path), accessible for only logged on or only logged of users. Pages are source for menu tree. Menu data can be stored in MySQL server data base, SQLite data base file or XML file. Menu items access control can be controlled by users and groups. Menu items can be published by date and time from and to. Menu management can be done using CMS administration tool "Menu" or XML file edit.
    • Skin. Skin is site reperesentation entity and consists of: template, images, java script and css file collection. Skins by default are located in /cms/skins folder. Skin folder consists of css, images, js and templates folders. Actual site skin is defined in site configuration file and enforced using .htaccess file RewriteRule's. Actual skin URL paths begins as /skin/images, /skin/js, /skin/css and /skin/templates. Skin management can be done using CMS administration tool "Setup".
    • Plugin. Plugin is software package plugged into CMS. Plugins by default are located in /cms/srv/plugins folder. Plugin local data by default is located in /cms/data/plugins/pluginid folder. Plugin has metadata about it: id, name, owner, plugin software folder path, plugin data folder path. etc. Plugin package must have standard plugin folder structure. Plugin delegate to CMS: jQuery plugins, CSS files, templates, templates plugins, PHP classes. Plugin may have its own manage tools located in plugin subsite.

      All KUSoftas CMS plugins are open source software and released under MIT license.

    Vulnerability Scanner