Plone Foundation ha liberado el 10-dic-2007 la cuarta versión de Plone, serie 3, versión 0.4.

Está disponible para descarga en:
http://plone.org/products/plone/releases/3.0.4

El listado de mejoras es (inglés):

Change log This is a summary of all changes.

For the complete list look at the changelog for each updated package. * Quote the description of search results in live search (security fix). * Fix the cookie handling for status message to not insert newlines on long messages. This fixes the stability problems (occasional site errors) introduced by the CVE-2007-5741 security fix. * Backed out handling of PTS as a global utility again.

It turns out that registering a persistent object both as a global utility is as bad as registering it as a module level global. This fixes the ConnectionStateErrors witnessed in Plone 3.0. * Only show the maintenance control panel for users who have management access in the Zope root. This prevents people who only have manager access in a Plone site from being able to shutdown the entire Zope instance. * Improved filename normalizer: allow filenames of up to 1023 characters instead of chopping them off at 50 and do not allow [] brackets in filenames * Remove an unneeded ZODB savepoint in the quick installer, which could cause failed installations to be commited. * Catch syntax errors in po-files when loading translation from locales folders and output a warning instead of preventing Zope from starting up. * Intelligent text improvements: accept IP addresses, port numbers and localhost in URLs, correct handling of ampersands in URLs and fix handling of URLs in brackets * Kupu visual editor fixes: o Images may only be resized if 'height' and 'width' are permitted image attributes. Resizing images in Firefox sets those attributes rather than the style attribute. o Improved support for safari/webkit browsers. o Fix image break on dragging.

* Do not version files larger than 32mb. The versioning system does not support them and we were silently breaking things. Instead show a message warning the user when he tries to version a large object. * Enable showing of differences for folder versions. * Handle ArchivistUnregisteredErrors errors during saving of versioned content. * KSS fix: fix multiple selection for field handling in safari * Allow CMFSite and PloneSite test layers to be set up more than once. * Allow through-the-web customizing of viewlets whose class name does not end with Viewlet. * Updated translations.

* Allow non-ASCII characters in webstats code. * Correct handling of workflow history with entries from anonymous and deleted users. * Update the template for the CalendarWidget to support time-only fields. * Correct migration errors for sites with a custom catalog such as QueueCatalog. * Fix invalid XHTML in Table of Contents. * Use a different method to index interfaces for content which is five times faster. Updated packages * ATContentTypes 1.2.3 * CMFDiffTool 0.3.5 * CMFEditions 1.1.4 * CMFPlone 3.0.4 * CMFQuickInstallerTool 2.0.4 * CMFTestCase 0.9.7 * PlacelessTranslationService 1.4.6 * PloneTestCase 0.9.7 * PloneTranslations 3.0.9 * PluggableAuthService 1.5.2 * kupu 1.4.6 * statusmessage 3.0.3 * archetypes.kss 1.2.4.1 * kss.core 1.2.4 * plone.app.controlpanel 1.0.3 * plone.app.customerize 1.0.1 * plone.app.form 1.0.4 * plone.app.kss 1.2.4 * plone.app.layout 1.0.4 * plone.app.linkintegrity 1.0.3 * plone.i18n 1.0.2 * plone.intelligenttext 1.0.1 by Wichert Akkerman — last modified December 10, 2007 - 11:51 The Plone

Carlos de la Guardia, consultor mexicano experto en Plone de visita en Chile,
nos muestra algunos portales en los que ha participado.  Todos ellos tienen no solo un look increíble, sino que se integran muy bien con otros productos, y lo mejor de todo es que están hechos en Plone.


1. CNN Expansión

Utiliza ampliamente XML y XSL.

2. Chilango

Utilizan los productos Composite Pack y Portletmania.

Está disponible una nueva versión de Plone

www.plone.org

Plone.org ha anunciado un problema de seguridad en las versiones 2.5 y 3.0.2.

This hotfix corrects a vulnerability in the statusmessages and linkintegrity modules, where unsafe network data was interpreted as python pickles. This allows an attacker to run arbitrary python code within the Zope/Plone process.

Más información y enlace al parche en:

http://plone.org/about/security/advisories/cve-2007-5741

Alexander Limi, a nombre del equipo de trabajo de Plone, ha anunciado cambios en la política de numeración de las próximas versiones de Plone.


Plone 3.1 ha sido anunciado para comienzos de 2008, para dar tiempo a la comunidad de estabilizar la reciente versión.

Las nuevas características se incorporarán en el proyecto Plone 4.0.  La fecha límite tentativa del proyecto es 1/Julio/2008.

Ya están abiertos los canales para hacer llegar las propuestas e ideas que serán parte de este proyecto.

Están disponibles quince presentaciones de la reciente PloneConference 2007, para descargar, en:

http://www.openplans.org/projects/plone-conference-2007/presentations

Esta tarde Patricio Pastor de la BCN, presentó en la Feria del Libro de Santiago el tema FLOSS (Software libre) para las bibliotecas.

Y Plone por cierto es parte de las soluciones.

Ver presentación (Slideshare)

Plone ha liberado hoy la versión 3.0.2.  Descárgala!!!!!

Estos son las mejoras:

Change log

• Give 'Modify portal content' permission to the Owner role by default. This allows sane use of workflow-less content types. Fixes http://dev.plone.org/plone/ticket/7180 [wichert]
• Modify form_tabbing.js to not touch the edit form if there's no fieldsets. [nouri]
• Set the media for ploneKss.css to screen so it can be merged with the other CSS files. [wichert]
• Add the language control panel when migration from previous Plone versions. [wichert]
• Fixed missing i18n markup in folder_constraintypes_form for portal types translation. This closes http://dev.plone.org/plone/ticket/7067. [hannosch, naro]
• Add migration to set the default GS profile when upgrading from 2.1. [alecm]
• Use a button/script combo for product reinstall from the control panel. http://dev.plone.org/plone/ticket/6457 [alecm]
• Remove silly root check from stripGRUFLocalRolePrefix script to fix migration bug. http://dev.plone.org/plone/ticket/5817 [alecm]
• Made Plone use 1/10th of the memory on file uploads. Details in http://dev.plone.org/plone/ticket/7027 (also backported to Plone 2.5.x) [zegor]
• Reverted addition of the GenericSetup import and export steps from PloneLanguageTool. [hannosch, wichert]

La iniciativa fue presentada en la reciente PloneConference.
 
El proyecto Plone4Universities tiene como misión el crear una comunidad universitaria en torno a Plone, fomentar su uso en instituciones universitarias, estrechar la colaboración y la visibilidad de los proyectos de desarrollo que realizan sus miembros y proporcionar una plataforma de comunicación entre estas intituciones.

El listado de universidades actuales sobrepasa las 20 instituciones.

Aunque en el listado no aparece alguna institución superior de nuestro país, algunos estudiantes de la UTFSM utilizan Plone. 


Más información en:

• http://www.plone4universities.org (Portal del proyecto)
• www.plone4universities.org/universities-using-plone  (Listado de universidades)

El blog "El Francotirador" publica un reportaje sobre el uso del software libre en el estado chileno.

Uno de los entrevistados es Christian Sifaqui, Jefe de sistemas de la BCN (Biblioteca del Congreso Nacional de Chile), quién describe como el administrador de contenidos Plone ha contribuído a darle valor a las actividades diarias de la organización.

Artículo disponible en: 

http://www.elfrancotirador.cl/2007/10/16/software-en-el-estado-licencia-para-pagar/

Siga de cerca las alternativas de la PloneConference 2007, que se realiza este año desde Italia.

Los eventos están siendo transmitidos en directo por internet TV, con un desfase de 6 horas.
http://ploneconf.comlounge.tv/

USStream
http://www.ustream.tv/search/all/plone%20conference%202007

También puede asistir virtualmente en Second Life.
https://secure-web0.secondlife.com/join/


Los videos de cada conferencia están en:
http://dev.comlounge.net/

Hay varios post en:
http://twitter.com/plone


La distancia ya no es una escusa.

http://plone.org/countries/conosur/noticias/lanzamiento-de-plone-3

Finalmente el equipo de documentación de Plone ha puesto a disposición de usuarios el manual de Plone 3.0
Bien por el trabajo en equipo.
Y bien por la reestructuación de la documentación en el sitio.

La Biblioteca del estado de IOWA, EEUU, utiliza Plone.

http://www.statelibraryofiowa.org/

Es interesante de analizar el uso integral de Plone.
Por ejemplo: la agenda destaca efectivamente eventos.

Y por cierto, el diseño visual no pasa por alto:  es limpio, ordenado, sobrio y moderno a la vez, por ejemplo con tabs y portlet redondeados.

No hay plazo que no se cumpla ni ........

Tal como lo prometió el team Plone, ya está disponible la nueva versión 3.0

La nueva versión corre sobre Zope 2.10 y Python 2.4.4.


Más información en  http://plone.org/products/plone/releases/3.0

Para descarga, disponible en:  http://plone.org/products/plone





Las principales mejoras son: (en inglés)

Feature enhancements in this release

The following features are associated with this release:

#118: Portlets engine based on PlonePortlets and Viewlets

Currently, the portlet mechanism in Plone is very crude. A proper structure to handle third-party portlets, individual caching policies and even asynchronous portlet updates is desirable.

#122: Edit-in-place mode for all basic field types

A lot of the time you just want to change a single attribute on an existing item. We want to enable an "advanced users" feature to make this quicker and more efficient.

#125: Ensuring link/reference integrity (removing 404 links)

One of Plone's weaknesses at the moment is the lack of resource tracking. If you delete a picture, and another document references this picture, you won't know before you look at the other document.

#127: Move properties to Edit screen using pre-loaded fieldsets

Clean up the UI a bit by moving the Properties to a grouped schemata on the edit screen.

#132: Return to Icon Flexibility

It is much more flexible to use the "getIcon" method to display icons via CSS in Plone than using the "portal_type". If the portal type is used, then there can only be a single icon for a content type, which makes it impossible to change the icon depending on what is contained in the content type. This is a proposal to get some of the flexibility back that was lost while going from Plone 2.0 to Plone 2.1.

#134: Reader and Editor roles

It is too difficult to share a private or restricted document with another person or group. By introducing Reader and Editor roles, the Sharing tab can be used to let any given user or group the right to read or edit any object.

#142: Componentise the global content menu

The global content menu, the green one with 'actions', 'add item' and 'state' drop-downs, is one beastly monolithic page template with a lot of logic. Worse, whilst it is possible to use actions to add new items to the 'actions' menu, if you want to add a new menu (e.g. for versioning or staging) you have to override the template wholesale. This proposal aims to change that by using views, adapters and utilities.

#144: Generalized Next / Previous navigation

There is a need for a feature that allows a user to navigate easily between content items stored in a container such as a folder.

#145: Locking

Prevent concurrent through-the-web editing in Plone. Trigger WebDAV locking on edit. Make it possible to borrow locks easily.

#146: Improve sharing page

The sharing page has to be simplified significantly.

#148: Move to CMF 2.1

Require CMF 2.1.

#149: Improved Markup Support

Creating a mechanism for adding support for additional markup languages such as Markdown and Textile for TextField fields and a site-wide policy for defining available and default formats.

#152: Dashboard

We want to create a page where the user can add portlets/widgets showing summaries with content of the portal. The idea is to provide an overview/summery over the content. The criteria which content and wich portlettype can be set/chosen by the user. The personal google page is a very good example.

#153: Portal type configlet in plone setup

Proposal for a configlet in Plone ui to control various settings related to portal types.

#157: Content rules engine

With the introduction of Zope 3 events, it becomes possible to react to events such as "object added" or "object modified". Plone should enable site administrators to set up rules that are invoked when these events occur under certain conditions. For example, it could be possible to move all Events added to a particular folder to the /events folder automatically.

#161: Remove migration code for old releases

Don't support migrating to Plone 3 from versions earlier then Plone 2.1.0-final.

#163: Minimize page weight

Plone as it is per Plone 2.5 is unnecessarily heavy when it comes to downloaded CSS, JS etc.

#168: integrate iterate for checkin/checkout/staging

builds on top of cmfeditions, to allow for explicit checkin/checkout and staging, without the overhead of site stages.

#171: Include KSS in Plone

KSS is an AJAX framework with Zope and Plone support. We propose inclusion of the framework core as part of Plone, together with the implementation of some UI improvements with Ajax.

#172: Wiki syntax support for all content

"wicked" provides usable wiki-like linking and content creation within AT based content. This proposal recommend the inclusion of this behavior as an option for Plone's content.

#173: OpenID support

Add support for the OpenID decentralized identify system to Plone

#174: More configurable and reusable i18n features

Move code for normalizing of ids out of CMFPlone and make it optionally configurable per language. Also consolidate all the three availablelanguage.py files currently found in AT, CMFPlone and PloneLanguageTool into an external package and hook these up using utilities instead.

#175: Expose more settings in the Control Panel

There are a lot of common settings that you still have to reach for the ZMI to adjust.

#176: New visual design for Plone

The existing Plone look is getting a bit long in the tooth — seeing as it essentially is the same as when it was conceived 5 years ago, it's time for an update.

#178: Return to using getIcon for content type icons

Aka. as "the un-PLIP", this proposal advocates changing back to the earlier approach used for content type icons in Plone.

#180: Add a RichText field to Smart Folders

Smart Folders would be much more flexible in real-world deployments if there was a RichText field before the results listing.

#26: Ship Plone with additional workflows and a workflow control panel

Plone currently ships with one workflow, we propose to ship it with four pre-defined workflows and a control panel that cover most of the use cases people normally have: Community, Intranet, Web Publishing and Extranets.

#8: Versioning

Plone needs to have a consistent, core solution for simple versioning tasks. This is expected of modern CMS packages. This PLIP outlines the needs and a proposed solution for versioning. Another PLIP will cover staging and multisite usage.

Plone.org ha recopilado y ordenado toda la documentación que dispone sobre Plone y sus productos, en un atractivo y simple portal.


Libros, manuales sobre Plone y sus productos, preguntas frecuentes, en fin...

Disponible en:  http://plone.org/documentation

Mientras esperamos con ansias la versión 3.0, ofrecida por el equipo de proyecto para el 21 de agosto de 2007, ya se pueden leer algunos requerimientos para incluir en la siguiente versión, la 3.5.

Las ideas propuestas para trabajar son:

• Removal of portal_memberdata
• Ship with better default member handling based on Membrane
  • Having something like Teamspace for project/team handling and project workspaces + delegated user management
• Replace the discussion architecture with Ploneboard and/or Listen
• Better media file handling (Video, audio) OOTB
• Expanded Document Management capabilities
• Improved BLOB support
• Using eggs for product packaging and dependencies
• Atom support in the core
  • Syncing between portals using Atom or RSS + something like MS' extensions to it
• Power User role
• Replacing the default theming approach with something similar to Deliverance
• Possibility to separate content production from content delivery? Entransit etc.
• Subscription to pages/containers (content subscription infrastructure)
• Composite Pages?
• Ship Plone with support for the most common auth setups (LDAP, Radius, NTLM, others?)
• Get a better export/import story
• Stream-based portal transforms replacement
• Improved email framework (incoming email handling)
• WebDAV improvements

Fuente (http://plone.org/products/plone/releases/3.5)

Ya está todo listo para la gran cumbre mundial de usuarios y desarrolladores de Plone, que este año 2007 se realizará en el Centro de Eventos de la "Ciudad de las Ciencias", ubicada en Napoles, Italia.

Y aunque las ceremonias se centrarán entre el 10 y 12 de octubre en torno a la Plone Conference, será una semana y media de actividades que se extenderá desde el 8 al 15 de octubre.

El programa contempla:

- Cursos:  días 8 y 9.
- Plone Conference:  días 10-11 y 12.
- Plone Sprint, para desarrolladores:  días 13-14 y 15.
- Una fiesta en la playa el 10 de octubre
- Una cena de gala el 11 de octubre

Se espera que este año la presencia sea cercana a 700 personas en la Plone Conference y de 300 para Plone Sprint (el recinto tiene capacidad para 1000).  Las inscripciones tienen un costo de 300 Euros.

Y si usted, como muchos de nosotros, no puede asistir, puede seguir el programa y la transmisión de las conferencias en vivo o bien a través de Youtube, tal como ocurrió el año pasado.

Vea los videos de la anterior Plone Conference 2006, realizada en Seatle, EE.UU.

La activa comunidad de Plone tiene sus bases en este equipo anónimo de personas.

¿Quienes están detras de Plone 3?

Acá están sus nombres:

http://plone.org/about/team/DeveloperTeam

El premio tiene, además, un estímulo en dinero equivalente a US$5.000 para contribuir con el desarrollo de los productos. 

Lea más información