Modified items

All recently modified items, latest first.

collective.ptg.garagedoor-0.1-1.lbn13.noarch: uigallery display type for collective.plonetruegallery Comes with the "jqueryui" effects (most of them are pretty useless, though)

collective.ptg.galleryimage-1.0-1.lbn13.noarch: Create a GalleryImage type. The purpose of this field is to provide a more robust field for collective.plonetruegallery to utilize for some of it's galleries. Implementation Utilizes the Image type along with archetypes.schemaextender to create the type. The benefit of using this approach is that there is no new persistent object types added to the zodb so uninstall should be a breeze and removing the product will mean those existing types will behave just like the normal image type.

collective.ptg.galleryfolder-0.3-1.lbn13.noarch: galleryfolder gallery type for plonetruegallery

collective.ptg.galleriffic-1.1.2.1-1.lbn13.noarch: .galleriffic

collective.ptg.galleria-1.3.0-1.lbn13.noarch: Basic integration of the Galleria javascript gallery with collective.plonetruegallery

collective.ptg.flickr-0.1.1-1.lbn13.noarch: Add on collective.plonetruegallery to aggregate from flickr

collective.ptg.fancybox-1.0.3-1.lbn13.noarch: .fancybox

collective.ptg.easyslider-0.5.1-1.lbn13.noarch: Easyslider gallery type for plonetruegallery

collective.ptg.contentleadimage-1.0-1.lbn13.noarch: This product provides an adapter for collective.plonetruegallery to display contentleadimages from collective.contentleadimage. In the weird case where an object is an image (provides IImageContent) and also has a contentleadimage, the contentleadimage is the one displayed in the gallery.

collective.ptg.contentflow-1.0.3-1.lbn13.noarch: .contentflow

collective.ptg.contactsheet-1.1.2-1.lbn13.noarch: Contact sheet gallery type for plonetruegallery

collective.ptg.carousel-0.2.2-1.lbn13.noarch: carousel display type for collective.plonetruegallery

collective.ptg.bootstrapcarousel-1.0.1-1.lbn13.noarch: Basic integration of the twitter bootstrap carousel with collective.plonetruegallery http://twitter.github.io/bootstrap/javascript.html#carousel This add-on will only work with Plone >= 4.3 as Jquery 1.7 is not supported on previous versions of Plone. Bootstrap's carousel needs Jquery 1.7 or higher

collective.proxyproperties-0.2-1.lbn13.noarch: Allow local site managers to override portal_properties property sheets. This setup will allow you to override just one property or all properties if you choose.

collective.prettysociable-0.3.1-4.lbn13.noarch: prettySociable is a jQuery plugin that tries to make sharing fun while being easy to use. It was inspired by the sharing on mashable.com. While ShareThis and AddThis provides a very useful piece code that allow users to share basically anything everywhere, their solution is not the prettiest nor the easiest to use. prettySociable simply asks the user to drag the items he wants to share onto the website he wants to send it to. The code is fully customizable, either from the CSS, or through custom settings you can set upon initialization. The original implementation can be found here: http://www.no-margin-for-errors.com/projects/prettysociable-mashable-like-sharing/ 'collective.prettysociable' is an integration of prettySociable for Plone. The following sharing services are available (see configuration to disable services): * Facebook * Twitter * Delicious * Digg * LinkedIn * Reddit * StumbleUpon * tumblr

collective.portlets.lineage-1.2.1-1.lbn13.noarch: Portlets which can optionally include or exclude content from subsites, as provided by collective.lineages Child Folder. The portlets filter out subsite paths via the use of Products.AdvancedQuery, which ships with Plone 3.x These portlets require that collective.lineages be installed in your Plone site. Currently, the following portlets are included in this package: - Recent Items - News - Events - Search - Review

collective.portlet.contact-1.1-1.lbn13.noarch: Display a contact in a Plone portlet. Contacts are provided throw backends. When installed this addon is configured to use the 'dummy' backend. You can configure this addon to use an other backend: Dummy backend, used for tests LDAP backend (add python-ldap in your setup) SugarCRM backend (add the addon collective.sugarcrm)

collective.plonetruegallery-3.4.0-1.lbn13.noarch: Introduction ------------ collective.plonetruegallery is a Plone product that implements a very customizable and sophisticated gallery. How It Works ------------ All you need to do is select the ``Gallery View`` from the ``Display`` drop down item for any Folder or Collection content type. Once that is done, a ``Gallery Settings`` tab is enabled for the type. With this, you can customize the various settings for the Gallery. Supported Display Types ----------------------- To install any of the various extra display types, you need to install the dependent package in buildout - galleria(ships with) - contact sheet(collective.ptg.contactsheet) - thumbnail zoom gallery(collective.ptg.thumbnailzoom) - presentation(collective.ptg.presentation) - galleriffic(collective.ptg.galleriffic) - highslide(collective.ptg.highslide) - fancybox(collective.ptg.fancybox) - pikachoose(collective.ptg.pikachoose) - s3slider(collective.ptg.s3slider) - nivo slider(collective.ptg.nivoslider) - nivo gallery(collective.ptg.nivogallery) - content flow(collective.ptg.contentflow) - supersized(collective.ptg.supersized)

collective.perseo-0.6.4-1.lbn13.noarch: Introduction Search Engine Optimization Package Features With collective.perseo you can manage several kind of SEO features. Globally Configurations applied to each page of the site, through 'PerSEO' tool under Add-on Configuration: * Webmaster Tools * tag title, description and keywords meta tags, separately for: o Home page o Single pages o Search page o Not Found page o Author page o Site Map page o Contact page o Event o File o Folder o Image o Link o News Item o Topic * Disable the indexing of resources using noindex and nofollow, separately for: o Search page o Login and Registration pages o Administration pages o Single pages o Event o File o Folder o Image o Link o News Item o Topic o (also handle noodp, noydir, noarchive, nosnippet) * Content types included in the sitemap.xml.gz * Ping sites (Google, Bing, Ask) automatically when the Site Map is updated * Indexing RSS feeds * Add itemscope and itemtype attributes to body tag (if you install the extension collective.perseoschema per Schema org) One by one Through 'SEO' tab on each content of the site (allows you to change SEO settings for that specific content): * tag title and description and Keywords meta tags * Meta Robots Follow Tag (follow/nofollow) * Meta Robots Index Tag (index/noindex) * Meta Robots Advanced Tag (noodp, noydir, noarchive, nosnippet) * Canonical URL * Content included in the sitemap.xml.gz (yes/no). * Priority of content in sitemap.xml.gz * itemtype attribute (if you install the extension collective.perseoschema per Schema org) SCHEMA.ORG For Schema.org attributes add the collective.perseoschema package. Warning! Installing collective.perseoschema package, the main_template and plone.path_bar, plone.global_sections, plone.header viewlets will be customized, to insert Schema.org attributes. The customizations of these resources in other Themes and Skins could be disabled.

collective.opensearch-1.5-1.lbn13.noarch: Produce Open Search Feeds collective.opensearch adds the possibility to add OpenSearch compatible search results to your Plone site. site wide: this is a simple copy of the plone search so all option that you may pass to the standard /search will be recognized as well. for a collection/topic: You can search inside a topic, i.e. you define a 'base query' as a topic and additional parameters of the query are applied additional. OpenSearch is a collection of simple formats for the sharing of search results. OpenSearch helps search engines and search clients communicate by introducing a common set of formats to perform search requests and syndicate search results. OpenSearch helps search engines and search clients communicate by introducing a common set of formats to perform search requests and syndicate search results. The OpenSearch description document format can be used to describe a search engine so that it can be used by search client applications. The OpenSearch response elements can be used to extend existing syndication formats, such as RSS and Atom, with the extra metadata needed to return search results collective.opensearch enables you to syndicate the search results of your plone site by formatting them in the RSS or Atom formats, augmented with OpenSearch response elements. Implemented extensions and conventions opensearch relevance opensearch description for autodiscovery suggestions so that browsers can autocomplete response elements and first, previous, next, last links Consume Open Search Feeds collective.opensearch adds a view to the link type that lets you search OpenSearch (or other searches that return RSS or Atom, pretty much any other format feed parser supports and KML) compatible search providers within your site. The feeds do not need to implement the opensearch extensions it suffices that they are valid feeds (e.g you can query yahoo, bing, google site search or any plone site). When you add a link with an open search url this view will be automatically set. To search e.g. plone.org from your site add a Link with the url: http://plone.org/search_rss?SearchableText={searchTerms} You can combine several open search links as a metasearch. All OpenSearch links inside a folder will be queried and their results displayed when you change the view of a folder to 'Open Search View' Usage: 1) A single remote search If you add a link content type with a open search description compatible url (i.e. it has a parameter {searchTerms} in the querystring) the view of the link will be set when the link is saved. The view consits of a simple searchform and the results of the query 2) search multiple sources at once To build a simple metasearch create a folder and add your query links to it. Change the view of the folder to 'Open Search View'. The view consist of a search form (currently only for full text search) which input will be appied to all open search links (i.e. any link that has 'Open Search View' set as its view). The results of the searches will be displayed in tabs beneath the form. The queries are executed asynchronously via AJAX, so you do not have to wait until the last query has finished. Abusing collective.opensearch to display miscelaneous feeds 3) display an abritary 'static' feed Allthough the main focus of this product is to produce and display search feeds you may use it to display any valid feed. If the url of the link you added does not contain the {searchTerms} parameter and 'Open Search View' (you have to select the view manually from the 'display' menu) is selected as the view of the link, the feed will be fetched regardless of the presence of a query parameter and its results will be displayed. The search form will not be displayed in the absence of the {searchTerms} parameter. 4) display multiple feeds Add your feeds to display to a folder (as in [2]) and select 'Open Search View' as the display view of the folder All feeds that do not have a {searchTerms} parameter in their url will be fetched immediately, regardless if a search input was provided. The search form will only be displayed if at least one of the links inside the folder has a {searchTerms} parameter. 5) Use collective.opensearch to search inside your collections As opensearch results are added to all collections you may use it as a searchform to search inside your collections. if you use a relative link (e.g. /mycollection/SearchableText={searchTerms}) you have to choose 'Open Search View' manually to display the search results.

« Previous 20 items Next 20 items » 1 ... 2315 2316 2317 2318 2319 2320 2321 ... 2359


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

Sections

Modified items