MidCOM
From OpenPSA Wiki
MidCOM (short for "Midgard Component Framework") is an Open Source Content Management Framework written in PHP. It provides a number of services covering areas like authentication, user notification and revision control for developers to use in their applications which can be written as MidCOM Components.
For content editors, WYSIWYG editors like TinyMCE and jQuery-based Datamanager2 widgets facilitate content editing on the actual website. Many more MidCOM Features are described in a separate article.
Contents |
[edit] Development
MidCOM contains a number of additions to the standard Midgard functionality. For example, the Style Engine expands the functionality offered by Midgard quite a bit (Templating in MidCOM offers an overview of the possibilities). MidCOM URL Methods allow you to embed commands into request URLs. MidCOM provides a Database Abstraction Layer that wraps MgdSchema and makes it available to Component developers.
See also:
[edit] History
MidCOM was originally developed separate from the Midgard core, but was later included in the standard distribution. Before MidCOM 2.0, MidCOM's functionality was stored in a MySQL database, starting from version 2.0, it is stored in the file system. midcom-fs is the designation for current versions, as opposed to midcom-db, which refers to 1.x versions.
The most recent MidCOM release is the 8.09 LTS series, which will be supported until 2013. The OpenPSA framework was forked from MidCOM in November 2010 at at the Midgard developer meeting and is developed independently since then. The new OpenPSA application and the underlying framework start with version number 9.0.
[edit] Installation
Starting with MidCOM 2.6.0, the framework and its components are available as PEAR packages to ease installation and tracking dependencies. The installation can be triggered from Datagard, additional packages can be installed from the command line.
To enable MidCOM for a specific website, one can create a new Host with Midgard Sitewizard or modify the respective Page Elements for an existing Host. If you choose the manual installation, the MidCOM root Topic must be enabled in a Host's Root Page, usually in code-global or code-init. Furthermore, a link to the static directory, which is usually called midcom-static, must be acessible to Apache from the Virtual Host's DocumentRoot.
See also Troubleshooting for typical installation problems
[edit] Configuration
MidCOM site configuration is saved in the Page Element code-init. Many of the config options are also avccessible via the Toolbar. See MidCOM Configuration for an overview of config options.
The components can be configured per Sitegroup in a special Snippetdir called sitegroup-config. To configure a Component, a Subsnippetdir with the name of the component has to be created. Alternatively, global component configuration can be done in Asgard. Configuration on a per-Topic-level can be done in a MidCOM Toolbar. See MidCOM Component Configuration for details.
Unparalleled accuracy, unequivocal clarity, and undenaible importance!
N8BslD <a href="http://ogzijfmovlyu.com/">ogzijfmovlyu</a>
