Hi Again,

Apologies if this is something of a newbie question (I've only been working with Magnolia / JCR for around a week now) but I'm having some difficulty navigating the content tree in a "Groovy" way in order to update the form module to be i18n.

I can get at content nodes by name very easily:

root = hm.getContent("/modules/form/dialogs")
c = root.getContent('formEdit/tabMain/title')
c.setNodeData('i18n', true)
c.save()

And that all works

However I can't seem to find any way to iterate through the available content or nodes - root.getChildren() simply returns null

Does anyone know a better way to do this?

Thanks!

Corin

On 10/22/2010 03:50 PM, Grégory Joseph wrote:
Hi Corin,

Yeah that's a good start to get thing going and validate the approach, paths, 
etc. The end-result will need to be in the form of update tasks, so that the 
module can be updated on existing instance, but a script sure would help 
anyway; it should be fairly straightforward to rewrite it as a task.

Cheers,

-g

On Oct 22, 2010, at 15:48, Corin Moss wrote:

Hi Grég,

That seems reasonably straight forward.

By the looks of it if I write a quick script to define i18n = true for all 
nodes where controlType==edit under the form module it should be pretty much 
covered.  I'll most likely run it up as a Groovy script, and post it to jira as 
requested.

Can you see any problems with that approach?

Regards,

Corin




On 10/22/2010 02:58 PM, Grégory Joseph wrote:
Hi Corin,

That's correct, the form module's dialogs are currently still missing i18n support; 
essentially, relevant controls of each dialog would need an "i18n" property set 
to true to fix this.

Best way to go at it would be to write update tasks to add those properties, 
and update the bootstrap files. If that's enough info to get you started, go 
ahead and file an issue at http://jira.magnolia-cms.com/browse/MGNLFORM .. 
patches would be great! ;)

We'll try to update 
http://documentation.magnolia-cms.com/technical-guide/i18n.html shortly in that 
regard. In the meantime, these blog entries might help get you started:
   
http://philipp-baerfuss-magnolia.blogspot.com/2010/01/i18n-support-in-dialogs-magnolia-43.html
   
http://philipp-baerfuss-magnolia.blogspot.com/2010/02/i18n-authoring-support-on-stage.html

.. and if not, shoot back ! ;)

Cheers,

-greg

On Oct 22, 2010, at 14:42, Corin Moss wrote:


Hi everyone,

We've been working quite successfuly with the i18n features of Magnolia for 
standard content, and we're now looking at how to use it in conjunction with 
some of the modules.  Case in point at the moment is the form module.  It 
appears that this module doesn't yet support i18n for the generated form 
elements - is this correct, or are we missing something?

If it indeed doesn't support i18n, we'd be interested in providing that 
support.  Where should one look for a best practice example?

Many thanks,

Corin



----------------------------------------------------------------
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]>
----------------------------------------------------------------



--
Mit freundlichen Grüßen / With Kind Regards,


Corin Moss
Director - Technology Development

Infomoss Consulting
It's possible now.
www.infomoss.com



----------------------------------------------------------------
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]>
----------------------------------------------------------------



--
Mit freundlichen Grüßen / With Kind Regards,


Corin Moss
Director - Technology Development

Infomoss Consulting
It's possible now.
www.infomoss.com



----------------------------------------------------------------
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