Search results

collective.js.ui.multiselect-1.0-1.lbn19.noarch

This package turns HTML multiple select fields into a fancy widget. It integrates the jQuery UI multiselect plugin into plone. jQuery UI multiselect The plugin and a demo is located at http://www.quasipartikel.at/multiselect/ The plugin is published under the MIT license, this package is released under GPL2.

collective.js.ui.multiselect-1.0-1.lbn25.noarch

This package turns HTML multiple select fields into a fancy widget. It integrates the jQuery UI multiselect plugin into plone. jQuery UI multiselect The plugin and a demo is located at http://www.quasipartikel.at/multiselect/ The plugin is published under the MIT license, this package is released under GPL2.

collective.js.underscore-1.5.2-1.lbn19.noarch

Bundles underscore.js for use with Plone. The version number of this module is equal to the used underscore.js version.

collective.js.underscore-1.5.2-1.lbn25.noarch

Bundles underscore.js for use with Plone. The version number of this module is equal to the used underscore.js version.

collective.jsonify-0.1-4.lbn13.noarch

collective.jsonify exports your Plone content to JSON. Many packages that export data from Plone have complicated dependencies, and so only work with Plone 3.0 or higher (or not even with 3.0). collective.jsonify's only dependency is simplejson. It can be installed in any Plone version, probably as far back as Plone 2.0 (not tested!). The exported JSON is a collective.transmogrifier friendly format. Install collective.jsonify on a site you want to export from, and setup an import transmogrifier pipeline on the site you're importing to, using the blueprints in the collective.jsonmigrator package. The @@jsonify BrowserView is also available with actions: query, list, get: Parameters are important. Here are some interesting examples: - ACTION = QUERY : get MODIFIED (from date - to date) objects http://www.myplonesite.com/custompath/deep/@@jsonify ?action=query &portal_type=my_at_or_dexterity_type &show_inactive=True &modified:list:date=2013-01-01 &modified:list:date=2013-03-01 &modified_usage=range:min:max MORE: if "available" parameter is added, it returns the NUMBER of objects the query returned, NULL if no returns MORE: "send_bin" parameter is "False" by default. You can change this by passing "send_bin=True" MORE: "absolute_urls" parameter is "True" by default. You can change this by passing "absolute_urls=False" IMPORTANT: "path" parameter is not needed: is always considered in the query, from URL path - ACTION = LIST : COMPACT LIST OF LIVE OBJECTS Why should I get it? Because by comparing it with the objects list in your mobile APP, you can have an evidence of DELETED objects. What is returned: [{"uid":value,"path":value}] What you cannot get: when an object has been deleted. * BINARY FIELDS: - binary fields names starts with "_datafield_" and are exported as dictionary, so you can download data separatly. Example: An Image field called "photo" from a custom Archetype content is exported as: "_datafield_photo": "{\"filename\": \"alpino-pizzeria.jpg\", \"data\": \" \", \"content_type\": \"image/jpeg\", \"size\": 55536, "md5": "fa2b0abcf540d2dde71d68071140a803"}"

collective.jsonify-1.6-1.lbn19.noarch

collective.jsonify exports your Plone content to JSON. Many packages that export data from Plone have complicated dependencies, and so only work with Plone 3.0 or higher (or not even with 3.0). collective.jsonify's only dependency is simplejson. It can be installed in any Plone version, probably as far back as Plone 2.0 (not tested!). The exported JSON is a collective.transmogrifier friendly format. Install collective.jsonify on a site you want to export from, and setup an import transmogrifier pipeline on the site you're importing to, using the blueprints in the collective.jsonmigrator package. The @@jsonify BrowserView is also available with actions: query, list, get: Parameters are important. Here are some interesting examples: - ACTION = QUERY : get MODIFIED (from date - to date) objects http://www.myplonesite.com/custompath/deep/@@jsonify ?action=query &portal_type=my_at_or_dexterity_type &show_inactive=True &modified:list:date=2013-01-01 &modified:list:date=2013-03-01 &modified_usage=range:min:max MORE: if "available" parameter is added, it returns the NUMBER of objects the query returned, NULL if no returns MORE: "send_bin" parameter is "False" by default. You can change this by passing "send_bin=True" MORE: "absolute_urls" parameter is "True" by default. You can change this by passing "absolute_urls=False" IMPORTANT: "path" parameter is not needed: is always considered in the query, from URL path - ACTION = LIST : COMPACT LIST OF LIVE OBJECTS Why should I get it? Because by comparing it with the objects list in your mobile APP, you can have an evidence of DELETED objects. What is returned: [{"uid":value,"path":value}] What you cannot get: when an object has been deleted. * BINARY FIELDS: - binary fields names starts with "_datafield_" and are exported as dictionary, so you can download data separatly. Example: An Image field called "photo" from a custom Archetype content is exported as: "_datafield_photo": "{\"filename\": \"alpino-pizzeria.jpg\", \"data\": \" \", \"content_type\": \"image/jpeg\", \"size\": 55536, "md5": "fa2b0abcf540d2dde71d68071140a803"}"

collective.jsonmigrator-0.2-2.lbn13.noarch

collective.jsonmigrator is a ready tool for you to migrate from old Plone sites (2.0, 2.1, 2.5) to new Plone 4.0 (or higher). Its based extensivly collective.transmogrifier and custom blueprints avaliable. What makes it different from other migration tools is that is fully documented and proven to work on lots of migration projects. Real beauty of it lays in ability to easily customize it and extend to support all your custom content types that you are using.

collective.jsonmigrator-0.3-1.lbn19.noarch

collective.jsonmigrator is a ready tool for you to migrate from old Plone sites (2.0, 2.1, 2.5) to new Plone 4.0 (or higher). Its based extensivly collective.transmogrifier and custom blueprints avaliable. What makes it different from other migration tools is that is fully documented and proven to work on lots of migration projects. Real beauty of it lays in ability to easily customize it and extend to support all your custom content types that you are using.

collective.jsonmigrator-1.0.1-1.lbn25.noarch

collective.jsonmigrator is a ready tool for you to migrate from old Plone sites (2.0, 2.1, 2.5) to new Plone 4.0 (or higher). Its based extensivly collective.transmogrifier and custom blueprints avaliable. What makes it different from other migration tools is that is fully documented and proven to work on lots of migration projects. Real beauty of it lays in ability to easily customize it and extend to support all your custom content types that you are using.

collective.lastlogin-0.1-3.lbn13.noarch

Introduction With this package it's easy to get a list of the users of a Plone site and the last time they logged in. This package has been developed for a customer of Zest Software to get an overview of active users. Only a minimal version was required and that's exactly what this is. Usage The easiest way to use this package is to include it in your buildout configuration. Then go to <plone_site>/@@lastlogin to get a list of Plone users and the last time they logged in.