Monday 08 September 2003 7:21:08 am

You might use a {switch / case} statement where you check which class your related object is an instance of.

I'm not able to do a test on this right now, but at least it's an idea...

Regards Bjørn

Tuesday 09 September 2003 1:03:03 am

Can you give an example of what goes wrong with the 'div'? A switch, case statement should work here, but i'd like to see what you are doing.

Paul

Wednesday 10 September 2003 12:26:44 am

Cant you put the <div> into the section show results?

{section show=...}
<div>
blah
</div>
{section-else}
something else...
{/section}

paul

Wednesday 10 September 2003 1:43:05 am

Try this out. Basically you need to test when there are rel objects and handle it accordingly.

This code isn't tested so ii may have a few typos in there.... Good luck.

{section show=count($node.object.related_contentobject_array)|gt(0)}
<div class="related">
<ul>

{section name=Rel loop=$node.object.related_contentobject_array}

{switch name=RelClass match=$Rel:item.contentclass_id}

{case match=1}
Folder stuff
<li><a href={concat("/content/view/full/",$:item.main_node.node_id)|ezurl}>{$:item.name}</a></li>
{/case}

{case match=2}
Article stuff
Etc
{/case}

{case match=14}
Whatever
{/case}

{/switch}

{/section}

</ul>
</div>
{section-else}
Do something when there no rel objects.
{/section}

Wednesday 10 September 2003 5:16:48 am

I've had the same problem several times. From the users point of view a related image is usually something very different from a related page, or a related downloadable file, and more often than not you want to display these items in different places in the templates, not just grouped together as one big bunch of items.

Some functions to ease the handling of relations of a specific class would be greatly appreciated.

I can think of a few things:

1. Fetch related objects of a specific class

2. Check if objects of a specific class exists

3. Group different related class types in the admin interface. Related images under one heading, related documents in another heading, etc...

4. Allow sorting of the different related objects in the admin interface, and use the sorting method when displaying the objects in the templates.

Some of this may be solved by using object relation lists for specific classes in 3.2, but that function didn't work in the 3.2 beta2 I tested, so I don't know specifically how it would work yet...

Daniel Staver
http://daniel.staver.no

Monday 14 March 2005 2:46:38 am

Old topic, but anyway for you who stumbled over this..(like i did)
#FIX
{case match=1}
Folder stuff
<li><a href={concat("/content/view/full/",$:item.main_node.node_id)|ezurl}>{$:item.name}</a></li>
{/case}

#SHOULD BE:
Folder stuff
<li><a href={concat("/content/view/full/",$Rel:item.main_node.node_id)|ezurl}>{$Rel:item.name}</a></li>
{/case}