Skip to content

Correspondence Technologies

Sections
Personal tools
You are here: Home » Software » SfIndex Demo » collective - CMFExample

Package: collective - CMFExample

An example for customizing plone used at OSCOM - Berkley 2002. Probably out-of-date.

a test of SfIndex product

Releases

Release Date Release Name Download
2003-03-06 22:00 CMFExample-0.6 sourceforge
2002-08-06 17:00 CMFExample 0.5 sourceforge

Package README (CVS ver. 1.5)

CMFExample - for use with the Plone implementation of the Content Management
Framework.

You can use the Plone interface as an adminsitrative interface, and still have
a public
skin be autonomous.  Usually you do this with Apache rewriting URLs and
proxying them
into ZServer.  This is a robust approach to Content Managment.  You can front
your
Apaches with SQUID to serves hundreds of requests per second.  This system is
serves
only as an example.  For more information look to the plone website,
http://www.plone.org/
nd you can email the plone-users mailing list,
http://plone.org/development/lists

ZOPE is an amazing system.  We provide you enterprise level functionality.  It
does not come without
a learning curve.  The plone team can help in consulting work.  Plone has an
international
development team stretching from Brazil to Norway with tens of years of
software development experience.
We believe there is no software product, free or 'for cost' that can help you
deploy software faster and
more reliable than Plone, CMF and ZOPE.

REQUIREMENTS:

    * Zope 2.6.0 or above

    * CMFTypes from CVS - http://sf.net/projects/collective

    * CMF1.3 (with Skinnable.py and SkinsContainer.py from HEAD) or above

    * Plone 1.0 or above

    * Apache is optional

INSTALLATION:

    * install a Plone Site

    * inside the Zope Management Interface (/manage) go into your new Plone
    site and create a External Method

    * External Method:

      id: install_examples
      module: CMFExample.Install
      function: install

    * Save it and click Test tab

    * NOTE: it will take awhile to install.  The installation is doing all
    sorts of acrobats.

BUGS:

    * some reason you may have SiteAccess folder may have to create a script in
    portal that says:
      context.emerging.manage_delObjects('bind_emerging_website')

HOW IT WORKS:

    * create a virtual host in apache, follow rewrite rules that you will call
    your 'public website' i.e. emerging.yoursite.com

    * You can read more here http://plone.org/Members/runyaga/presentations/OSC-
    OM/workshop/index_html

Script(Python) that does the skin toggling on VirtualHost traversal:

REQUEST=context.REQUEST
phypath=REQUEST.get('VirtualRootPhysicalPath', ())
if phypath and phypath[-1]=='emerging':
    context.portal_url.getPortalObject().changeSkin('Emerging Website')
# You can read more about this by googling for Site Root or Site Access
# and not that the changeSkin method must be available.  You get this
# by grabbing the latest Skinnable.py or SkinsContainer.py from cvs.zope.org in
CMF/CMFCore
# it will be available with CMF1.4

FOR MORE INFORMATION:

    * http://plone.org/ - plone development

    * http://zope.org/ - zope community site

    * http://zope.com/ - Zope Corporation

    * http://python.org/ - the easiest scripting language on the web

 

Powered by Plone

This site conforms to the following standards: