Module Integration in Content Tree/Navigation: Best practice?
Module Integration in Content Tree/Navigation: Best practice?
Tuesday 07 February 2012 12:04:20 pm
Hi eZExperts,
I wonder what would be the best practice for the integration of a module with views in the navigation. I found some hints here in the forum, may be a good answer could find it's way in the tutorial?
So far I have seen:
-
Use the redirect operator:
http://share.ez.no/forums/extensions/how-to-link-to-my-custom-module
(Along with some tips for $Result['path'] and node_id on ezpedia, which are rather poorly documented)
-
"create a custom operator or a custom fetch to get the output of your custom module"
fetch('module','module_name','view')
(same thread, I found no docs on this)
- "Instead of publishing them as content objects, you can set up virtual urls to have them "appear" where you want to. A little bit more counterintuitive maybe, but it should be enough for most needs.", same thread, found no docs on this either...
Short: is there an "official" way to integrate a module and its output in the rest of the managed content?
Regards,
frank