[#MMB-1052] mm:list gives strange result with nodes of different types - MMBase

Details

Type: Bug
Status: Resolved
Priority: Major
Resolution: Won't Fix
Affects Version/s: 1.7.0
Fix Version/s: Irrelevant
Component/s: Taglib

Description:

Hide
original bugid: #6626
In the database:

cma1 - posrel -> nl1
cma2 - posrel -> nl2
cma3 - posrel -> nl3

cma1, cma2, cma3 are aliases for cmas
nl1, nl2, nl3 are aliases for newsletters

When i use:
<mm:list nodes="cma1,cma2,nl3" path="cmas,posrel,newletters" />

The result is:
cma1 - posrel -> nl1
cma2 - posrel -> nl2

But if i use:
<mm:list nodes="nl3" path="cmas,posrel,newletters" />

The result is:
cma3 - posrel -> nl3

I did not check in 1.7.1.

Bug or feature?

Show
original bugid: #6626 In the database: cma1 - posrel -> nl1 cma2 - posrel -> nl2 cma3 - posrel -> nl3 cma1, cma2, cma3 are aliases for cmas nl1, nl2, nl3 are aliases for newsletters When i use: <mm:list nodes="cma1,cma2,nl3" path="cmas,posrel,newletters" /> The result is: cma1 - posrel -> nl1 cma2 - posrel -> nl2 But if i use: <mm:list nodes="nl3" path="cmas,posrel,newletters" /> The result is: cma3 - posrel -> nl3 I did not check in 1.7.1. Bug or feature?

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

Michiel Meeuwissen added a comment - 1970-01-01 00:59

I think this is a known issue. I'm not quite sure if is shoudl be considered a bug or a feature. The general rule is that the nodes attribute works only on one of the steps of the path.

I'm not sure if that is logical though (It seems not).

As a work-around, you can probbably use listcontainer.
<mm:listcontainer path="a,b,c">
<mm:constraint field="a.number" value="<aliasofa>" />
  <mm:constraint field="b.number" value="<aliasofb>" />
  <mm:list>
     ....

Show

Michiel Meeuwissen added a comment - 1970-01-01 00:59 I think this is a known issue. I'm not quite sure if is shoudl be considered a bug or a feature. The general rule is that the nodes attribute works only on one of the steps of the path. I'm not sure if that is logical though (It seems not). As a work-around, you can probbably use listcontainer. <mm:listcontainer path="a,b,c"> <mm:constraint field="a.number" value="<aliasofa>" /> <mm:constraint field="b.number" value="<aliasofb>" /> <mm:list> ....

Hide

Permalink

Michiel Meeuwissen added a comment - 2007-02-02 20:41

I'd suggest to reject it for 1.9, If at least someone else agrees.

Show

Michiel Meeuwissen added a comment - 2007-02-02 20:41 I'd suggest to reject it for 1.9, If at least someone else agrees.

People

Assignee:

MMBase Project Leader

Reporter:

Nikolay Bukharev
Votes:

0

Watchers:

0

Dates

Created:

2004-11-16 10:58

Updated:

2009-07-31 17:50

Resolved:

2009-07-31 16:25