Bug 794365 (JBEPP-1409) - Sort contents in CLV using a custom field of a node
Summary: Sort contents in CLV using a custom field of a node
Keywords:
Status: NEW
Alias: JBEPP-1409
Product: JBoss Enterprise Portal Platform 5
Classification: JBoss
Component: Site Publisher
Version: 5.1.1.GA
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL: http://jira.jboss.org/jira/browse/JBE...
Whiteboard: EPPSP_6_0_0_Candidate SitePublisher
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-28 13:42 UTC by William Antônio
Modified: 2020-04-27 01:31 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Feature Request

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEPP-1409 0 Major Closed Sort contents in CLV using a custom field of a node 2012-08-09 18:48:33 UTC

Description William Antônio 2011-11-28 13:42:23 UTC 
Complexity: Medium
Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A0000008yCMIIA2&sfdc.override=1
project_key: JBEPP

We have a custom nodetype and when showing content of the type of this nodetype in the CLV portlet we would like to order the results using a customized field. For example, we have the following node:

com:myField1
com:myField2

We would like to order the results in CLV using one of these custom fields.

The same situation is described in this post:

http://community.exoplatform.org/portal/public/classic/forum/topic/topic2153ffa47f00000101df9641c95264e6
Comment 2 Martin Weiler 2011-11-28 14:31:53 UTC 
This request is related to https://jira.exoplatform.org/browse/ECMS-3068.
Comment 3 Thomas Heute 2011-12-15 10:27:25 UTC 
Labels: Added: EPPSP_6_0_0_Candidate
Comment 4 hfnukal@redhat.com 2012-01-10 13:22:23 UTC 
Labels: Removed: EPPSP_6_0_0_Candidate Added: EPPSP_6_0_0_Candidate SitePublisher
Note You need to log in before you can comment on or make changes to this bug.