Monday 29 October 2007 1:27:20 am

Hi,

In templates in content/collectedinfomail/*.tpl you can use:

{* redirect to another node *}
{set-block scope=root variable=redirect_to_node_id}2{/set-block}

Personal website -> http://serwatka.net
Blog (about eZ Publish) -> http://serwatka.net/blog

Monday 29 October 2007 2:25:43 am

Thanks Łukasz,

I'll just document this for anyone else who might need it... [EZ 3.10.0]

A custom (or existing) class that acts as an information collector has several redirect possibilities:

<b>1.</b> Displaying a "result" template (eg poll result), typically located in <i>[Design-Extension]/templates/content/collectedinfo/</i>

<b>2.</b> "Redirect" to a specific URL (for all objects of that class)

<b>3.</b> Redirect back to the content node ("Node") method.

Setting up information collection for a custom class involves creating settings for it in (eg) <i>settings/override/collect.ini.append.php</i>. Information about settings can be seen in <i>settings/collect.ini</i>

My question was about getting something like option 2 (above) to go to a dynamic URL, as I set in a template file. Lucasz's suggestion is to use option 1 and then create a redirect in the template loaded by that option.

So, collect.ini.append.php (eg, other options left out)

[InfoSettings]
TypeList[my_infocollector_class]=my_infocollector_class
[DisplaySettings]
DisplayList[my_infocollector_class]=result

And, in <i>[Design-Extension]/templates/content/collectedinfo/my_infocollector_class.tpl</i>

{* redirect to another node *}
{set-block scope=root variable=redirect_to_node_id}2{/set-block}

This then opens up opportunities for setting a variable redirect, perhaps using
- relative location (eg parent)
- last visited node
- value from template
- Get/Post value

@Heath .. yes, there seem to be some similar features to login redirection - ie RedirectURLAttribute, though I haven't experimented with this and there seems to be no documentation yet.

Thanks to you both. Hope this helps others.

Monday 29 October 2007 4:26:09 am

Hi Heath,

I'm writing some documentation for EZ to publish for the EZ community at the moment, I'll aim to get some more material on to Ezpedia over coming months ... just getting out a little bit on-the-fly here. Just wanting to tackle a disadvantage of EZ forums ... it's often possible to find forum entries that are relevant but the why and what happened information is often missing. I suspect it would be useful for forum topics to be closed/resolved in the same way that issues are on issues.ez.no. (In effect "issues" are problems with EZ publish; "forum topics" are usually problems people are experiencing using EZ publish to achieve the results they want).

Anyway, I've been doing a lot of work in the areas of complex systems + information / knowledge architectures ... I'm interested in designing an overall architecture for the EZ ecosystem at some stage. I'll have a look at ways to better incorporate my existing and new documentation into EZ/EZpedia as part of this work soon.

Regards from Tasmania, Australia.

- Paul

Monday 29 October 2007 6:08:48 am

Hi Paul,

Have you considered warp this information in to one document and publish as article on ez.no about information collection (e.g useful tips)?

http://ez.no/developer/articles/writing_articles_for_ez_no

Personal website -> http://serwatka.net
Blog (about eZ Publish) -> http://serwatka.net/blog