9. Configuring and Customizing Plone “Through The Web”

Warning

This chapter has not yet been updated for Plone 5!

9.1. The Control Panel

The most important parts of Plone can be configured in the control panel.

  • Click on the portrait/username in the toolbar
  • Click Site Setup

We’ll explain every page and mention some of the actions you can perform here.

9.1.1. General

  1. Date and Time
  2. Language
  3. Mail
  4. Navigation
  5. Site
  6. Add-ons
  7. Search
  8. Discussion
  9. Theming
  10. Social Media
  11. Syndication
  12. TinyMCE

9.1.2. Content

  1. Content Rules
  2. Editing
  3. Image Handling
  4. Markup
  5. Content Settings
  6. Dexterity Content Types

9.1.3. Users

  1. Users and Groups

9.1.4. Security

  1. HTML Filtering
  2. Security
  3. Errors

9.1.5. Advanced

  1. Maintenance
  2. Management Interface
  3. Caching
  4. Configuration Registry
  5. Resource Registries

Below the links you will find information on your Plone, Zope and Python Versions and an indicator as to whether you’re running in production or development mode.

9.2. Portlets

In the toolbar under More options you can open the configuration for the different places where you can have portlets.

  • UI fit for smart content editors
  • Various types
  • Portlet configuration is inherited
  • Managing
  • Ordering/weighting
  • The future: may be replaced by tiles
  • @@manage-portlets

Example:

  • Go to http://localhost:8080/Plone/@@manage-portlets
  • Add a static portlet “Sponsors” on the right side.
  • Remove the news portlet and add a new one on the left side.
  • Go to the training folder: http://localhost:8080/Plone/the-event/training and click Manage portlets
  • Add a static portlet. “Featured training: Become a Plone-Rockstar at Mastering Plone!”
  • Use the toolbar to configure the portlets of the footer:
    • Hide the portlets “Footer” and “Colophon”.
    • Add a Static text portlet and enter “Copyright 2015 by Plone Community”.
    • Use Insert ‣ Special Character to add a real © sign.
    • You could turn that into a link to a copyright page later.

9.3. Viewlets

Portlets save data, Viewlets usually don’t. Viewlets are often used for UI-Elements and have no nice UI to customize them.

  • @@manage-viewlets
  • Viewlets have no nice UI
  • Not aimed at content editors
  • Not locally addable, no configurable inheritance.
  • Usually global (depends on code)
  • Will be replaced by tiles?
  • The code is much simpler (we’ll create one tomorrow).
  • Live in viewlet managers, can be nested (by adding a viewlet that contains a viewlet manager).
  • TTW reordering only within the same viewlet manager.
  • The code decides when it is shown and what it shows.

9.4. ZMI (Zope Management Interface)

Go to http://localhost:8080/Plone/manage

Zope is the foundation of Plone. Here you can access the inner workings of Zope and Plone alike.

Note

Here you can easily break your site so you should know what you are doing!

We only cover three parts of customization in the ZMI now. Later on when we added our own code we’ll come back to the ZMI and will look for it.

At some point you’ll have to learn what all those objects are about. But not today.

9.4.1. Actions (portal_actions)

  • Actions are mostly links. But really flexible links.
  • Actions are configurable TTW (Through-The-Web) and through code.
  • These actions are usually iterated over in viewlets and displayed.

Examples:

  • Links in the Footer (site_actions)
  • Actions Dropdown (folder_buttons)

Actions have properties like:

  • description
  • url
  • i18n-domain
  • condition
  • permissions

9.4.1.1. site_actions

These are the links at the bottom of the page:

  • Site Map
  • Accessibility
  • Contact
  • Site Setup

We want a new link to legal information, called “Imprint”.

  • Go to site_actions (we know that because we checked in @@manage-viewlets)
  • Add a CMF Action imprint
  • Set URL to string:${portal_url}/imprint
  • Leave condition empty
  • Set permission to View
  • Save

explain

  • Check if the link is on the page
  • Create new Document “Imprint” and publish

9.4.2. Skins (portal_skins)

In portal_skins we can change certain images, CSS-files and templates.

  • portal_skins is deprecated technology
  • Plone 5 got rid of most files that lived in portal_skins.

9.4.2.1. Change some CSS

  • Go to ZMI
  • Go to portal_skins
  • Go to plone_styles
  • Go to ploneCustom.css
  • Click customize

The CSS you add to this file is instantly active on the site.

9.4.3. portal_view_customizations

9.4.4. CSS Registry (portal_css)

deprecated (See the chapter on theming)

9.4.5. Further tools in the ZMI

There are many more notable items in the ZMI. We’ll visit some of them later.

  • acl_users
  • error_log
  • portal_properties (deprecated)
  • portal_setup
  • portal_workflow
  • portal_catalog

9.5. Summary

You can configure and customize a lot in Plone through the web. The most important options are accessible in the Plone control panel but some are hidden away in the ZMI. The amount and presentation of information is overwhelming but you’ll get the hang of it through a lot of practice.