Mason-CM Info   User: guest | Date: 10/22/2017 
OVERVIEW   DOCUMENTATION   MANUAL 
  Doc:  ADMIN
Notes for the Content Management Administrator
===================================================================

-- Content Management is configured through the "conf/mcm*" files,
which basically defines hashes of configuration settings. 
The first step in getting Content Management to to walk
through this hash and set things up for your location. At a minimum,
you'll need to set $mcm->{data}, $mcm->{comp}, the branches, and the
acl for the users.

-- Be sure to read all the comments in 'conf/mcm*'.

-- In addition to simple file locking in the editor, Content
Management allows you to restrict read/write access in certain
directories by user. For example, you may want to limit your editors
to read-only access in component directories, while giving your
programmers full access. Users with read-only access to a directory
are presented with MCM's "read-only" mode, where the interface changes
to omit all write operations.  If a user has no privs at all in a
directory, they get a "no privs" error when they try to navigate into it.

To take full advantage of this feature, you will probably want to
replace the generic user authorization subroutine provided in 
"shared/manipACL.comp" (to grant/deny access to specific users in 
specific subdirectories). 

Example: 
Use a custom user-privs database in Oracle; for your own site you may want 
to examine one of the Apache::Authen* modules out there (AuthenDBI, et al), 
or write an interface to mirror directory privs from the filesystem.

-- When creating new text files there are two templates available. 
Add or change these in "shared/createTemplates.snip". To add a new template
ad a <%DEF *templatename*.tmpl></%DEF> section to this file. 

-- The "index" component, has a section for posting announcements
via MCM's helpScreen component. A sample announcement file
"help/welcome.page" is provided as a template.

-- We use emacs a lot, so MCM has filters for #hidden# or hidden~ files, 
ignoring them in listings, and deleting them automatically on directory 
deletes. See also 'mcmRuntime.conf' ->{dirmask}

-- If you want to run multiple copies of Content Management on different 
virtual servers, make a copy of "conf/mcmRuntime.conf" for each virtual
server, naming each copy mcmRuntime.*server name*.conf. Then, add the
following to the top of the main, shared "conf/mcmRuntime.conf" file:

  my $vhost = $r->server->server_hostname;
  return $m->comp("mcmRuntime.$vhost.conf", 
  		$ARGS, branch => $branch, 
  		path => $path);
  		
-- From the old Mason days there is stil a reload list created when 
set 'use_reload_file => 1' in mcmProject.*.conf. It is stored into 
"data_dir"/etc/reload.lst. When using 'preloads' in the Mason set up,
this list can be opened and passed as an array ref to the new constructor
of the request. Attention, do not use this on too many files, as this
crowds the RAM with components maybe not used so often. 

-- Be aware that you need to configure your Apache virtual host for a 
long timeout if you expect large file uploads. 


=================================================================
04.08.2003 12:12, Christian Hauser, c.hauser@itassistance.ch
 Documentation

   

© 2007 Mason-CM V 1.3, Content Management built on Mason - Headquarter, CPAN