collective.portaltabs 0.4.0

Manage site's portal tabs from Plone interface in a simple way

Table of contents

• Introduction

  • When you need this

  • When you don’t need this

• How to use

  • First note

  • Handling tabs

  • What I can write inside an URL section?

  • Manage additional actions categories

• Upload directly an “actions.xml” file

  • Plone is an helephant, remember all

• TODO

• Bug report and feature request

• Credits

• Authors

• Changelog

  • 0.4.0 (2014-07-25)

  • 0.3.0 (2013-01-15)

  • 0.2.0 (2011-05-19)

  • 0.1.0a (2010-12-15)

Introduction

Add to Plone a way to manage site portal tabs using the Plone interface and hiding common syntax difficulties you can find in ZMI.

When you need this

You need this product when you want to give to your non-technical users the ability to manage the portal tabs section of your Plone site.

Going deeply:

• you don’t want (or you can’t) that your power user will need to go to ZMI (for example, the Plone 4.1 “Site Administrator” role can’t)

• you still want to make them able to manage portal tabs

• your users don’t know nothing about TAL and python, and commonly want only to add static links to the site

• your additional tabs don’t need advanced features like condition for being seen, or permissions (for this, you can still go to ZMI)

When you don’t need this

If you only need to port into Plone interface the “portal_action” tool customizationthis is not your product. Try to check quintagroup.plonetabs instead.

How to use

First note

This product only manage portal tabs that are not automatically generated from Plone. For this reason, a warning message is displayed if the “Automatically generate tabs” option is selected in the “Navigation settings” panel.

Handling tabs

From the “Site Setup” panel, go to the new “Manage portal tabs” link you’ll find after the product installation.

The “Portal Tabs settings” view is composed by two section; the first one for make changes to existing tabs (and also order and delete them), and the second for adding new tabs.

Newly created tab only need two kind of information: the name of the tab to be displayed (title) and the URL. When creating a tab you can also handle the id of the tab, or this will be automatically generated.

What I can write inside an URL section?

The product try to hide some of the too-technical feature you have available in the ZMI portal_actions tool management, however all features are still there.

• to create an absolute link to something, just type the link (e.g: “http://foo.org”)

• when you need to create links to URL inside the site, just type “/folder/foo” (note that this path can be a content path, but no check are done at all)

• TAL espression are still available, but you need to start them with a “tal:”

• Python expression are still available, but you need to start them with a “python:”

• inside an URL, you can still use TALES expressions in the normal form “${foo1/foo2/...}”

For security reason, usage on “python:”, “tal:” and in-string TALES with “$” are protected by another permissions “collective.portaltabs: Use advanced expressions”, given only to Manager role.

Manage additional actions categories

You can use collective.portaltabs to handle also other CMF action categorie than “portal_tabs”. To do this you need to configure what other categories can be handled accessing the “@@manage-portaltabs-categories” settings page.

All entries must match a CMF action category that exists. Going back to the “Portal Tabs settings” make possible to handle also those new actions

Upload directly an “actions.xml” file

If you have defined your own portal tabs using a Generic Setup profile, you can upload your actions.xml (or compatible file) file directly in the manage form.

Plone is an helephant, remember all

Please, remember that if you used an actions.xml in one of your product, Plone will remember all action you have loaded, and changes done manually later will be reverted if you reinstall the product.

To make Plone stopping remember about those actions, you need to:

• uninstall your product that added the actions

• remove the products from the portal_quickinstaller (“Contents” tab)

• remove the actions.xml file from your product

• install again

TODO

• More tests

• Provide some AJAX fancy features for selecting portal contents

Bug report and feature request

Please, go to the product’s issue tracker.

Credits

Developed with the support of:

• S. Anna Hospital, Ferrara

  

• Azienda USL Ferrara

  

• University of Padova - Department of Management and Engineering

All of them supports the PloneGov initiative.

Authors

This product was developed by RedTurtle Technology team.

Changelog

0.4.0 (2014-07-25)

• Restored controlpanel icons no more delivered by Plone 4.3 [keul]

• Fixed link to navigation controlpanel [keul]

• Added option for visibility condition of the action [keul]

0.3.0 (2013-01-15)

• updated to Plone 4.1+ security and new “Site Administrator” role [keul]

• support for query expression starting with /, that generate links to internal section of the site [keul]

• tabs settings panel is now protected with a specific permission [keul]

• protected the use of tal:, python: and $ with a proper permission [keul]

• removed the usage of CMF properties. General configuration migrated to Plone registry [keul]

• Added tests [keul]

0.2.0 (2011-05-19)

• added input validations [keul]

• more help texts and translations [keul]

• added a direct link to the ZMI manage section [keul]

• added a way to upload Generic Setup compatible actions.xml file, to automatically load actions [marco.mariani]

0.1.0a (2010-12-15)

• initial release