Las caracteristicas de Plone¶

Advertencia

This chapter has not yet been updated for Plone 5!

In-depth user-manual: http://docs.plone.org/5/en

Iniciando y Deteniendo Plone¶

Tenemos el control de Plone con un pequeño script llamado “instance”:

$ ./bin/instance fg

This starts Plone in foreground mode so that we can see what it is doing by monitoring console messages. This is an important development method. Note that when Plone is started in foreground mode, it is also automatically in development mode. Development mode gives better feedback, but is much slower, particularly on Windows.

Usted puede detener el proceso presionando ctrl + c.

The instance script offers the following options, which you can call up at any time with ./bin/instance help:

$ ./bin/instance fg
$ ./bin/instance start
$ ./bin/instance stop
$ ./bin/instance -O Plone debug
$ ./bin/instance -O Plone run myscript.py
$ ./bin/instance adduser

Depending on your computer, it might take up to a minute until Zope will tell you that it’s ready to serve requests. On a decent laptop it should be running in under 15 seconds.

Una instalación estándar escucha en el puerto 8080, así que vamos a echar un vistazo a nuestro sitio Zope visitando http://localhost:8080

¡Como puede ver, no hay Plone todavía!

We have a running Zope with a database but no content. But luckily there is a button to create a Plone site. Click on that button (login: admin, password:admin). This opens a form to create a Plone site. Use Plone as the site id.

Usted será automáticamente redirigido al sitio nuevo.

Nota

Plone tiene muchos mensajes. Contienen información importante. ¡Léalos y asegúrese de entender su contenido!

Tutorial de la interfaz de usuario¶

Vamos a ver lo que está ahí...

header:
- logo: con un enlace a la pagina principal
- searchbox: search (with live-search)
navigation: The global navigation
banner: A banner. Only visible on the frontpage.
portal-columns: un contenedor que contienen:
- portal-column-one: portlets (configurable boxes with tools like navigation, news etc.)
- portal-column-content: el contenido y el editor
- portal-column-two: portlets
portal-footer: portlets for the footer, site actions, and colophon
edit-zone: a vertical bar on the left side of the browser window with editing options for the content

These are also the css classes of the respective divs. If you want to do theming you’ll need them.

On the edit bar, we find options affecting the current context...

folder contents
view
edit
rules
sharing
status
add
more options
content info
user actions

Some edit bar options only show when appropriate; for example, folder contents and add are only shown for Folders. rules is currently invisible because we have no content rules available.

Usuarios¶

Let’s create our first users within Plone. So far we used the admin user (admin:admin) configured in the buildout. This user is often called “zope root” and is not managed in Plone but only by Zope. Therefore the user’s missing some features like email and fullname and won’t be able to use some of plone’s features. But the user has all possible permissions. As with the root user of a server, it’s a bad practice to make unnecessary use of zope root. Use it to create Plone sites and their initial users, but not much else.

You can also add zope users via the terminal by entering:

$ ./bin/instance adduser <someusername> <supersecretpassword>

That way you can access databases you get from customers where you have no Plone user.

To add a new user in Plone, click on the user icon at the bottom of the left vertical bar and then on Site setup. This is Plone’s control panel. You can also access it by browsing to http://localhost:8080/Plone/@@overview-controlpanel

Click on Users and Groups and add a user. If had configured a mail server, Plone could send you a mail with a link to a form where you can choose a password. We set a password here because we haven’t yet configured a mail server.

Estableciendo a este usuario con su nombre un Administrador del sitio.

Then create another user called testuser. Make this one a normal user. You can use this user to see how Plone looks and behaves to users that have no admin permissions.

Now let’s see the site in 3 different browsers with three different roles:

como anónimo.

como editor.

como administrador.

Configurar un servidor de Correo¶

We have to configure a mailserver since later we will create some content rules that send emails when new content is put on our site.

Servidor: mail.gocept.net
Nombre de usuario: training@neww.de
Password: training2015

Por favor, no abuses de esto. Vamos a deshabilitar esta cuenta después de la capacitación.

Tipos de Contenidos¶

Editar una pagina:

Edite el documento front-page
Title Plone Conference 2015, Bucharest
Descripción Tutorial
Texto ...

Crear un estructura del sitio:

Agregar carpeta “El Evento” y que contenga...
- Carpeta “Charlas”
- Carpeta “Entrenamientos”
- Carpeta “Sprint”
En la ruta /news: Agregar una Noticia “¡Sitio Web de la Conferencia esta en linea!” con una imagen
En la ruta /news: Agregar una Noticia “¡Enviar sus Charlas!”
In /events: Add Event “Deadline for talk-submission” Date: 2015/08/10
Agregar Carpeta “Registro”
Delete Folder “Members” (Users)
Agregar Carpeta “Intranet”

Los tipos de contenidos por defecto:

Documento
Noticia
Evento
Archivo
Imagen
Enlace
Carpeta
Colección

Nota

Please keep in mind that we use plone.app.contenttypes for the training. Therefore the types are based on Dexterity and slightly different from the types that you will find in a default Plone 4.3.x site.

Carpetas¶

Ir a ‘el-evento’
explicar title/id/url
explicar /folder_contents
cambiar orden
acciones en masa
desplegable “Mostrar”
default_pages
Add a page to ‘the-event’: “The Event” and make it the default page
El futuro: wildcard.foldercontents

Colecciones¶

add a new collection: “all content that has pending as wf_state”.
explicar la colección por defecto de eventos en http://localhost:8080/Plone/events/aggregator/edit
explicar Topicos
mention collection portlets
multi-path queries
constraints, e.g. /Plone/folder::1

Reglas de Contenido¶

¡Crear una nueva regla “una nueva charla está presente”!
Nuevo contenido en Carpeta “Charlas” -> Enviar correo a revisores.

Histórico¶

Show and explain; mention versioning and its relation to types.

Administrar usuarios y grupos¶

agregar / editar / eliminar Usuarios
roles
grupos
- Agregar grupo “Editores” y agregar el usuario ‘editor’ a este
- Agregar grupo: orga
- agregar grupo: jury y agregue usuario ‘jurymember’ a este.

Flujos de trabajos¶

Take a look at the state drop-down on the edit bar on the homepage. Now, navigate to one of the folders just added. The homepage has the status published and the new content is private.

Let’s look at the state transitions available for each type. We can make a published item private and a private item published. We can also submit an item for review.

Each of these states connects roles to permissions.

In published state, the content is available to anonymous visitors;
In private state, the content is only viewable by the author (owner) and users who have the can view role for the content.

A workflow state is an association between a role and one or more permissions. Moving from one state to another is a transition. Transitions (like submit for review) may have actions — like the execution of a content rule or script — associated with them.

A complete set of workflow states and transitions make up a workflow. Plone allows you to select among several pre-configured workflows that are appropriate for different types of sites. Individual content types may have their own workflow. Or, and this is particularly interesting, no workflow. In that case, which initially applies to file and image uploads, the content object inherits the workflow of its container.

Nota

An oddity in the all of the standard Plone workflows: a content item may be viewable even if its container is not. Making a container private does not automatically make its contents private.

Lea mas en: http://docs.plone.org/working-with-content/collaboration-and-workflow/index.html

Copia de trabajo¶

Published content, even in an intranet setting, can pose a special problem for editing. It may need to be reviewed before changes are made available. In fact, the original author may not even have permission to change the document without review. Or, you may need to make a partial edit. In either case, it may be undesirable for changes to be immediately visible.

Plone’s working copy support solves this problem by adding a check-out/check-in function for content — available on the actions menu. A content item may be checked out, worked on, then checked back in. Or abandoned if the changes weren’t acceptable. Not until check in is the content visible.

While it’s shipped with Plone, working copy support is not a common need. So, if you need it, you need to activate it via the add-on packages configuration page. Unless activated, check-in/check-out options are not visible.

Nota

Working-copy support is not yet available for content types created via Dexterity. This is on the way.

Flujos de trabajo Placeful¶

You may need to have different workflows in different parts of a site. For example, we created an intranet folder. Since this is intended for use by our conference organizers — but not the public — the simple workflow we wish to use for the rest of the site will not be desirable.

Plone’s Workflow Policy Support package gives you the ability to set different workflows in different sections of a site. Typically, you use it to set a special workflow in a folder that will govern everything under that folder. Since it has effect in a “place” in a site, this mechanism is often called “Placeful Workflow”.

As with working-copy support, Placeful Workflow ships with Plone but needs to be activated via the add-on configuration page. Once it’s added, a Policy option will appear on the state menu to allow setting a placeful workflow policy.

Nota

Workflow Policy support is not yet available for folderish content types created via Dexterity. This is on the way.