You are here: Home

Modified items

All recently modified items, latest first.
RPMPackage raptus.article.default-2.0b13-1.lbn13.noarch
If you install the default package like the core package, you will get automatically the usual types like link, image, etc.. Besides if you install the article with default, you will not have to register all packages in buildout.cfg. The default package find automatically all component packages of raptus.article. For details read the doc of `default package <http://pypi.python.org/pypi/raptus.article.default/>`_.
RPMPackage raptus.article.core-2.0b17-1.lbn13.noarch
This package provides a configurable article content type, which replaces the default Page content type. The following features for raptus.article are provided by this package: Content ------- * Article - Page Type - folderish Components ---------- * Related Items - Component - Component showing related Items. Other ----- * zcml namespace (article) - used to initialize new components.
RPMPackage raptus.article.contentswitcher-1.0b5-1.lbn13.noarch
Provides a jQuery based content switcher. The following features for raptus.article are provided by this package: Components ---------- * Content switcher (continually fades in and out the contained articles and provides a navigation) * Content switcher teaser (continually fades in and out the contained articles and provides a navigation)
RPMPackage raptus.article.contentflow-2.0b4-2.lbn13.noarch
The following features for raptus.article are provided by this package: Components ---------- * Content flow (showing the contained articles like in iTunes) * Content flow teaser (showing the contained articles like in iTunes and is displayed above the columns)
RPMPackage raptus.article.contentfader-2.0b6-2.lbn13.noarch
Provides a component which continually fades in and out the contained articles.
RPMPackage raptus.article.collections-1.0a1-1.lbn13.noarch
Provides basic collection components. The following features for raptus.article are provided by this package: Components ---------- * Collections (Collections including their results contained in the article) * Collections left (Collections including their results contained in the article on the left side) * Collections right (Collections including their results contained in the article on the right side) * Collections columns (Collections including their results contained in the article arranged in columns)
RPMPackage raptus.article.backlink-1.0a1-1.lbn13.noarch
raptus.article.backlink provides support for adding a back link to articles. The following features for raptus.article are provided by this package: Components ---------- * raptus.article.backlink
RPMPackage raptus.article.allcontent-1.0a3-1.lbn13.noarch
Provides a component which displays the whole content of the contained articles. The following features for raptus.article are provided by this package: Components ---------- * All content (List of the contained articles displayed with all their content.)
RPMPackage raptus.article.alias-1.0a5-1.lbn13.noarch
Provides the possibility to create aliases for content objects which may be contained in an article and display them in the specified components.
RPMPackage raptus.article.additionalwysiwyg-2.0b7-1.lbn13.noarch
Extends the article by a second WYSIWYG text field to make it possible to split your text into two parts and display it for example above and below another component. The following features for raptus.article are provided by this package: Fields ------ * Additional WYSIWYG text field for the articles. Components ---------- * Additional text (displays your text above an image or a video) * Additional text left (displays your text in a separate column on the left) * Additional text right (displays your text in a separate column on the right)
RPMPackage quintagroup.z3cform.captcha-1.0.1-3.lbn13.noarch
quintagroup.z3cform.captcha is a package that allows to add captcha to the z3c.form. As a result such forms are prevented from automatic submit. Captchas in a z3c form Using quintagroup.z3cform.captcha in a z3c.form form is simple. Just add a Captcha field to your schema, use CaptchaWidgetFactory widget factory for this field and away you go: >>> from zope.interface import Interface >>> from z3c.form import form, field >>> from quintagroup.z3cform.captcha import Captcha >>> from quintagroup.z3cform.captcha import CaptchaWidgetFactory Now define form schema with Captch field >>> class ICaptchaSchema(Interface): ... captcha = Captcha( ... title=_(u'Type the code'), ... description=_(u'Type the code from the picture shown below.')) And set proper widget factory for the captcha field >>> class CaptchaForm(form.Form): ... fields = field.Fields(ICaptchaSchema) ... fields['captcha'].widgetFactory = CaptchaWidgetFactory and z3c.form will take care of the rest. The widget associated with this field will render the captcha and verify the use input automatically.
RPMPackage quintagroup.seoptimizer-4.2.0-2.lbn13.noarch
Quintagroup Search Engine Optimization Tool
RPMPackage quintagroup.portlet.cumulus-1.2-3.lbn13.noarch
Introduction quintagroup.portlet.cumulus is a Plone product that allows you to add tag cloud portlets to your Plone site. Your site's tags (content categories are used as tags) are displayed using a Flash movie that rotates them in 3D. It works just like a regular tags cloud, but is more visually exciting. This is the WordPress WP-Cumulus plugin ported to Plone as a portlet. When you add this portlet anywhere in the site it will display all site's tags. If you have installed QullsEnabled product this portlet will display only blog's tags when rendered inside blog. Usage * Install "Tag cloud (cumulus) portlet" with QuickInstaller. * Select Tag Cloud (cumulus) portlet from Add portlet drop-down menu. * Provide your own values for portlet configuration if needed. * Save changes.
RPMPackage quintagroup.plonetabs-0.7-1.lbn13.noarch
The product allows Plone websites to manage portal_actions tool from portal_control_panel configlet. This release is a fully rewritten version of earlier qPloneTabs product versions. It is based on kss javascript framework and plone 3 technologies.
RPMPackage quintagroup.plonegooglesitemaps-1.7.0-2.lbn13.noarch
Allows Plone websites to get better visibility for Google search engine
RPMPackage quintagroup.plonecaptchas-4.2-2.lbn13.noarch
quintagroup.plonecaptchas is a simple captchas implementation for Plone, designed for validation of human input in insecure forms. This is a standalone implementation which does not depend on captchas.net services. quintagroup.plonecaptchas adds captcha support to Plone, it works together with quintagroup.captcha.core package (http://projects.quintagroup.com/products/wiki/quintagroup.captcha.core) and quintagroup.formlib.captcha (http://projects.quintagroup.com/products/wiki/quintagroup.formlib.captcha) With these products installed captchas will be added to Plone's 'Send this', 'Contact Us' (/contact-info) forms, and Plone's default discussion mechanism: 'Add Comment' and 'Reply' forms. quintagroup.plonecaptchas does not automatically plug to Plone's default registration (/@@register). You can make captcha plug to Plone's Register form via Zope Management Interface. Instructions here: http://projects.quintagroup.com/products/wiki/quintagroup.plonecaptchas#JoinForm
RPMPackage quintagroup.formlib.captcha-1.4-3.lbn13.noarch
Introduction quintagroup.formlib.captcha is a package that allows to add captcha to zope.formlib. As a result such forms are prevented from automatic submit. Captchas in a formlib form Using quintagroup.formlib.captcha product in a formlib form is simple. Just add a Captcha field to your schema, and away you go: >>> from zope.interface import Interface >>> from quintagroup.formlib.captcha.form import Captcha >>> class CaptchaSchema(Interface): ... captcha = Captcha( ... title=_(u'Type the code'), ... description=_(u'Type the code from the picture shown below.')) and formlib will take care of the rest. The widget associated with this field will render the captcha and verify the use input automatically.
RPMPackage quintagroup.captcha.core-0.3-4.lbn13.noarch
Quintagroup Captcha Core (quintagroup.captcha.core) is a core package of simple captcha implementation. It allows to configure captchas on your Plone site. This product works together with other Quintagroup captcha products. To protect standard Plone forms with captcha - use quintagroup.plonecaptchas package. After product installation you'll see 'Plone captchas setup' option under 'Add-on Product Configuration' in Site Setup. There you can select what kind of captchas you want to appear: either static or dynamic. In case you select dynamic - captcha images will be generated on the fly and you will be able to configure captchas look by using different font sizes, background and font colours, period, amplitude, random values.
RPMPackage quintagroup.analytics-1.1.1-2.lbn13.noarch
Introduction Quintagroup Analytics Tool (quintagroup.analytics) provides statistic information about your Plone site. It adds few content stats views of plone content workflow states, ownership and portlets registered on different contexts. Information provided by Quintagroup Analytics Tool allows you to see Plone site content from different perspectives. This information can be very useful while migrating your site into newer Plone version, or into another CMS. With its help you can visually audit the content setup in Plone site before migration and compare it with the migrated website structure. Usage To see your Plone site statistic information - navigate to 'Quintagroup Analytics' item under Add-on Products Configuarion. Browse through all configlet tabs to see all statistic information, generated by Quintagroup Analytics Tool: * Content Ownership by Type - information about most popular content types on your site. Here you can see the most frequently created content types on your site and their owners. * Content Ownership by State - information about site's content workflow states. Here you can see how many content object are published/submitted for review/etc. and their owners. * Content Types by State - information about site's most frequently created content types and their workflow states. * Site Portlets - information about site portlets assigned throughout site sections. This information can be exported into .csv format. You can see all portlets assigned on your site and edit them. * Legacy Portlets - information about legacy assigned throughout site sections. This information can be exported into .csv format. * Properties stats - information on certain property values for all site objects, such as titles, descriptions, etc. This information can be exported into .csv format.
RPMPackage quintagroup-1.1.1-2.lbn13.noarch
Python namespace module