I was expecting something already cooked and ready to eat. Thank you.
I think this is a very useful function because developers often want to
export only some nodes to make local tests in a developing environment.

Thank you again.

Andrea


2010/3/11 Jan Haderka <[email protected]>

>
> What to include (and what not) in the export is governed by the rule
> used in the export. By changing the rule you will filter out the nodes
> you don't want. If you look through the Syndicator code you should be
> able to find the rule used by activation.
>
> HTH,
> Jan
>
>
> On Thu, 2010-03-11 at 10:21 +0100, Andrea Castelli wrote:
> > Hi everybody,
> > I'm writing  a command to export magnolia data to another system. I
> > need to an export command that can export a single node with Metadata
> > (the same as the function "activate this node"). I found an export
> > command (very easy and simple) but there is only the function to
> > export data with all subnodes . Setting export data "not recursive"
> > exports only the requested node (not Metadata and mgnl:contentNode).
> >
> > The other way is to override the function "activate this node" but it
> > is very tricky.
> >
> > Is there a function "export this node"?
> > How can I proceed to develop it? (I'm copying and rewriting the code
> > of "activate this node")
> >
> > Any other advices?
> >
> > Thank you.
> > Andrea
>
>
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <[email protected]>
> ----------------------------------------------------------------
>
>

----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to