Modified items

All recently modified items, latest first.

collective.alerts-1.2.3-2.lbn25.noarch: This product implements Cory LaViska's 'JQuery Alert Dialogs' for Plone. Basically, they are fancy, styleable replacements for the standard 'alert', 'confirm' and 'prompt' browser functions. Please see: http://abeautifulsite.net/notebook/87 for more information. Usage ----- When collective.alerts is installed and the jquery.alerts library registered in portal_javascripts (should be automatic), then the alerts can be called as follows: - jAlert( message, [title, callback] ) - jConfirm( message, [title, callback] ) - jPrompt( message, [value, title, callback] )

collective-sd.analytics-0.1.3-1.lbn25.noarch: Simple Google analytics integration for Singing & Dancing Adds tracking parameters to urls in outgoing S&D newsletters. See browser.txt for more in depth info. Note for translators: Titles and descriptions for the configuration ui can be lifted from http://www.google.com/support/analytics/bin/answer.py?hl=en&answer=55578 in almost any language.

collective-2.2.6-3.lbn25.noarch

archetypes.schemaextender-2.1.8-1.lbn25.noarch: This package allows you to modify an Archetypes schema, using simple adapters. This can be used to add new fields, reorder fields and fieldsets or make other changes. The most common use of schema extension is to allow add-on products to enhance standard Plone content types, for example by adding an option that can be set to toggle special behaviour. schemaextender hooks into the Archetypes framework by registering an ISchema adapter for BaseContent and BaseFolder, making it responsible for providing the schema for all types derived from those classes. This includes all standard Plone content types. Since only one ISchema adapter can be active schemaextender provides its own mechanism to modify schemas using named adapters. There are three types of adapters available: * ISchemaExtender: using this adapter you can add new fields to a schema. * IOrderableSchemaExtender: this adapters makes it possible to both add new fields and reorder fields. This is more costly than just adding new fields. * IBrowserLayerAwareExtender: this adpaters are making use of plone.browserlayer, so that the extender is only available if a layer is registered. * ISchemaModifier: this is a low-level hook that allows direct manipulation of the schema. This can be very dangerous and should never be used. The adapter types are documented in the ''interfaces.py'' file in archetypes.schemaextender.

archetypes.referencebrowserwidget-2.5.10-1.lbn25.noarch: This is an implementation of referencebrowser widget. It provides a widget used for Archetypes reference-fields. The widget can be used on its own or as a dropin replacement of the ATReferenceBrowserWidget in Plone 3 and is included in Plone >= 4. Unlike the ATReferenceBrowserWidget, archetypes.refencebrowserwidget uses an overlay instead of a popup to display the referencebrowser.

archetypes.querywidget-1.1.3-1.lbn25.noarch: archetypes.querywidget

archetypes.kss-1.7.3-1.lbn25.noarch: KSS (Kinetic Style Sheets) for Archetypes This product gives generic KSS support to Archetypes. It depends on the product "kss.core" and "plone.app.kss".

Products.rendezvous-1.4-7.lbn25.noarch: Products.rendezvous is a timeboard to select a rendez-vous when most people are available. You create a RendezVous content type where you select some days. For each date, you create 0 to several slots (for instance: 1pm, 2pm, morning, evening) and you publish your object. Then you send the url to all people you want to see at this rendezvous. Each member of the portal can participate to this rendezvous. The user checks the days and slots which for he or she is available.

Products.UserAndGroupSelectionWidget-3.0b5-1.lbn25.noarch: UserAndGroupSelectionWidget is an Archetypes widget to search and select users and/or groups from a huge base of users. It uses a modernized, fast code-base and is tested with hundreds of groups and thousands of users. It is configureable to select only groups, only users, both or only user of a distinct group. Using translation-adaptors you can use generic group names and genric group filters. The translation adaptor will translate it into real group ids or group id filters.

Products.TinyMCE-1.4.3-1.lbn25.noarch: Adds support for TinyMCE, a platform independent web based Javascript HTML WYSIWYG editor, to Plone.

Products.TextIndexNG-3.4.14-1.lbn25.noarch: Features: * DocumentConverters * StemmerSupport for 13 languages * SimilaritySearch for english text (based on the Levenshtein distance) * NearSearch, * PluggableParsers * extended StopWords support * full integration in ZCatalog * TestFunctionality through ZMI * ExtensibleArchitecture * being MoreEfficient than the current !TextIndex * full globbing support (wildcard search) * NormalizationSupport (e.g. reducing accented characters to their base form) * full UnicodeAwareness * Relevance ranking of search results added. Searches are now ranked using an extended cosine measure. The cosine measure is based on a vector model and calculates the document "score" based on the frequency of the query terms inside the document result set. * Much faster phrase/near search: the old implementation of TextIndexNG had to perform a very expensive job at query time when phrase/near search was performed. Re-using the !WidCode module of !ZCTextIndex made this operation less expensive. * Left-truncation added: TextIndexNG can be configured creation-time time to support left-truncation (means you can search for "*suffix") Left-truncation is an option because this feature requires a second reverted index inside the lexicion and much more memory! * optional auto-expansion support: This optional feature allows you to get better search results when some of the query terms could not be found. The index expands a query term "foo" to "foo*" if there was no hit for "foo". This expansion is currently global for the index. This feature will be available on a per-query basis in a later version. (Auto-expansion will be extended in a later version to search for similiar terms) * improved HTML converter: now using Chris Withers "Strip-o-Gram" module instead of the Strip-Tag-Parser * added converter for text/sgml * Similarity search (soundex, metaphone, doublemetaphone) dropped and replace with a more general approach and language indepedant approach using the Levenshtein distance. * range searches like "Fi..Foo" * substring searches "substring"

Products.SimpleAttachment-4.4-1.lbn25.noarch: Several Plone products have a need to handle simple attachments: content types that do not have a workflow of their own but will reuse the permissions on their container. SimpleAttachment implements simple file and image attachment types that can serve this need.

Products.Sessions-4.1-1.lbn25.py37.noarch: Zope 2 session management.

Products.SecureMailHost-1.1.2-4.lbn25.noarch

Products.RobotsTool-3.0.2-4.lbn25.noarch: You can read more about robots.txt at: * http://www.google.com/bot.html * http://www.robotstxt.org/wc/exclusion-admin.html

Products.ResourceRegistries-2.2.13-1.lbn25.noarch: A registry for linked Stylesheet files and Javascripts. This registry is mainly aimed at solving the following usecases: - Enable product authors to register stylesheets with their product installers without having to resort to override either header.pt or ploneCustom.css creating potential conflicts with other products. - Enable more componentialization of the stylesheets provided with Plone (and other products) without having to increase the number of http requests for a Plone page. - Enable condition checking on stylesheets. Great for variable look-and-feel for groups/roles/folders/departments/content-types/etc - Enable inline dynamic stylesheets. For those style rules that should vary for each request. Mainly used for things like header-bar- backgroundimages, department colors etc. - Enable developers to activate/deactivate their styles in a simpler way - Enable compression to safe bandwidth and download time If several stylesheets listed directly after each other in the registry have the same parameters and expression, they will be concatenated into a larger, composite, stylesheet on rendering. - This can be useful for splitting stylesheets into smaller components for overrideing, while preserving cacheability and minimising the number of http-requests to Plone. This tool was started at the excellent SnowSprint 2005 - Organised by Telesis in the Austrian Alps. Thanks, Jodok! :)

Products.QuotaFolder-0.1.1-2.lbn25.noarch: QuotaFolder is a folder-ish object that restricts the total number of objects, their total size and their individual maximum size. QuotaFolder takes subfolders (recursively) into account, so it should not be possible to escape the quota restrictions. The basic goal of QuotaFolder is not to put an absolute limit on ZODB usage - it is impossible to determine this. For example, each object may have several revisions in the ZODB, and some of the internal state of the object is stored in the ZODB that's not returned by get_size(). The goal is to limit the use of objects in general, to prevent people from offering large files or using up resources with enormous amounts of objects.

Products.Quills-remoteblogging-1.8.1-1.lbn25.noarch: Use your Blog with any Weblog Editor that supports the `MetaWeblog API`_. This feature requires the ``Products.MetaWeblogPASPlugin`` product to be installed into your Plone site. .. _MetaWeblog API: http://www.metaweblogapi.com/

Products.Quills-1.8.1-1.lbn25.noarch: Enterprise-strength blogging for Plone

Products.PythonScripts-3.0-1.lbn25.noarch: Overview The Python Scripts product provides support for restricted execution of Python scripts, exposing them as callable objects within the Zope environment. Providing access to extra modules Python script objects have a limited number of “safe” modules available to them by default. In the course of working with Zope, you will probably wish to make other modules available to script objects. The Utility.py module in the PythonScripts products provides a simple way to make modules available for use by script objects on a site-wide basis. Before making a module available to Python scripts, you should carefully consider the potential for abuse or misuse of the module, since all users with permission to create and edit Python scripts will be able to use any functions and classes defined in the module. In some cases, you may want to create a custom module that just imports a subset of names from another module and make that custom module available to reduce the risk of abuse. The easiest way to make modules available to Python scripts on your site is to create a new directory in your Products directory containing an __init__.py file. At Zope startup time, this “product” will be imported, and any module assertions you make in the __init__.py will take effect. Here’s how to do it: In your Products directory (either in lib/python of your Zope installation or in the root of your Zope install, depending on your deployment model), create a new directory with a name like “GlobalModules”. In the new directory, create a file named __init__.py. Edit the __init__.py file, and add calls to the ‘allow_module’ function (located in the Products.PythonScripts.Utility module), passing the names of modules to be enabled for use by scripts. For example: from Products.PythonScripts.Utility import allow_module allow_module('base64') allow_module('re') allow_module('DateTime.DateTime') This example adds the modules ‘base64’, ‘re’ and the ‘DateTime’ module in the ‘DateTime’ package for use by Python scripts. Note that for packages (dotted names), each module in the package path will become available to script objects. Restart your Zope server. After restarting, the modules you enabled in your custom product will be available to Python scripts. Placing security assertions within the package/module you are trying to import will not work unless that package/module is located in your Products directory. This is because that package/module would have to be imported for its included security assertions to take effect, but to do that would require importing a module without any security declarations, which defeats the point of the restricted Python environment. Products work differently as they are imported at Zope startup. By placing a package/module in your Products directory, you are asserting, among other things, that it is safe for Zope to check that package/module for security assertions. As a result, please be careful when place packages or modules that are not Zope Products in the Products directory.

Next 20 items » 1 2 3 4 5 6 7 ... 1766


	Copyright © 2000-2019 Corporation of Balclutha Inc. All rights reserved.

Sections

Modified items