Thanks Ralf, you're a star!

And cheers Oliver, looks an interesting possibility to have multiple
values for a property.

-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] 
Sent: 21 February 2008 17:18
To: [email protected]
Subject: Re: [magnolia-user] How to specify names of dataNodes with
controls

Hi Chris,

maybe it is easier if you use XPATH. The query then looks like

//topic[jcr:contains(., 'issue')]

asuming that you name the Control "topic" and "issue" is the value you 
are looking for.

Ralf

Allan, CJ (Chris) schrieb:
> Hi Ralf,
>
> Oh yeah ... kinda forget that ... a bit stupid.
>
> What I want to do is an extension of the 'topic' idea, and the 'search
> by topic' paragraph in enterprise edition. I would like to be able to
> have multiple topics for any paragraph. Currently you can have 'issue'
> and 'issueCustom'.
>
> If you change the issue control from 'radio' to 'checkbox' for example
> then you get, for example, in the JCR:
>
>       Issue
>         0             option1 String
>         1             option3 String
>         2             option6 String
>
> But if you want to execute a statement looking for the options you
> selected, the nodes now have the name '0', '1', '2' etc, rather than
> 'issue' so you can't really search on them.
>
> I would be perfectly happy with multiple selections getting appended
> onto the 'issue' dataNode as one long string e.g.
>       
>       Issue           'option1,option3,option6'       String
>
> Then a statement like the following would still work:
>       SELECT * FROM nt:base where jcr:path like '/path/%'and issue
> like 'option3'
>
> Any way of achieving a multi-topic paragraph is fine by me though. I
> would be grateful of any suggestions you have!
>
> Chris
>
> -----Original Message-----
> From: [email protected] [mailto:[EMAIL PROTECTED] 
> Sent: 21 February 2008 14:52
> To: [email protected]
> Subject: Re: [magnolia-user] How to specify names of dataNodes with
> controls
>
> Hi Chris,
>
> You suggest to use multiple NodeDatas with the same name. This is not
> supported. Why do you need this? Maybe there is an other solution for
> it.
>
> Ralf
>
> Allan, CJ (Chris) schrieb:
>   
>> Hi,
>>
>> When using the checkbox and multiselect controls in dialogs, a
content
>> node gets created in the JCR (with the name of the content node in
the
>> dialog configuration), and the options that were selected  gets
>>     
> created
>   
>> as dataNodes whose name are 0, 1, 2 etc
>>
>> e.g. if I have a checkbox control on a dialog, named 'options' and
>> someone checks, 'option1' and 'option3', then in the JCR there will
be
>>     
> a
>   
>> content node as follows:
>>      
>>      options
>>         0            option1 String
>>         1            option3 String
>>
>> Is there a way of specifying the name of the dataNodes, so instead it
>> would be
>>
>>      options
>>         mydata       option1 String
>>         mydata       option3 String
>>
>> Thanks,
>>
>> Chris
>>
>> ----------------------------------------------------------------
>> for list details see
>> http://documentation.magnolia.info/docs/en/editor/stayupdated.html
>> ----------------------------------------------------------------
>>
>>   
>>     
>
> ----------------------------------------------------------------
> for list details see
> http://documentation.magnolia.info/docs/en/editor/stayupdated.html
> ----------------------------------------------------------------
>
> ----------------------------------------------------------------
> for list details see
> http://documentation.magnolia.info/docs/en/editor/stayupdated.html
> ----------------------------------------------------------------
>
>   

----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------

----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------

Reply via email to