You are here: Home

Modified items

All recently modified items, latest first.
RPMPackage raptus.article.alias-1.0a6-1.lbn19.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.lbn25.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.3-1.lbn19.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.3-1.lbn19.noarch
quintagroup.seoptimizer allows per document editing of: HTML Title tag META description tag META keywords tag HTML comment into page header HTML noframes tag into page header META robots tag META Disposition tag Canonical URl http://projects.quintagroup.com/products/wiki/qSEOptimizer#CanonicalURL For Title, description keywords and comment you have statistics (total/stop/used words, field length counter).
RPMPackage quintagroup.portlet.cumulus-1.2-3.lbn19.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-1.0-1.lbn19.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.8.2-1.lbn19.noarch
Plone Google Sitemaps allows you to enable different kinds of Google Sitemaps on your Plone website. Such Sitemaps help Google identify site URLs and the data under each site section. With Google Sitemaps enabled, search engines could track your Plone site URLs faster and more efficiently, optimizing their search by placing all the information on one page. With Plone Google Sitemaps product you can enable following Sitemap types on your Plone website: Content Sitemap - is a regular list of pages on your website. Creating and submitting such a Sitemap lets Google know about all the pages on your Plone website, including URLs that may not be discoverable by Google’s normal crawling process. Mobile Sitemap - is a specific type of Sitemap, that indexes all site URLs that serve mobile-oriented content. News Sitemap - is different from regular Sitemaps, since it is specific to Google News only. It uses the Sitemap protocol, with additional News-specific tags, defined by Google. The package brings protocol with additional Google Sitemaps tab to News Item content type for defining NewsSitemap-specific meta tags. Different Sitemap types index their own content and do not depend on other Sitemaps.
RPMPackage quintagroup.plonecaptchas-4.2-2.lbn19.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-1.lbn25.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.4.3-1.lbn19.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.lbn19.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.lbn19.noarch
Python namespace module
RPMPackage qi.portlet.TagClouds-1.35-1.lbn19.noarch
qi.portlet.TagClouds is a plone product that adds tag cloud portlet support. The following parameters of the portlet are configurable through the web: portlet title number of different tag sizes maximum tags to show content types searched (optionally) tags (subjects) searched (optionally) section of the site to be searched workflow states searched filtering by keywords so that a tag cloud of all keywords that are combined with the filter keywords is shown qi.portlet.TagClouds also comes with a simple caching mechanism. Cache remains valid for a time interval that can be set in the portlet settings.
RPMPackage pytz-2016.10-1.lbn19.noarch
pytz brings the Olson tz database into Python. This library allows accurate and cross platform timezone calculations using Python 2.3 or higher. It also solves the issue of ambiguous times at the end of daylight savings, which you can read more about in the Python Library Reference (datetime.tzinfo). Amost all (over 540) of the Olson timezones are supported.
RPMPackage python2-zodbpickle-1.0.2-1.lbn25.x86_64
This package presents a uniform pickling interface for ZODB: - Under Python2, this package forks both Python 2.7's pickle and cPickle modules, adding support for the protocol 3 opcodes. It also provides a new subclass of bytes, zodbpickle.binary, which Python2 applications can use to pickle binary values such that they will be unpickled as bytes under Py3k. - Under Py3k, this package forks the pickle module (and the supporting C extension) from Python 3.2, Python 3.3, and Python 3.4. The fork adds support for the noload operations used by ZODB.
RPMPackage python2-webencodings-0.5.1-6.lbn25.py37.noarch
This is a Python implementation of the WHATWG Encoding standard.
RPMPackage python2-urllib3-1.16-3.lbn19.noarch
Python2 HTTP module with connection pooling and file POST abilities.
RPMPackage python2-requests-2.11.1-3.lbn19.noarch
Most existing Python modules for sending HTTP requests are extremely verbose and cumbersome. Python’s built-in urllib2 module provides most of the HTTP capabilities you should need, but the API is thoroughly broken. This library is designed to make HTTP requests easy for developers.
RPMPackage python2-pillow-3.4.2-1.lbn19.x86_64
Python image processing library, fork of the Python Imaging Library (PIL) This library provides extensive file format support, an efficient internal representation, and powerful image processing capabilities. There are four subpackages: tk (tk interface), qt (PIL image wrapper for Qt), devel (development) and doc (documentation).
RPMPackage python2-piexif-1.0.13-1.lbn25.py37.noarch
Very simple Python library to simplify exif manipulations that does not depend on other libraries. There are only just five functions: load(filename) - Get exif data as dict. dump(exif_dict) - Get exif as bytes to save with JPEG. insert(exif_bytes, filename) - Insert exif into JPEG. remove(filename) - Remove exif from JPEG. transplant(filename, filename) - Transplant exif from JPEG to JPEG. Python 2 version.