[MGNLFORUM-115] Nodetype definition is not correct in file magnolia-forum-nodetypes.xml Created: 12/Oct/10 Updated: 13/Mar/12 Resolved: 08/Dec/10 |
|
| Status: | Closed |
| Project: | Forum (closed) |
| Component/s: | None |
| Affects Version/s: | 1.2.1 |
| Fix Version/s: | 1.3 |
| Type: | Bug | Priority: | Major |
| Reporter: | Christian Ringele | Assignee: | Magnolia International |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
When updating the forum module from 1.1 to 1.2.1 it expects two new values in the file custom_nodetype.xml: <propertyDefinition autoCreated="false" mandatory="false" multiple="false" name="mgnl:ordering_info" onParentVersion="COPY" protected="false" requiredType="String" /> and <childNodeDefinition autoCreated="true" defaultPrimaryType="mgnl:metaData" mandatory="true" name="MetaData" onParentVersion="COPY" protected="false" sameNameSiblings="false"> <requiredPrimaryTypes> <requiredPrimaryType>mgnl:metaData</requiredPrimaryType> </requiredPrimaryTypes> </childNodeDefinition> But when installing the forum module directly with version 1.2.1, these definitions are not added, because they are missing in the file: |
| Comments |
| Comment by Magnolia International [ 06/Dec/10 ] |
|
The MetaData issue should be fixed with Christian - could you check the latest snapshot and let me know if it works on your end ? |
| Comment by Magnolia International [ 08/Dec/10 ] |
|
tested positively by Christian. |