[MGNLCAT-23] Error while saving categories to the Contact data type Created: 03/Nov/10 Updated: 04/Nov/15 Resolved: 04/Nov/15 |
|
| Status: | Closed |
| Project: | Magnolia Categorization Module |
| Component/s: | None |
| Affects Version/s: | 1.1.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Frank Rittinger | Assignee: | Teresa Miyar |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Magnolia 3.4.8 Enterprise, magnolia live demo site and local magnolia demo |
||
| Attachments: |
|
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
When I try to save categories on the data modules Contact element, Magnolia doesn't save the form but redisplays it empty again and throws the following exception. Workflow:
2010-11-03 11:05:14,933 ERROR nfo.magnolia.module.admininterface.SaveHandlerImpl: no matching property definition found for {}categories |
| Comments |
| Comment by Frank Rittinger [ 03/Nov/10 ] |
|
dialog definition |
| Comment by Suzanne Deprez [ 29/Mar/11 ] |
|
I was able to eliminate this error by adding the following line to within the nodetype (within a <nodetype> </nodetype> pair) for a Data type within the file webapps/magnoliaAuthor/repositories/magnolia/repository/nodetypes/custom_nodetypes.xml in the apache installation directory for Magnolia: This was done after adding the tabCategorization to the dialog for the Data type in AdminCentral. |
| Comment by Zdenek Skodik [ 31/Mar/11 ] |
|
In other words the issue is that the base node type of the data module - dataBase - does not allow multiple values for properties. All the data types defined by the Data module are children of this dataBase and as such inherit that multiple="false" by default. |
| Comment by Michael Mühlebach [ 04/Nov/15 ] |
|
Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes. |