<?xml version="1.0" encoding="utf-8" ?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns="http://purl.org/rss/1.0/">




    



<channel rdf:about="http://plone.org/search_rss">
  <title>Plone CMS: Open Source Content Management</title>
  <link>http://plone.org</link>

  <description>
    
            These are the search results for the query, showing results 1 to 15.
        
  </description>

  

  

  <image rdf:resource="http://plone.org/logo.png"/>

  <items>
    <rdf:Seq>
      
        <rdf:li rdf:resource="http://plone.org/products/collective.js.charcount"/>
      
      
        <rdf:li rdf:resource="http://plone.org/products/dexterity.membrane"/>
      
      
        <rdf:li rdf:resource="http://plone.org/products/collective.rtvideo.mediacore"/>
      
      
        <rdf:li rdf:resource="http://plone.org/products/Products.ZOpenArchives"/>
      
      
        <rdf:li rdf:resource="http://plone.org/products/collective.contentrules.subscription"/>
      
      
        <rdf:li rdf:resource="http://plone.org/support/sites/asap-garage-doors"/>
      
      
        <rdf:li rdf:resource="http://plone.org/support/sites/central-region-junior-soccer-association"/>
      
      
        <rdf:li rdf:resource="http://plone.org/support/sites/kingborough-lions-united-football-club"/>
      
      
        <rdf:li rdf:resource="http://plone.org/products/collective.fontawesome"/>
      
      
        <rdf:li rdf:resource="http://plone.org/support/sites/forum-verejne-zakazky-kvalitne"/>
      
      
        <rdf:li rdf:resource="http://plone.org/support/providers/mware-cz"/>
      
      
        <rdf:li rdf:resource="http://plone.org/support/sites/loucen-concours-delegance"/>
      
      
        <rdf:li rdf:resource="http://plone.org/support/sites/advokatni-kancelar-dana-pergl-partneri"/>
      
      
        <rdf:li rdf:resource="http://plone.org/support/providers/computing-insights"/>
      
      
        <rdf:li rdf:resource="http://plone.org/support/sites/riskcenter.com"/>
      
    </rdf:Seq>
  </items>

</channel>


  <item rdf:about="http://plone.org/products/collective.js.charcount">
    <title>collective.js.charcount</title>
    <link>http://plone.org/products/collective.js.charcount</link>
    <description>jQuery plugin dynamic character count
                     for textareas and input fields</description>
    <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<h2 class="title">collective.js.charcount</h2>
<div class="contents topic" id="table-of-contents">
<p class="topic-title first">Table of Contents</p>
<ul class="simple">
<li><a class="reference internal" href="#overview" id="id1">Overview</a></li>
<li><a class="reference internal" href="#about-charcount" id="id2">About charCount</a></li>
<li><a class="reference internal" href="#plugin-options-and-default-values" id="id3">Plugin Options (and default values)</a><ul>
<li><a class="reference internal" href="#limit-140" id="id4">limit: 140</a></li>
<li><a class="reference internal" href="#warning-25" id="id5">warning: 25</a></li>
<li><a class="reference internal" href="#counterelement-span" id="id6">counterElement: 'span'</a></li>
<li><a class="reference internal" href="#css-counter" id="id7">css: 'counter'</a></li>
<li><a class="reference internal" href="#csswarning-warning" id="id8">cssWarning: 'warning'</a></li>
<li><a class="reference internal" href="#cssexceeded-exceeded" id="id9">cssExceeded: 'exceeded'</a></li>
<li><a class="reference internal" href="#countertext" id="id10">counterText: ''</a></li>
</ul>
</li>
<li><a class="reference internal" href="#how-to-install" id="id11">How to install</a><ul>
<li><a class="reference internal" href="#mostly-harmless" id="id12">Mostly Harmless</a></li>
</ul>
</li>
<li><a class="reference internal" href="#installation" id="id13">Installation</a><ul>
<li><a class="reference internal" href="#contributors" id="id14">Contributors</a></li>
</ul>
</li>
<li><a class="reference internal" href="#changelog" id="id15">Changelog</a><ul>
<li><a class="reference internal" href="#unreleased" id="id16">1.0 (unreleased)</a></li>
</ul>
</li>
</ul>
</div>
<div class="section" id="overview">
<h3><a class="toc-backref" href="#id1">Overview</a></h3>
<p>jQuery plugin Simplest Twitterlike dynamic character count for textareas and
input fields.</p>
</div>
<div class="section" id="about-charcount">
<h3><a class="toc-backref" href="#id2">About charCount</a></h3>
<p>The first thing that this plugin do is create a sibling element (it adds is
immediately AFTER the form element), the &quot;counter&quot;, where the remaining
character info is stored. On each key up event or text field value change the
counting function is triggered and the contents of this &quot;counter&quot; element is
changed accordingly. If the remaining character count reaches the &quot;warning&quot;
zone (gets close to zero) the CSS class is added. We use this class to change
the color of the character count info. If the count reaches zero and goes beyond
it another class is added so we can use another style for exceeding the limit.</p>
<p>Just so you can find your way around it, this is the code that the plugin generates
by default:</p>
<pre class="literal-block">
&lt;span class=&quot;counter&quot;&gt;140&lt;/span&gt;
</pre>
</div>
<div class="section" id="plugin-options-and-default-values">
<h3><a class="toc-backref" href="#id3">Plugin Options (and default values)</a></h3>
<div class="section" id="limit-140">
<h4><a class="toc-backref" href="#id4">limit: 140</a></h4>
<p>The character limit you wish to set for your text area or input field. It must be
a number.</p>
</div>
<div class="section" id="warning-25">
<h4><a class="toc-backref" href="#id5">warning: 25</a></h4>
<p>When remaining characters reach the number set with this option the &quot;warning&quot; css
class name will be applied to the counter element.</p>
</div>
<div class="section" id="counterelement-span">
<h4><a class="toc-backref" href="#id6">counterElement: 'span'</a></h4>
<p>The type of element you wish to choose as your &quot;counter&quot; element. By default it is
a SPAN element, but you can use paragraphs, divs, strongs, ems…</p>
</div>
<div class="section" id="css-counter">
<h4><a class="toc-backref" href="#id7">css: 'counter'</a></h4>
<p>Class name added to the counter element. Use this class name as a css selector to
describe element’s appearance.</p>
</div>
<div class="section" id="csswarning-warning">
<h4><a class="toc-backref" href="#id8">cssWarning: 'warning'</a></h4>
<p>Class name added to the counter element once the character count reaches the &quot;warning&quot;
number.</p>
</div>
<div class="section" id="cssexceeded-exceeded">
<h4><a class="toc-backref" href="#id9">cssExceeded: 'exceeded'</a></h4>
<p>Class name added to the counter element once the character count reaches zero.</p>
</div>
<div class="section" id="countertext">
<h4><a class="toc-backref" href="#id10">counterText: ''</a></h4>
<p>If you wish to add some text before the remaining character number, you can do so by
using this option. It is empty by default.</p>
<p>Here’s what default usage code looks like:</p>
<pre class="literal-block">
$(&quot;#message1&quot;).charCount();
</pre>
<p>…and this is the plugin usage with some customized options:</p>
<pre class="literal-block">
$(&quot;#message2&quot;).charCount({
    allowed: 50,
    warning: 20,
    counterText: 'Characters left: '
});
</pre>
<p>Also take a look at the CSS I used for my demos:</p>
<pre class="literal-block">
form .counter{
    position:absolute;
    right:0;
    top:0;
    font-size:20px;
    font-weight:bold;
    color:#ccc;
}
form .warning{color:#600;}
form .exceeded{color:#e00;}
</pre>
</div>
</div>
<div class="section" id="how-to-install">
<h3><a class="toc-backref" href="#id11">How to install</a></h3>
<p>This addon can be installed as any other Plone addon. Please follow official
<a class="reference external" href="http://plone.org/documentation/kb/installing-add-ons-quick-how-to">documentation</a>.</p>
<p>After installing the package on your portal you can access the demo in:
<a class="reference external" href="http://youportal.com/++resource++collective.js.charcount.demo.html">http://youportal.com/++resource++collective.js.charcount.demo.html</a></p>
<p>Have an idea? Found a bug? Let us know by <a class="reference external" href="https://github.com/collective/collective.js.charcount/issues">opening a support ticket</a>.</p>
<div class="section" id="mostly-harmless">
<h4><a class="toc-backref" href="#id12">Mostly Harmless</a></h4>
<a class="reference external image-reference" href="http://travis-ci.org/collective/collective.js.charcount"><img alt="https://secure.travis-ci.org/collective/collective.js.charcount.png" src="https://secure.travis-ci.org/collective/collective.js.charcount.png" /></a>
</div>
</div>
<div class="section" id="installation">
<h3><a class="toc-backref" href="#id13">Installation</a></h3>
<blockquote>
<ul>
<li><p class="first">When you're reading this you have probably already run
<tt class="docutils literal">easy_install collective.js.charcount</tt>. Find out how to install setuptools
(and EasyInstall) here:
<a class="reference external" href="http://peak.telecommunity.com/DevCenter/EasyInstall">http://peak.telecommunity.com/DevCenter/EasyInstall</a></p>
</li>
<li><p class="first">Get <a class="reference external" href="http://plone.org/products/pythonproducts">pythonproducts</a> and install it via:</p>
<pre class="literal-block">
python setup.py install --home /path/to/instance
</pre>
<p>into your Zope instance.</p>
</li>
<li><p class="first">Create a file called <tt class="docutils literal"><span class="pre">collective.js.charcount-configure.zcml</span></tt> in the
<tt class="docutils literal"><span class="pre">/path/to/instance/etc/package-includes</span></tt> directory.  The file
should only contain this:</p>
<pre class="literal-block">
&lt;include package=&quot;collective.js.charcount&quot; /&gt;
</pre>
</li>
</ul>
</blockquote>
<p>Alternatively, if you are using zc.buildout and the plone.recipe.zope2instance
recipe to manage your project, you can do this:</p>
<blockquote>
<ul>
<li><p class="first">Add <tt class="docutils literal">collective.js.charcount</tt> to the list of eggs to install, e.g.:</p>
<blockquote>
<p>[buildout]
...
eggs =</p>
<div class="system-message">
<p class="system-message-title">System Message: ERROR/3 (<tt class="docutils">&lt;string&gt;</tt>, line 151)</p>
<p>Unexpected indentation.</p>
</div>
<blockquote>
<p>...
collective.js.charcount</p>
</blockquote>
</blockquote>
</li>
</ul>
<blockquote>
<ul>
<li><p class="first">Tell the plone.recipe.zope2instance recipe to install a ZCML slug:</p>
<p>[instance]
recipe = plone.recipe.zope2instance
...
zcml =</p>
<div class="system-message">
<p class="system-message-title">System Message: ERROR/3 (<tt class="docutils">&lt;string&gt;</tt>, line 160)</p>
<p>Unexpected indentation.</p>
</div>
<blockquote>
<p>collective.js.charcount</p>
</blockquote>
</li>
<li><p class="first">Re-run buildout, e.g. with:</p>
<p>$ ./bin/buildout</p>
</li>
</ul>
</blockquote>
</blockquote>
<p>You can skip the ZCML slug if you are going to explicitly include the package
from another package's configure.zcml file.</p>
<p>After updating the configuration you need to run ''bin/buildout'', which will
take care of updating your system.</p>
<p>Go to the 'Site Setup' page in a Plone site and click on the 'Add-ons' link.</p>
<p>Check the box next to <tt class="docutils literal">collective.js.charcount</tt> and click the 'Activate' button.</p>
<p>Note: You may have to empty your browser cache and save your resource
registries in order to see the effects of the package installation.</p>
<div class="section" id="contributors">
<h4><a class="toc-backref" href="#id14">Contributors</a></h4>
<ul class="simple">
<li>Cleber J. Santos</li>
</ul>
</div>
</div>
<div class="section" id="changelog">
<h3><a class="toc-backref" href="#id15">Changelog</a></h3>
<div class="section" id="unreleased">
<h4><a class="toc-backref" href="#id16">1.0 (unreleased)</a></h4>
<ul class="simple">
<li>Initial release</li>
</ul>
</div>
</div>
]]></content:encoded>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Cleber J Santos</dc:creator>
    <dc:rights></dc:rights>
    <dc:date>2013-05-18T17:27:10Z</dc:date>
    <dc:type>Software Project</dc:type>
  </item>


  <item rdf:about="http://plone.org/products/dexterity.membrane">
    <title>dexterity.membrane</title>
    <link>http://plone.org/products/dexterity.membrane</link>
    <description>Dexterity content and behaviors to integrate with membrane.</description>
    <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<div class="section" id="introduction">
<h3>Introduction</h3>
<p>This is very much alpha code.  But it seems to work fine in a client
project.  Or at least the client code where this package got copied from
seems to work fine.  It could be that too much client code has been
left behind here or removed, but it seems to be okay.</p>
<p>The code is inspired by parts of the <tt class="docutils literal">fsd.membrane</tt> package (being
developed by the WebLion group) and the membrane documentation at
<a class="reference external" href="http://packages.python.org/Products.membrane/content.html">http://packages.python.org/Products.membrane/content.html</a></p>
<div class="section" id="compatibility">
<h4>Compatibility</h4>
<p>This package has been developed for Plone 4.1.  In fact it will only
work on that version (or higher) as we require uuid support.</p>
<p>We depend on Products.membrane 2.0.2 or higher as that contains a fix
to make sure members that are deleted are also removed from the
membrane_tool catalog.</p>
</div>
<div class="section" id="user-id">
<h4>User id</h4>
<p>As user id we use the uuid that is generated for the content item.
This only works on Plone 4.1 and higher.  See the definition of
<tt class="docutils literal">getUserId</tt> in the <tt class="docutils literal">membraneuser.py</tt> behavior.</p>
<p>If you define your own member content type, you should enable the
<tt class="docutils literal">plone.app.referenceablebehavior.referenceable.IReferenceable</tt>
behavior on it as that gives uuid support.  This also means members
can be referenced from Archetypes content.</p>
</div>
<div class="section" id="email-as-login-name">
<h4>Email as login name</h4>
<p>This package contains a member content type that has an email field.
This is used as login name by the behavior.  See <tt class="docutils literal">getUserName</tt>.
Other implementations are possible, so we do not force you to use the
email address as the login name in your site.  But setting the
use_email_as_login property to True is probably a good idea.  The only
effect this has as far as this package is concerned, is that some text
in login forms is changed: you see 'email address' as label instead of
'login name', mostly.  To enable this, you can put this in
<tt class="docutils literal">propertiestool.xml</tt>, possibly in a custom package for your
project:</p>
<pre class="literal-block">
&lt;?xml version=&quot;1.0&quot;?&gt;
&lt;object name=&quot;portal_properties&quot; meta_type=&quot;Plone Properties Tool&quot;&gt;
  &lt;object name=&quot;site_properties&quot; meta_type=&quot;Plone Property Sheet&quot;&gt;
    &lt;property name=&quot;use_email_as_login&quot; type=&quot;boolean&quot;&gt;True&lt;/property&gt;
  &lt;/object&gt;
&lt;/object&gt;
</pre>
</div>
<div class="section" id="member-content-type">
<h4>Member content type</h4>
<p>This package defines a member content type, but this may be considered
an example; feel free to create a different type and only use the
behaviors or create your own adaptations of them.</p>
</div>
<div class="section" id="behaviors">
<h4>Behaviors</h4>
<ul class="simple">
<li><tt class="docutils literal">dexterity.membrane.behavior.membraneuser.IMembraneUser</tt>: this
makes the content behave as a membrane user, defining a way to get
the user id (<tt class="docutils literal">getUserId</tt>) and login name (<tt class="docutils literal">getUserName</tt>).</li>
<li><tt class="docutils literal">dexterity.membrane.behavior.membraneuser.IProvidePasswords</tt>:
adds a password and confirmation field to your dexterity content.
This is used during authentication.</li>
<li><tt class="docutils literal">dexterity.membrane.behavior.membranegroup.IMembraneGroup</tt>: this
makes the content behave as a membrane group, defining a way to get
the group id (<tt class="docutils literal">getGroupId</tt>) and group name (<tt class="docutils literal">getGroupName</tt>).</li>
</ul>
</div>
<div class="section" id="membrane-implementation">
<h4>Membrane implementation</h4>
<ul class="simple">
<li><tt class="docutils literal">Products.membrane.interfaces.IMembraneUserAuth</tt>: we implement
authentication using the email field and the password field.</li>
<li><tt class="docutils literal">Products.membrane.interfaces import IMembraneUserProperties</tt>: we
provide a read-only mapping from the first and last name fields of
our own <tt class="docutils literal">IMember</tt> schema to the fullname user property.  We have a
read-write mapping for the email, home_page/homepage and
description/bio properties/fields for <tt class="docutils literal">IMember</tt>.</li>
</ul>
</div>
<div class="section" id="local-roles">
<h4>Local roles</h4>
<p>This package defines a local role provider that makes sure a logged in
user gets the local Reader, Editor and Creator roles on the membrane
object that belongs to that user.</p>
</div>
<div class="section" id="workflow">
<h4>Workflow</h4>
<p>We define a simple workflow with pending/approved states.  A user can
only login when in the approved state.</p>
</div>
</div>
<div class="section" id="changelog">
<h3>Changelog</h3>
<div class="section" id="id1">
<h4>0.3 (2013-05-15)</h4>
<ul class="simple">
<li>Fix installation problems when OS does not support symbolic links. Renamed
<tt class="docutils literal">README.txt</tt> to <tt class="docutils literal">README.rst</tt> and updated <tt class="docutils literal">setup.py</tt> to point to that
file. This fixes #5.
[saily]</li>
<li>Fix getattr in getPropertiesForUser to have a default value.
[datakurre]</li>
</ul>
</div>
<div class="section" id="id2">
<h4>0.2 (2013-02-19)</h4>
<ul class="simple">
<li>Keep constistent with plone's email login #12187, so don't lowercase email
addresses.
[saily]</li>
<li>Add basic membrane group behavior
[saily]</li>
</ul>
</div>
<div class="section" id="id3">
<h4>0.1 (2012-09-20)</h4>
<ul class="simple">
<li>Initial alpha release</li>
</ul>
</div>
</div>
]]></content:encoded>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Maurits van Rees</dc:creator>
    <dc:rights></dc:rights>
    <dc:date>2013-05-15T12:31:20Z</dc:date>
    <dc:type>Software Project</dc:type>
  </item>


  <item rdf:about="http://plone.org/products/collective.rtvideo.mediacore">
    <title>collective.rtvideo.mediacore</title>
    <link>http://plone.org/products/collective.rtvideo.mediacore</link>
    <description>RedTurtle Video integration for MediaCore</description>
    <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<h2 class="title">Introduction</h2>
<p>This is an add-on for <a class="reference external" href="https://pypi.python.org/pypi/redturtle.video">RedTurtle Video</a> product for Plone. Additional documentation can be found in the main product's page.</p>
<p>Add this to your Plone installation for beeing able to use <a class="reference external" href="http://mediacore.com/">MediaCore</a> video link as valid URLs for &quot;Video link&quot; content type.</p>
<p>In order to serve content from Mediacore you need to configure an adapter and specify the domain name.
Is possible to add an adapter to your application in many way:</p>
<blockquote>
<ul class="simple">
<li>directly to the buildout section on a .cfg file (example below):</li>
<li>within a configure.zcml in collective.rtvideo.mediacore</li>
<li>within an other package which implements redturtle.video.interfaces.IRTRemoteVideo</li>
</ul>
</blockquote>
<pre class="literal-block">
[instance]
...
eggs =
    collective.rtvideo.mediacore
    ...

zcml-additional =
    &lt;configure xmlns=&quot;http://namespaces.zope.org/zope&quot;&gt;
        &lt;adapter for = &quot;redturtle.video.interfaces.IRTRemoteVideo zope.publisher.interfaces.browser.IHTTPRequest&quot;
            provides = &quot;collective.rtvideo.mediacore.videoembedcode.IMediaCoreEmbedCode&quot;
            factory = &quot;collective.rtvideo.mediacore.videoembedcode.JWPlayerEmbedCode&quot;
            name= &quot;your.domain&quot;/&gt;
    &lt;/configure&gt;
</pre>
<!--  -->
<div class="section" id="note">
<h3>Note</h3>
<p>This plugin alone is not enougth.
Mediacore must provides a view to serve some information about media as JSON.
See <a class="reference external" href="https://pypi.python.org/pypi/mediacore.mediainfo/">mediacore.mediainfo</a> package for more details.</p>
</div>
]]></content:encoded>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Nicola Senno</dc:creator>
    <dc:rights></dc:rights>
    <dc:date>2013-05-15T11:08:44Z</dc:date>
    <dc:type>Software Project</dc:type>
  </item>


  <item rdf:about="http://plone.org/products/Products.ZOpenArchives">
    <title>Products.ZOpenArchives</title>
    <link>http://plone.org/products/Products.ZOpenArchives</link>
    <description>OAI connector for eXist data in Zope and Plone.</description>
    <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<div class="section" id="products-zopenarchives-installation">
<h3>Products.ZOpenArchives Installation</h3>
<p>To install Products.ZOpenArchives into the global Python environment (or a workingenv),
using a traditional Zope 2 instance, you can do this:</p>
<ul>
<li><p class="first">When you're reading this you have probably already run
<tt class="docutils literal">easy_install Products.ZOpenArchives</tt>. Find out how to install setuptools
(and EasyInstall) here:
<a class="reference external" href="http://peak.telecommunity.com/DevCenter/EasyInstall">http://peak.telecommunity.com/DevCenter/EasyInstall</a></p>
</li>
<li><p class="first">If you are using Zope 2.9 (not 2.10), get <a class="reference external" href="http://plone.org/products/pythonproducts">pythonproducts</a> and install it
via:</p>
<pre class="literal-block">
python setup.py install --home /path/to/instance
</pre>
</li>
</ul>
<p>into your Zope instance.</p>
<ul>
<li><p class="first">Create a file called <tt class="docutils literal"><span class="pre">Products.ZOpenArchives-configure.zcml</span></tt> in the
<tt class="docutils literal"><span class="pre">/path/to/instance/etc/package-includes</span></tt> directory.  The file
should only contain this:</p>
<pre class="literal-block">
&lt;include package=&quot;Products.ZOpenArchives&quot; /&gt;
</pre>
</li>
</ul>
<p>Alternatively, if you are using zc.buildout and the plone.recipe.zope2instance
recipe to manage your project, you can do this:</p>
<ul>
<li><p class="first">Add <tt class="docutils literal">Products.ZOpenArchives</tt> to the list of eggs to install, e.g.:</p>
<blockquote>
<p>[buildout]
...
eggs =</p>
<div class="system-message">
<p class="system-message-title">System Message: ERROR/3 (<tt class="docutils">&lt;string&gt;</tt>, line 36)</p>
<p>Unexpected indentation.</p>
</div>
<blockquote>
<p>...
Products.ZOpenArchives</p>
</blockquote>
</blockquote>
</li>
<li><p class="first">Tell the plone.recipe.zope2instance recipe to install a ZCML slug:</p>
<blockquote>
<p>[instance]
recipe = plone.recipe.zope2instance
...
zcml =</p>
<div class="system-message">
<p class="system-message-title">System Message: ERROR/3 (<tt class="docutils">&lt;string&gt;</tt>, line 45)</p>
<p>Unexpected indentation.</p>
</div>
<blockquote>
<p>Products.ZOpenArchives</p>
</blockquote>
</blockquote>
</li>
<li><p class="first">Re-run buildout, e.g. with:</p>
<blockquote>
<p>$ ./bin/buildout</p>
</blockquote>
</li>
</ul>
<p>You can skip the ZCML slug if you are going to explicitly include the package
from another package's configure.zcml file.</p>
<p>Because its top level Python namespace package is called <tt class="docutils literal">Products</tt>, this
package can also be installed in Zope 2 as an old style <strong>Zope 2 Product</strong>.</p>
<p>For that, move (or symlink) the <tt class="docutils literal">ZOpenArchives</tt> folder of this project
(<tt class="docutils literal">Products.ZOpenArchives/Products/ZOpenArchives</tt>) into the <tt class="docutils literal">Products</tt> directory of
the Zope instance it has to be installed for, and restart the server.</p>
<p>You can also skip the ZCML slug if you install this package the <strong>Zope 2
Product</strong> way.</p>
</div>
<div class="section" id="zmi-installation">
<h3>ZMI Installation</h3>
<p>** Important !!! :
This install only talk about ZOpenArchives configured with an eXist storage.
I let constructors of old catalog storage but it's strongly recommanded to not use it.</p>
<dl class="docutils">
<dt>Object you have to play with are:</dt>
<dd><ul class="first last simple">
<li>Exist Open Archive Repository</li>
<li>Exist Open Archive Aggregator (and Exist Open Archive Set/NameSpace in it).</li>
</ul>
</dd>
</dl>
<p>** Requiered products :</p>
<blockquote>
<blockquote>
Xron - deprecated - Prefer use a crontab call to update Aggregator
PyXML 0.8.x or higher (0.8.3 recommended and tested)</blockquote>
<ul>
<li><dl class="first docutils">
<dt>eXist DB features:</dt>
<dd><p class="first last">exist_zope DB adapter to use eXsitDB repository features (recommanded in this version and include in the package)</p>
</dd>
</dl>
</li>
</ul>
</blockquote>
<p>** Compatibility:</p>
<blockquote>
Tested on Zope 2.11 but i think it's work from Zope 2.6</blockquote>
<p>** Installation:</p>
<blockquote>
<blockquote>
<p>Just untar archive into your zope product directory</p>
<p>and restart zope</p>
<p>You can add two types of object inside your ZMI:
- Exist Open Archive Repository:</p>
<div class="system-message">
<p class="system-message-title">System Message: ERROR/3 (<tt class="docutils">&lt;string&gt;</tt>, line 99)</p>
Unexpected indentation.</div>
<blockquote>
<ul>
<li><p class="first">Add an &quot;Exist Open Archive Repository&quot; object from the &quot;add menu&quot;. Fill the exist database adapter ID and others fields.</p>
</li>
<li><p class="first">If needed change values inside &quot;Preferences&quot; and &quot;Server info&quot; panels.</p>
</li>
<li><dl class="first docutils">
<dt>You can manage NameSpaces supported by the repository</dt>
<dd><p class="first last">--&gt; Go inside the &quot;NameSpaces folder and add if needed an &quot;Exist Open Archive Namespace&quot;.
By default, DC, LOM and CDM namespace are added.</p>
</dd>
</dl>
</li>
<li><dl class="first docutils">
<dt>You can manage repository sets</dt>
<dd><p class="first last">--&gt; Go inside the &quot;setsStorage&quot; folder and add &quot;Exist Open Archive Set&quot;
If you want to define sets, i recommand you to read some documentation from the OAI spec (openarchives.org) to define them in the right way</p>
</dd>
</dl>
</li>
</ul>
<p>You now have a repository correctly setted, envoy !</p>
</blockquote>
</blockquote>
<ul>
<li><dl class="first docutils">
<dt>Exist Open Archive Aggregator:</dt>
<dd><p class="first">It's exactly the same than a repository see above but with the possibility to add Harvester in it.
There's two types of harvester:</p>
<div class="system-message">
<p class="system-message-title">System Message: ERROR/3 (<tt class="docutils">&lt;string&gt;</tt>, line 113)</p>
<p>Unexpected indentation.</p>
</div>
<blockquote>
<ul class="simple">
<li>Exist Open Archive Arvester : connect to a remote site to harvest it.</li>
<li>ZCatalog Harvester 4 eXist: Harvest a local catalog (DC format) to give an OAI view to your zope site.</li>
</ul>
</blockquote>
<p class="last">Enjoy !</p>
</dd>
</dl>
</li>
</ul>
</blockquote>
<dl class="docutils">
<dt>** Updates:</dt>
<dd>Important: If you update to v1.5.3, you need to reconfigure exist namespace inside each namespace object</dd>
</dl>
<p>** OAI registry :</p>
<blockquote>
<p><a class="reference external" href="http://gita.grainger.uiuc.edu/registry/ListAllRepos.asp">http://gita.grainger.uiuc.edu/registry/ListAllRepos.asp</a></p>
<p><a class="reference external" href="http://www.openarchives.org/Register/BrowseSites">http://www.openarchives.org/Register/BrowseSites</a></p>
</blockquote>
</div>
]]></content:encoded>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Encolpe Degoute</dc:creator>
    <dc:rights></dc:rights>
    <dc:date>2013-05-14T22:20:00Z</dc:date>
    <dc:type>Software Project</dc:type>
  </item>


  <item rdf:about="http://plone.org/products/collective.contentrules.subscription">
    <title>collective.contentrules.subscription</title>
    <link>http://plone.org/products/collective.contentrules.subscription</link>
    <description>A Plone content rule for send e-mail to addresses taken from a subscription list</description>
    <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>This product will add to Plone a new content rule, similar to the default &quot;Send an email&quot; ones, but email recipients are taken from a list of addresses that are subscribed for that rule.</p>
<div class="section" id="use-case">
<h3><a class="toc-backref" href="#id2">Use-case</a></h3>
<p>We want to notify about some updated of the site, and we want to allows users to subscribe or not to these notifications automatically.</p>
<p>We can do this with a contentrule registered for some object creation, and use our new action to send emails.</p>
<div class="contents topic" id="contents">
<p class="topic-title first">Contents</p>
<ul class="simple">
<li><a class="reference internal" href="#use-case" id="id2">Use-case</a></li>
<li><a class="reference internal" href="#setting-up-the-rule" id="id3">Setting up the rule</a></li>
<li><a class="reference internal" href="#rule-subscription" id="id4">Rule subscription</a></li>
<li><a class="reference internal" href="#subscriptions-overwiew" id="id5">Subscriptions overwiew</a></li>
<li><a class="reference internal" href="#to-do" id="id6">To-do</a></li>
<li><a class="reference internal" href="#requirements" id="id7">Requirements</a></li>
<li><a class="reference internal" href="#authors" id="id8">Authors</a></li>
<li><a class="reference internal" href="#changelog" id="id9">Changelog</a><ul>
<li><a class="reference internal" href="#id1" id="id10">0.1.0 (2013-05-10)</a></li>
</ul>
</li>
</ul>
</div>
</div>
<div class="section" id="setting-up-the-rule">
<h3><a class="toc-backref" href="#id3">Setting up the rule</a></h3>
<p>This product provides a new rule action to connect with base Plone rules. When you create a new action, you need to fill some fields:</p>
<dl class="docutils">
<dt><tt class="docutils literal">Subject</tt></dt>
<dd>The e-mail subject. You can place inside this text some markers.</dd>
<dt><tt class="docutils literal">Sender email</tt></dt>
<dd>The sender of the e-mail. If empty, will be automatically used the one set in portal mail settings.</dd>
<dt><tt class="docutils literal">Message</tt></dt>
<dd><p class="first">The body text of the e-mail that will be sent. The text is the same for all section where
the rule is activated on.</p>
<p class="last">You can place inside this text some markers.</p>
</dd>
</dl>
<p>The list of markes is shown at the bottom of action's edit form.</p>
</div>
<div class="section" id="rule-subscription">
<h3><a class="toc-backref" href="#id4">Rule subscription</a></h3>
<p>As we said previously, site managers can create some rules, and users (also anonymous users) can choose which rules subscribes to.</p>
<p>To do this, there is a simple form created with z3c.form that shows all available rules with our custom action.</p>
<p>The form is available at &quot;<em>http://site_url/&#64;&#64;notify-subscribe</em>&quot;</p>
<img alt="http://blog.redturtle.it/pypi-images/collective.contentrules.subscription/subscribe_rules.png/" src="http://blog.redturtle.it/pypi-images/collective.contentrules.subscription/subscribe_rules.png/" />
<p>If the user is authenticated and have an email address, email field is automatically filled.</p>
<p>There is also an anti-spam check made with <a class="reference external" href="https://pypi.python.org/pypi/collective.z3cform.norobots">collective.z3cform.norobots</a>.</p>
</div>
<div class="section" id="subscriptions-overwiew">
<h3><a class="toc-backref" href="#id5">Subscriptions overwiew</a></h3>
<p>There is also an overview controlpanel for site administrators that shows all rule subscriptions and allows to remove some addresses.</p>
<p>This view is available from Plone controlpanel or at &quot;<em>http://site_url/&#64;&#64;contentrules-subscription-controlpanel</em>&quot;</p>
<img alt="http://blog.redturtle.it/pypi-images/collective.contentrules.subscription/rules_controlpanel.png" src="http://blog.redturtle.it/pypi-images/collective.contentrules.subscription/rules_controlpanel.png" />
</div>
<div class="section" id="to-do">
<h3><a class="toc-backref" href="#id6">To-do</a></h3>
<ul class="simple">
<li>Allow users to unsubscribe</li>
<li>Improve subscription security using some confirm machinery</li>
</ul>
</div>
<div class="section" id="requirements">
<h3><a class="toc-backref" href="#id7">Requirements</a></h3>
<p>This product has been tested on:</p>
<ul class="simple">
<li>Plone 4.0</li>
<li>Plone 4.1</li>
<li>Plone 4.2</li>
<li>Plone 4.3</li>
</ul>
</div>
<div class="section" id="authors">
<h3><a class="toc-backref" href="#id8">Authors</a></h3>
<p>This product was developed by RedTurtle Technology team.</p>
<a class="reference external image-reference" href="http://www.redturtle.it/"><img alt="RedTurtle Technology Site" src="http://www.redturtle.it/redturtle_banner.png" /></a>
</div>
<div class="section" id="changelog">
<h3><a class="toc-backref" href="#id9">Changelog</a></h3>
<div class="section" id="id1">
<h4><a class="toc-backref" href="#id10">0.1.0 (2013-05-10)</a></h4>
<ul class="simple">
<li>Initial release [cekk]</li>
</ul>
</div>
</div>
]]></content:encoded>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Andrea Cecchi</dc:creator>
    <dc:rights></dc:rights>
    <dc:date>2013-05-10T08:31:39Z</dc:date>
    <dc:type>Software Project</dc:type>
  </item>


  <item rdf:about="http://plone.org/support/sites/asap-garage-doors">
    <title>ASAP Garage Doors</title>
    <link>http://plone.org/support/sites/asap-garage-doors</link>
    <description>ASAP Garage Doors is a West Australian family owned business involved in all aspects of garage door sales, repairs and maintenance. Having been in the garage door industry for over 18 years we have built a reputation for quality, value for money and good old fashion service. Being a family business these are values we strive for and constantly look to improve.</description>
    
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Simon Edwards</dc:creator>
    <dc:rights></dc:rights>
    <dc:date>2013-05-07T13:44:25Z</dc:date>
    <dc:type>Site using Plone</dc:type>
  </item>


  <item rdf:about="http://plone.org/support/sites/central-region-junior-soccer-association">
    <title>Central Region Junior Soccer Association</title>
    <link>http://plone.org/support/sites/central-region-junior-soccer-association</link>
    <description>Plone site for southern soccer association in Tasmania, Australia.</description>
    
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Simon Edwards</dc:creator>
    <dc:rights></dc:rights>
    <dc:date>2013-05-07T13:40:00Z</dc:date>
    <dc:type>Site using Plone</dc:type>
  </item>


  <item rdf:about="http://plone.org/support/sites/kingborough-lions-united-football-club">
    <title>Kingborough Lions United Football Club</title>
    <link>http://plone.org/support/sites/kingborough-lions-united-football-club</link>
    <description>Plone site for the non-profit sporting club KLUFC.  Utilising several Plone plugins and Diazo theming.</description>
    
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Simon Edwards</dc:creator>
    <dc:rights></dc:rights>
    <dc:date>2013-05-07T13:35:00Z</dc:date>
    <dc:type>Site using Plone</dc:type>
  </item>


  <item rdf:about="http://plone.org/products/collective.fontawesome">
    <title>collective.fontawesome</title>
    <link>http://plone.org/products/collective.fontawesome</link>
    <description>Font Awesome for Plone</description>
    <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<div class="section" id="introduction">
<h3>Introduction</h3>
<p>This addon register fontawesome into Plone CSS registry.</p>
<p>version of font awesome: 3.1.1</p>
</div>
<div class="section" id="license">
<h3>License</h3>
<ul class="simple">
<li>The Font Awesome font is licensed under the SIL Open Font License
<a class="reference external" href="http://scripts.sil.org/OFL">http://scripts.sil.org/OFL</a></li>
<li>Font Awesome CSS, LESS, and SASS files are licensed under the MIT License
<a class="reference external" href="http://opensource.org/licenses/mit-license.html">http://opensource.org/licenses/mit-license.html</a></li>
<li>The Font Awesome pictograms are licensed under the CC BY 3.0 License
<a class="reference external" href="http://creativecommons.org/licenses/by/3.0/">http://creativecommons.org/licenses/by/3.0/</a></li>
<li>Attribution is no longer required in Font Awesome 3.0, but much appreciated:
&quot;Font Awesome by Dave Gandy - <a class="reference external" href="http://fortawesome.github.com/Font-Awesome">http://fortawesome.github.com/Font-Awesome</a> &quot;</li>
</ul>
</div>
<div class="section" id="how-to-install">
<h3>How to install</h3>
<p>This addon can be installed has any other addons. please follow official
<a class="reference external" href="http://plone.org/documentation/kb/installing-add-ons-quick-how-to">documentation</a></p>
<p>If you need ie7 support in your project you should activate the ie7 stylesheet.</p>
</div>
<div class="section" id="how-to-use">
<h3>How to use</h3>
<p>To use an icon you can add 'icon-X' to your tag where X is the icon you want:</p>
<pre class="literal-block">
&lt;ul&gt;
    &lt;li class=&quot;icon-glass&quot;&gt;item 1&lt;/li&gt;
    &lt;li class=&quot;icon-music&quot;&gt;item 2&lt;/li&gt;
    &lt;li class=&quot;icon-search&quot;&gt;item 3&lt;/li&gt;
&lt;/ul&gt;
</pre>
<p>Or just use CSS for your class 'myclass':</p>
<pre class="literal-block">
.myclass:before {
    content: &quot;\f000&quot;;
    font-family: FontAwesome;
    font-style: normal;
    font-weight: normal;
    text-decoration: inherit;
}
</pre>
<p>to know more on the content to use or class to use you can look at the code
<a class="reference external" href="https://github.com/FortAwesome/Font-Awesome/blob/master/docs/assets/css/font-awesome.css#L272">https://github.com/FortAwesome/Font-Awesome/blob/master/docs/assets/css/font-awesome.css#L272</a></p>
<p>An example page is avaible in the addon, here is a screenshot:</p>
<img alt="http://plone.org/products/collective.fontawesome/screenshot" src="http://plone.org/products/collective.fontawesome/screenshot" />
</div>
<div class="section" id="credits">
<h3>Credits</h3>
<div class="section" id="companies">
<h4>Companies</h4>
<ul class="simple">
<li>Makina-Corpus <a class="reference external" href="http://www.makina-corpus.com">http://www.makina-corpus.com</a></li>
</ul>
</div>
<div class="section" id="people">
<h4>People</h4>
<ul class="simple">
<li>JeanMichel FRANCOIS aka toutpt &lt;<a class="reference external" href="mailto:toutpt&#64;gmail.com">toutpt&#64;gmail.com</a>&gt;</li>
</ul>
</div>
</div>
<div class="section" id="changelog">
<h3>Changelog</h3>
<div class="section" id="id1">
<h4>1.0.2 (2013-05-14)</h4>
<ul class="simple">
<li>Update to fontawesome 3.1.1</li>
</ul>
</div>
<div class="section" id="id2">
<h4>1.0.1 (2013-05-06)</h4>
<ul class="simple">
<li>Fix packaging (manifest)</li>
</ul>
</div>
<div class="section" id="id3">
<h4>1.0 (2013-05-06)</h4>
<ul class="simple">
<li>Package created using templer
[JeanMichel aka toutpt]</li>
</ul>
</div>
</div>
]]></content:encoded>
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Jean-Michel FRANCOIS</dc:creator>
    <dc:rights></dc:rights>
    <dc:date>2013-05-06T12:43:40Z</dc:date>
    <dc:type>Software Project</dc:type>
  </item>


  <item rdf:about="http://plone.org/support/sites/forum-verejne-zakazky-kvalitne">
    <title>Fórum Veřejné zakázky kvalitně</title>
    <link>http://plone.org/support/sites/forum-verejne-zakazky-kvalitne</link>
    <description>"Fórum Veřejné zakázky kvalitně" is a joint project of the Chamber of Public Contract Administrators and the Ministry of Industry and Trade of the Czech Republic, which seeks to increase efficiency in the procurement process in the Czech Republic, especially the consistent application of the principles of "3E" (economy, efficiency and effectiveness of public performance administration and management of public funds).</description>
    
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Pavel Machula</dc:creator>
    <dc:rights></dc:rights>
    <dc:date>2013-05-05T11:15:00Z</dc:date>
    <dc:type>Site using Plone</dc:type>
  </item>


  <item rdf:about="http://plone.org/support/providers/mware-cz">
    <title>MWare CZ</title>
    <link>http://plone.org/support/providers/mware-cz</link>
    <description>Advisory services in IT security and compliance</description>
    
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Pavel Machula</dc:creator>
    <dc:rights></dc:rights>
    
      <dc:subject>Consulting</dc:subject>
    
    <dc:date>2013-05-05T11:15:00Z</dc:date>
    <dc:type>Provider</dc:type>
  </item>


  <item rdf:about="http://plone.org/support/sites/loucen-concours-delegance">
    <title>Loučeň Concours d'Elegance</title>
    <link>http://plone.org/support/sites/loucen-concours-delegance</link>
    <description>The Chateau Loučeň Concours d’Elegance is a classic car exhibition of top-class vintage cars and is included in the FIVA calendar. The Chateau Loučeň Concours d’Elegance aims to establish itself as the main event in the region of the Central Europe and takes inspiration from well established and respected events like Villa d’Este or Pebble Beach.</description>
    
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Pavel Machula</dc:creator>
    <dc:rights></dc:rights>
    <dc:date>2013-05-05T11:10:00Z</dc:date>
    <dc:type>Site using Plone</dc:type>
  </item>


  <item rdf:about="http://plone.org/support/sites/advokatni-kancelar-dana-pergl-partneri">
    <title>Dáňa, Pergl &amp; Partners attorneys at law </title>
    <link>http://plone.org/support/sites/advokatni-kancelar-dana-pergl-partneri</link>
    <description>Dáňa, Pergl &amp; Partners is a law office with more than fifteen years history, a company that from the very beginning has followed the path of branch specialization with emphasis on providing highly-professional and specialized services.</description>
    
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Pavel Machula</dc:creator>
    <dc:rights></dc:rights>
    <dc:date>2013-05-05T11:05:00Z</dc:date>
    <dc:type>Site using Plone</dc:type>
  </item>


  <item rdf:about="http://plone.org/support/providers/computing-insights">
    <title>Computing Insights</title>
    <link>http://plone.org/support/providers/computing-insights</link>
    <description>Computing Insights is a San Diego, California based company with over 19 years of experience in successfully developing, integrating, designing and hosting web applications with the Zope application server and 13 years with the Plone web framework. We not only have the technical skills but also the business and marketing skills to meet demanding business needs.</description>
    
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Tom Scrivner</dc:creator>
    <dc:rights></dc:rights>
    
      <dc:subject>Custom development</dc:subject>
    
    
      <dc:subject>Consulting</dc:subject>
    
    
      <dc:subject>Training</dc:subject>
    
    
      <dc:subject>Hosting provider</dc:subject>
    
    <dc:date>2013-05-04T21:40:00Z</dc:date>
    <dc:type>Provider</dc:type>
  </item>


  <item rdf:about="http://plone.org/support/sites/riskcenter.com">
    <title>RiskCenter.com</title>
    <link>http://plone.org/support/sites/riskcenter.com</link>
    <description>A Wall Street, financial news service, RiskCenter.com needed a new portal and content management system(CMS). Their old CMS/Portal software was having numerous problems managing their large worldwide subscriber base of financial professionals. Computing Insights crafted a Plone 4 and MySQL solution to meet their demanding current and future needs.


Plone's mature industrial strength platform met the RiskCenter's demanding requirements for member management, article creation and article management. The new Plone system allows visitors to see a short summary of new articles and subscribers to see the complete articles. An easy to use advertising and automated daily HTML newsletter (RiskAlert tm) management system was developed to streamline their daily operations. A python-based API sub-system was constructed with a major Email provider to fully automate daily newsletter subscriptions and a synchronized subscriber list.


The RiskCenter's large and growing 17,000+ article MySQL database was integrated into their new large scale portal. A large percentage of the articles incorporate rich media assets in the form of multiple images, diagrams and drawings.</description>
    
    <dc:publisher>No publisher</dc:publisher>
    <dc:creator>Tom Scrivner</dc:creator>
    <dc:rights></dc:rights>
    <dc:date>2013-05-04T18:06:46Z</dc:date>
    <dc:type>Site using Plone</dc:type>
  </item>




</rdf:RDF>
