Ticket #1893 (closed enhancement: fixed)

Opened 1 year ago

Last modified 5 months ago

Portlets should have user-friendly IDs

Reported by: madarche Assigned to: jmorliaguet
Priority: P1 Milestone: CPS 3.4.7
Component: CPSPortlets Version: TRUNK
Severity: normal Keywords:
Cc:

Description (Last modified by madarche)

When a portlet is created it has an ID like "portlet_425210414". This is not user-friendly and makes it really hard to find a specific portlet in the ZMI and in a GenericSetup? XML export.

The portlets IDs should be based on the name provided by the user when they are created, just like any other CPS documents.

Note that after this problem is fixed, already created portlets will still have their unfriendly IDs. Only newly created portlets will benefit from the fix.

Change History

02/25/08 01:40:33 changed by gracinet

+1, but beware that some html ids are based on this zope id.

03/12/08 11:23:21 changed by madarche

  • description changed.

04/24/08 11:39:20 changed by madarche

  • priority changed from P2 to P1.

09/04/08 12:14:52 changed by madarche

  • status changed from new to closed.
  • resolution set to fixed.

Fixed by changeset [52971].

09/04/08 12:19:29 changed by madarche

This improvement only affects the ID of the portlet at its creation. If one changes the title of the portlet once it is created, the ID will remain the same.

01/23/09 10:18:24 changed by jmorliaguet

  • status changed from closed to reopened.
  • resolution deleted.

You forget to set the internal portlet 'identifier' which means that not two portlets of the same type can be created.

patch follows.

01/23/09 11:16:54 changed by gracinet

Jean-Marc, can you explain in a few words what this global identifier is been used for ?

01/23/09 11:22:18 changed by madarche

  • status changed from reopened to closed.
  • resolution set to fixed.

The changeset is [53365].

The portlet identifier must be unique among all portlets, it is not the same thing as the portlet's zope id in a portlet container.

01/23/09 11:29:04 changed by madarche

Changeset [53367] backports the fix on the CPS-3.4 branch.

02/04/09 11:14:40 changed by madarche

Explanation from Jean-Marc:

it is used to identify portlets uniquely no matter which container they are located in, for instance when you do copy and paste between containers, unique ids per container are not enough.

the id is similar to the document id in portal_repository except that it is stored in the portlet's catalog

portlets are also documents so they need a zope id (which is more cosmetic than anything else)