Was this ever answered? If so, then please ignore my answer.

On Nov 9, 2010, at 10:43 AM, sergio vidangos wrote:

> I'm facing a similar problem and here's what I've found:
> 
> the problem is that the base node type defined in the data module (which is 
> used for data types like contacts), does not allow multiple values for 
> properties. categories are saved as a comma-separated list in a 'categories' 
> property. that's why the properties cannot be saved.
> 
> take a look to this file in the data module:
> /mgnl-nodetypes/magnolia-module-data-nodetypes.xml
> 
> the base type for the data module is called "dataBase" and only supports 
> single-value properties as stated in the following line (i checked module 
> version 1.4, 1.5 and 1.6-snapshot, they're all the same in this regard. 
> That's also the case in the file attached to this thread before):
> 
> <propertyDefinition name="*" requiredType="undefined" autoCreated="false" 
> mandatory="false" onParentVersion="COPY" protected="false" multiple="false"/>
> 
> this line must be added to the node type definition in order to support both, 
> single and multi-value properties:
> 
> <propertyDefinition name="*" requiredType="undefined" autoCreated="false" 
> mandatory="false" onParentVersion="COPY" protected="false" multiple="true"/>
> 
> 
> i can't tell if there's a special reason, why multi-value properties have not 
> been supported yet in the data module. but adding that line would solve the 
> problem described. I think this is a bug of the data module and not the 
> categorization module.

AFAIK there is no special reason apart from not being editable from the tree 
directly.

> 
> But we are facing the trouble now so... is there some easy way to overwrite 
> this node type constraints for the data types I define in the data module? I 
> tried defining my type in the " JCR Node Type" field while creating a new 
> data type, but nothing seems to happen. My definition is well defined, but 
> there's no difference. The nodes I create afterwards are not from this type.
> I couldn't find an example for using this custom definition correctly. Can 
> someone give a hint please?

on existing instance you need to change this in 
/repositories/magnolia/repository/nodetypes/custom_nodetypes.xml ... just find 
the appropriate definition there and update it

HTH,
Jan

> 
> Thanks
> sergio
> 
> 
> 
> 
> 
> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On Behalf Of Zdenek Skodik
> Sent: Wednesday, November 03, 2010 10:09 AM
> To: Magnolia User-List
> Subject: Re: AW: [magnolia-user] Data Module: attach categorization to 
> Contact data type
> 
> 
> Ok, can you please file a bug report at jira and attach the dialog you're 
> facing the issue with since you run into at demo instance as well so we can 
> at least reproduce the issue to see more?
> 
> Thanks,
> Zdenek
> 
> 
> 
> On Tue, 2010-11-02 at 17:56 +0100, frank rittinger wrote:
>> Hi Zdenek,
>> 
>> thank you for the reply. I replaced the file you sent with no luck. I didn't 
>> define custom types, but in the demo project custom types are already 
>> defined. Might this lead to the problem?
>> 
>> I also get the same behavior on the magnolia live demo or a fresh 4.3.8 
>> Version. 
>> 
>> I really only added the new tab reference. Is there maybe something else to 
>> do, I missed?
>> 
>> Best regards,
>> 
>> Frank
>> 
>> -----Ursprüngliche Nachricht-----
>> Von: [email protected] 
>> [mailto:[email protected]] Im Auftrag von Zdenek Skodik
>> Gesendet: Dienstag, 2. November 2010 10:31
>> An: Magnolia User-List
>> Betreff: Re: [magnolia-user] Data Module: attach categorization to 
>> Contact data type
>> 
>> Hello Frank,
>> 
>> hm, it works for me, could you make sure your node type definitions are up 
>> to date?
>> Please find attached default definitions from Magnolia CMS 4.3.8 (you 
>> can simply replace them, when your server is down, in case you haven't 
>> defined your own definitions).
>> 
>> -Zdenek
>> 
>> 
>> On Wed, 2010-10-27 at 15:39 +0200, frank rittinger wrote:
>>> Hello list,
>>> 
>>> 
>>> 
>>> I’m trying to attach categories to the predefined Contact data type in the 
>>> data module. I added the tabCategorization to the Contact dialog. All works 
>>> fine until I try to save a Contact with categories. I then get the 
>>> following JCR Exception:
>>> 
>>> 
>>> 
>>> 2010-10-27 15:21:38,309 ERROR 
>>> nfo.magnolia.module.admininterface.SaveHandlerImpl: no matching 
>>> property definition found for {}categories
>>> 
>>> javax.jcr.nodetype.ConstraintViolationException: no matching 
>>> property definition found for {}categories
>>> 
>>>      at 
>>> org.apache.jackrabbit.core.nodetype.EffectiveNodeType.getApplicableP
>>> ropertyDef(EffectiveNodeType.java:770)
>>> 
>>>      at 
>>> org.apache.jackrabbit.core.NodeImpl.getApplicablePropertyDefinition(
>>> NodeImpl.java:920)
>>> 
>>>      at 
>>> org.apache.jackrabbit.core.NodeImpl.getOrCreateProperty(NodeImpl.jav
>>> a:420)
>>> 
>>>      at 
>>> org.apache.jackrabbit.core.NodeImpl.getOrCreateProperty(NodeImpl.jav
>>> a:391)
>>> 
>>>      at 
>>> org.apache.jackrabbit.core.NodeImpl.setProperty(NodeImpl.java:2290)
>>> 
>>>      at 
>>> info.magnolia.cms.core.DefaultNodeData.setValue(DefaultNodeData.java
>>> :280)
>>> 
>>> 
>>> 
>>> … following stack trace ommitted …
>>> 
>>> 
>>> 
>>> Adding other data to the Contact works fine.
>>> 
>>> 
>>> 
>>> Isn’t it possible to use the categorization module like this or am I 
>>> missing something?
>>> 
>>> 
>>> 
>>> Any help is welcome. Best regards,
>>> 
>>> 
>>> 
>>> Frank
>>> 
>>> 
>>> 
>>> ____________________________________________________________________
>>> _
>>> 
>>> Vorstand: Ralf Heller, Udo Mobes
>>> Vorsitzende des Aufsichtsrates: Kirsten Heller Sitz der 
>>> Gesellschaft: Gruenwaelderstrasse 10-14, D-79098 Freiburg 
>>> Amtsgericht Freiburg HRB 6218
>>> 
>>> Versand am 27.10.2010 15:36 von rittinger frank
>>> Validation-Code: 3743203507640
>>> 
>>> 
>>> 
>>> 
>>> ____________________________________________________________________
>>> __
>>> ----------------------------------------------------------------
>>> 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]>
>> ----------------------------------------------------------------
>> 
>> 
>> ----------------------------------------------------------------
>> 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]>
> ----------------------------------------------------------------
> 
> 
> 
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <[email protected]>
> ----------------------------------------------------------------

-  
Best regards,

Jan Haderka, PhD.
Magnolia International Ltd.
http://www.magnolia-cms.com

http://twitter.com/magnolia_cms
http://facebook.com/Magnolia
--------------------------------------
Magnolia®  - Simple Open-Source Content Management



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